On 11/05/2013 2:53 AM, Andrew Hughes wrote: <snip>
I have offered a very simple solution to that problem to which no-one has yet given any reason as to why we should not implemented it; simply add a HotSpot tree where pushes can be made prior to JPRT runs, then perform the JPRT runs on the commits in that tree before merging to the main HotSpot tree. Problem solved.
You need one of these repos for each of the hotspot group repos, otherwise the changesets won't be correct. You also need an Oracle employee to then push the change through JPRT - and that would be a lot more effort than the existing processes as "we" would need to clone the external repo first, re-parent the clone to the group repo, re-sync from parent if needed, then do JPRT submit. Plus you need someone to update these repos each time the "parent" gets updated.
So a simple enough idea, but the logistics are more complex. David
