JDK 9 Sandbox Development Forest

[Chris Hegarty]

On 16 Dec 2014, at 02:23, Stuart Marks <stuart.marks at oracle.com> wrote:

> Yay sandbox!
> 
> Thanks for following through with this, Chris.
> 
> Just to try things out, I've created my own test branch "smarks-test0". And I've already run into a bug in hgforest.sh. :-) The problem is that following the instructions in the sandbox guidance:
> 
>    http://cr.openjdk.java.net/~chegar/docs/sandbox.html
> 
> The example line to commit an initial changeset to the branch:
> 
>    sh common/bin/hgforest.sh commit -m "Initial changes for JDK-8000000”

D’oh! I used '-l’ when testing, but ‘-m’ appeared clearer in the documentation.

> doesn't work. The problem is that hgforest.sh breaks the quoted string into separate arguments, which the commit command doesn't like. I've filed https://bugs.openjdk.java.net/browse/JDK-8067631 on this.
> 
> The workaround is to put the commit comment into a file and do something like
> 
>    sh common/bin/hgforest.sh commit -l /absolute/path/to/comment.txt

Yes, this will work. Thanks.

> Meanwhile, I've done a bit of hacking on the hgforest.sh script, and I've posted a webrev--, er, no, I've pushed a changeset (!) here:
> 
>    http://hg.openjdk.java.net/jdk9/sandbox/rev/886037762070
> 
> It's on my own branch, of course.
> 
> If people could try this out, I'll transplant it back to jdk9-dev at some point.

I played with this on Mac and Linux, and it works. I also reviewed the changes in the changeset. Consider it Reviewed.

If you can push this to jdk9/dev, then I’ll hold off changing the documentation to use ‘-l’.

-Chris.

> All hail the new era of the JDK Sandbox!
> 
> s'marks
> 
> 
> 
> 
> 
> 
> On 12/15/14 11:38 AM, Chris Hegarty wrote:
>> Hi,
>> 
>> Announcing the JDK 9 Sandbox Development Forest, as proposed by Mike Duigou [1].
>> 
>> The primary purpose of the JDK 9 Sandbox Development Forest is to facilitate OpenJDK developers that are working on non-trivial changes, possibly JEP-scale effort, whose scope and duration make it necessary to collaborate with others in an open shared version control system, rather than just using privately shared patches.
>> 
>> Working in the sandbox can facilitate rapid iterative development, as there is no requirement for changes to be reviewed or accompanied by bug numbers, i.e. jcheck is not enabled. Just create a new branch and start working. When the changes are ready for integration into the main-line, then they will need to follow the appropriate forest integration rules. Any committer to the JDK 9 project can push changes to the sandbox.
>> 
>> Questions or issues relating to it should be directed to the maintainer, Chris Hegarty. It is strongly recommended that you subscribed to the changes mailing list if you are actively developing changes in the sandbox.
>> 
>> 	• Forest location: http://hg.openjdk.java.net/jdk9/sandbox
>> 	• Changeset notifications: jdk9-sandbox-changes at openjdk dot java dot net
>> 
>> Please read the following common questions and guidance before using the sandbox.
>>   http://cr.openjdk.java.net/~chegar/docs/sandbox.html
>> 
>> The most important rule to keep in mind when using the sandbox is; You should never push changes to the default branch. All active development should happen in branches ( other than the default ), leaving the default branch “clean”, so it can easily be updated with changes from the upstream main-line forest. Individual branch owners can, at their discretion, sync up their branch with the main-line changes in the default branch.
>> 
>> -Chris.
>> 
>> [1] http://mail.openjdk.java.net/pipermail/discuss/2014-September/003552.html
>>