Re: Branching trunk and creating 1.2

2006-11-21 Thread Paul McMahan
My understanding was that after branching 1.2 we would focus on stabilizing that branch for TCK. So I would not commit new features to 1.2 and would only commit bug fixes to 1.2 after getting a green light from one of the release managers (Dain or Alan). Paul On 11/20/06, Vamsavardhana Reddy <[

Re: Branching trunk and creating 1.2

2006-11-21 Thread Vamsavardhana Reddy
I know most of us would want to work on trunk. Whatever commits are done to branches\1.2 should also go into trunk. Should some commits done to trunk be considered for branches\1.2 depending on the relevance? --vamsi On 11/18/06, Matt Hogstrom <[EMAIL PROTECTED]> wrote: Hi Vamsi, I'd like to

Re: Branching trunk and creating 1.2

2006-11-18 Thread Matt Hogstrom
Hi Vamsi, I'd like to try something different. Many of the JIRAs we've moved from release to release to release. I'd like to have people look at the JIRAs and if they are going to work on them then go ahead and assign them to 2.0. Otherwise we'll continue to push them around over, and

Re: Branching trunk and creating 1.2

2006-11-18 Thread Vamsavardhana Reddy
Hi Matt, Now that branches\1.2 is created, I think we need to add 2.0 in the "Fix version" in all the JIRAs marked for 1.2 and 1.x so that they will not closed without merging the fix into the trunk. --vamsi On 11/17/06, Matt Hogstrom <[EMAIL PROTECTED]> wrote: All, We've been talking about

Re: Branching trunk and creating 1.2

2006-11-17 Thread Kevan Miller
On Nov 17, 2006, at 2:21 PM, Dain Sundstrom wrote: On Nov 17, 2006, at 7:49 AM, Matt Hogstrom wrote: 1. Upgrade all the license headers and copyright notices to conform to the new ASF guidelines. Just chatted with kevan and they are almost done with this. One of the license fixes broke

Re: Branching trunk and creating 1.2

2006-11-17 Thread Dain Sundstrom
On Nov 17, 2006, at 7:49 AM, Matt Hogstrom wrote: 1. Upgrade all the license headers and copyright notices to conform to the new ASF guidelines. Just chatted with kevan and they are almost done with this. One of the license fixes broke something in the console and they are working on a f

Re: Branching trunk and creating 1.2

2006-11-17 Thread Sachin Patel
Kevan already did. On 11/17/06, Tim McConnell <[EMAIL PROTECTED]> wrote: Hi Matt, I think Jay already submitted fixes for the license headers and copyright notices. They just need to be committed. I think Sachin is going to do that today. Sachin ?? Matt Hogstrom wrote: > All, > > We've been tal

Re: Branching trunk and creating 1.2

2006-11-17 Thread Tim McConnell
Hi Matt, I think Jay already submitted fixes for the license headers and copyright notices. They just need to be committed. I think Sachin is going to do that today. Sachin ?? Matt Hogstrom wrote: All, We've been talking about moving 1.2 from trunk to a branch while the final touches are put

Re: Branching trunk and creating 1.2

2006-11-17 Thread Kevan Miller
On Nov 17, 2006, at 10:49 AM, Matt Hogstrom wrote: All, We've been talking about moving 1.2 from trunk to a branch while the final touches are put on it as well as promoting trunk to 2.0- SNAPSHOT and starting the push to Java EE 5.0. At this point it looks like most of the activity that

Re: Branching trunk and creating 1.2

2006-11-17 Thread Vamsavardhana Reddy
Matt, as I understand, the commits should go into both places (trunk and branches\1.2) right? And dooes the goat herder need to take care of the missing commits or just push the goat to commit in both places? Good to see that the JIRAs for 1.2 count is coming down :o). It would have been even b

Branching trunk and creating 1.2

2006-11-17 Thread Matt Hogstrom
All, We've been talking about moving 1.2 from trunk to a branch while the final touches are put on it as well as promoting trunk to 2.0- SNAPSHOT and starting the push to Java EE 5.0. At this point it looks like most of the activity that is underway in trunk is complete. Here is the outst