Summary Results:
+1 - David DeWolf, Ate, Raphael, Stephan, David Sean Taylor, and Carsten
0 - NONE
-1 - NONE
Everyone seemed to prefer creating the branch specifically for the 286
compatibility work.
I will move forward with creating both the JIRA version and the Branch.
I will probably wait to create the branch until after we cut the
upcoming 1.1.0-beta2 release within the next week.
Unless someone chimes in with better names, I will create:
Branch: 1.1-286-COMPATIBILITY
JIRA: 1.1-286-COMPATIBILITY
The 1.1 indicates where the branch will be coming from and the 286
compatibility obviously implies spec work. This naming convention is
not intended to imply what the work may eventually be released as. That
will be up for a vote when it's time for the release or merging into the
trunk.
David
Stefan Hepper wrote:
+1
[X] Create the branch for 286 work
Stefan
David H. DeWolf wrote:
It seems that based on the feedback from last week's meeting recap and
proposal email, we are generally in agreement that we should move
forward with creating a branch and new jira version for jsr 286 work.
To that end, I would like to propose an official vote for the first
step. . . creating the branch and version. Please note that this is
not an endorsement for any code, all code will be considered on the
pluto-dev list as with any other contribution.
Some people mentioned that they would prefer to create a branch for
1.1 maintenance and keep the 286 work in the trunk. In addition to
your +1/0/-1 vote, please also indicate:
[] Create the branch for 286 work
[] Create the branch for pluto-1.1 work, keep trunk the bleeding edge
(286)
Thanks,
David
