-
Notifications
You must be signed in to change notification settings - Fork 149
Setup AGI to be built with Kokoro #2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
GAPID_VERSION_MINOR="7" | ||
GAPID_VERSION_POINT="0" | ||
AGI_VERSION_MAJOR="0" | ||
AGI_VERSION_MINOR="9" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this be 0.1.0 (not sure how pre-1.0.0 habits are)?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We are so close to the 1.0 release, I picked 0.9. I expect us to do at most 1 minor release, before we bump this to 1.0.
- Combine *SliceSelectionView.java and *SlicesSelectionView.java into one, do selection count checking at selection view composite creation time, and set the composite layout accordingly. - This can help reduce file numbers and make it easier to locate selection view composite.
- When user right click on a command in the Performance tab, there would be an option "Select in Command Tab", which lets user quickly jump to the same command in the Command tab, and have all other resource tabs start loading.
- Change the two pass performance loading mechanism, in which the first pass server calculate crude data and save inside database, and the second pass the client query server dynamically based on expanding action. - Instead, server derive and calculate performance for all possible parent command nodes at intialization time, altogether with the performance calculation for the leaf commands (renderpass commands). All the perf data will be passed back to client once and all.
- Change the two pass performance loading mechanism, in which the first pass server calculate crude data and save inside database, and the second pass the client query server dynamically based on expanding action. - Instead, server derive and calculate performance for all possible parent command nodes at intialization time, altogether with the performance calculation for the leaf commands (renderpass commands). All the perf data will be passed back to client once and all.
- Change the two pass performance loading mechanism, in which the first pass server calculate crude data and save inside database, and the second pass the client query server dynamically based on expanding action. - Instead, server derive and calculate performance for all possible parent command nodes at intialization time, altogether with the performance calculation for the leaf commands (renderpass commands). All the perf data will be passed back to client once and all.
- Change the two pass performance loading mechanism, in which the first pass server calculate crude data and save inside database, and the second pass the client query server dynamically based on expanding action. - Instead, server derive and calculate performance for all possible parent command nodes at intialization time, altogether with the performance calculation for the leaf commands (renderpass commands). All the perf data will be passed back to client once and all.
No description provided.