Re: Branching trunk and creating 1.2
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 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 over again. What do you think ? Other thoughts? On Nov 18, 2006, at 5:15 AM, Vamsavardhana Reddy wrote: 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 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 outstanding issues I'm aware of. 1. Upgrade all the license headers and copyright notices to conform to the new ASF guidelines. 2. Need to get some issues with the connectors straightened out. Also, we're down from 200 JIRAs to 88 and still decreasing :) When we get these items straightened out I'd like to go ahead and make the branch tonight if we're good. Dain expressed his concerns about drift in the code base and having lived through the dead-1.2 branch muck he's spot on. We need to make sure that code doesn't get committed in one place and not another. Anyone want to volunteer to be the goat herder? Any other issues people can think of? Matt Hogstrom [EMAIL PROTECTED] When the clouds are full they pour the rain out on the earth; and whether a tree falls to the north, or it falls to the south, wherever the tree falls, there it lies. Matt Hogstrom [EMAIL PROTECTED] When the clouds are full they pour the rain out on the earth;and whether a tree falls to the north, or it falls to the south, wherever the tree falls, there is lies.
Re: Branching trunk and creating 1.2
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 [EMAIL PROTECTED] wrote: 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
Re: Branching trunk and creating 1.2
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 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 outstanding issues I'm aware of. 1. Upgrade all the license headers and copyright notices to conform to the new ASF guidelines. 2. Need to get some issues with the connectors straightened out. Also, we're down from 200 JIRAs to 88 and still decreasing :) When we get these items straightened out I'd like to go ahead and make the branch tonight if we're good. Dain expressed his concerns about drift in the code base and having lived through the dead-1.2 branch muck he's spot on. We need to make sure that code doesn't get committed in one place and not another. Anyone want to volunteer to be the goat herder? Any other issues people can think of? Matt Hogstrom [EMAIL PROTECTED] When the clouds are full they pour the rain out on the earth; and whether a tree falls to the north, or it falls to the south, wherever the tree falls, there it lies.
Re: Branching trunk and creating 1.2
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 over again. What do you think ? Other thoughts? On Nov 18, 2006, at 5:15 AM, Vamsavardhana Reddy wrote: 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 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 outstanding issues I'm aware of. 1. Upgrade all the license headers and copyright notices to conform to the new ASF guidelines. 2. Need to get some issues with the connectors straightened out. Also, we're down from 200 JIRAs to 88 and still decreasing :) When we get these items straightened out I'd like to go ahead and make the branch tonight if we're good. Dain expressed his concerns about drift in the code base and having lived through the dead-1.2 branch muck he's spot on. We need to make sure that code doesn't get committed in one place and not another. Anyone want to volunteer to be the goat herder? Any other issues people can think of? Matt Hogstrom [EMAIL PROTECTED] When the clouds are full they pour the rain out on the earth; and whether a tree falls to the north, or it falls to the south, wherever the tree falls, there it lies. Matt Hogstrom [EMAIL PROTECTED] When the clouds are full they pour the rain out on the earth; and whether a tree falls to the north, or it falls to the south, wherever the tree falls, there is lies.
Branching trunk and creating 1.2
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 outstanding issues I'm aware of. 1. Upgrade all the license headers and copyright notices to conform to the new ASF guidelines. 2. Need to get some issues with the connectors straightened out. Also, we're down from 200 JIRAs to 88 and still decreasing :) When we get these items straightened out I'd like to go ahead and make the branch tonight if we're good. Dain expressed his concerns about drift in the code base and having lived through the dead-1.2 branch muck he's spot on. We need to make sure that code doesn't get committed in one place and not another. Anyone want to volunteer to be the goat herder? Any other issues people can think of? Matt Hogstrom [EMAIL PROTECTED] When the clouds are full they pour the rain out on the earth; and whether a tree falls to the north, or it falls to the south, wherever the tree falls, there it lies.
Re: Branching trunk and creating 1.2
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 better if many were addressed rather than moved to 2.0 and WishList :o(. But, once again every thing can not be addressed right away. --vamsi On 11/17/06, Matt Hogstrom [EMAIL PROTECTED] 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 is underway in trunk is complete. Here is the outstanding issues I'm aware of. 1. Upgrade all the license headers and copyright notices to conform to the new ASF guidelines. 2. Need to get some issues with the connectors straightened out. Also, we're down from 200 JIRAs to 88 and still decreasing :) When we get these items straightened out I'd like to go ahead and make the branch tonight if we're good. Dain expressed his concerns about drift in the code base and having lived through the dead-1.2 branch muck he's spot on. We need to make sure that code doesn't get committed in one place and not another. Anyone want to volunteer to be the goat herder? Any other issues people can think of? Matt Hogstrom [EMAIL PROTECTED] When the clouds are full they pour the rain out on the earth; and whether a tree falls to the north, or it falls to the south, wherever the tree falls, there it lies.
Re: Branching trunk and creating 1.2
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 is underway in trunk is complete. Here is the outstanding issues I'm aware of. 1. Upgrade all the license headers and copyright notices to conform to the new ASF guidelines. 2. Need to get some issues with the connectors straightened out. We're 98% there... I'm done updating source files with old license headers (updating license text and removing copyrights). Thanks to Jay McHugh, most of the files that did not have a license headers have also been updated. Only applications/console remain... After I update applications/console, I'll rerun the scans to verify we're in good shape. Also, we're down from 200 JIRAs to 88 and still decreasing :) Nice. Thanks! When we get these items straightened out I'd like to go ahead and make the branch tonight if we're good. Dain expressed his concerns about drift in the code base and having lived through the dead-1.2 branch muck he's spot on. We need to make sure that code doesn't get committed in one place and not another. Anyone want to volunteer to be the goat herder? Any other issues people can think of? LICENSE and NOTICE files still need to be updated to be ready for a 1.2 release. However, I don't think that should hold up a branch. I'll work on that. May or may not be done today. This is a small number of files. I'm happy to merge... Once I get the applications/console updates in, I think we can branch at any time. We still have known must-fix problems (recent xalan issue on Java 5, tck issues, etc.). We're signing up to start merging issues like that... IMO, key to making this work is timely merging of updates. People working on 1.2 are likely to be the people under the most time pressures. If merging starts to pose a problem, I'm certainly willing to help... Merging, building, and testing can take significant hunks of time... Let's be sure and spread this pain around a little bit... --kevan
Re: Branching trunk and creating 1.2
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 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 outstanding issues I'm aware of. 1. Upgrade all the license headers and copyright notices to conform to the new ASF guidelines. 2. Need to get some issues with the connectors straightened out. Also, we're down from 200 JIRAs to 88 and still decreasing :) When we get these items straightened out I'd like to go ahead and make the branch tonight if we're good. Dain expressed his concerns about drift in the code base and having lived through the dead-1.2 branch muck he's spot on. We need to make sure that code doesn't get committed in one place and not another. Anyone want to volunteer to be the goat herder? Any other issues people can think of? Matt Hogstrom [EMAIL PROTECTED] When the clouds are full they pour the rain out on the earth; and whether a tree falls to the north, or it falls to the south, wherever the tree falls, there it lies.
Re: Branching trunk and creating 1.2
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 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 outstanding issues I'm aware of. 1. Upgrade all the license headers and copyright notices to conform to the new ASF guidelines. 2. Need to get some issues with the connectors straightened out. Also, we're down from 200 JIRAs to 88 and still decreasing :) When we get these items straightened out I'd like to go ahead and make the branch tonight if we're good. Dain expressed his concerns about drift in the code base and having lived through the dead-1.2 branch muck he's spot on. We need to make sure that code doesn't get committed in one place and not another. Anyone want to volunteer to be the goat herder? Any other issues people can think of? Matt Hogstrom [EMAIL PROTECTED] When the clouds are full they pour the rain out on the earth; and whether a tree falls to the north, or it falls to the south, wherever the tree falls, there it lies.
Re: Branching trunk and creating 1.2
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 fix. 2. Need to get some issues with the connectors straightened out. I verified the connector fix this morning and everything is working again. So one I get the nod from Kevan, I'll cut the branch and all the JavaEE 5 code can pour in :) -dain
Re: Branching trunk and creating 1.2
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 something in the console and they are working on a fix. License changes didn't break the console. The problem is being caused by RC 476126. I haven't reverted the change, because it's needed for TCK... This shouldn't hold up the branch. The fix for this can be merged... So one I get the nod from Kevan, I'll cut the branch and all the JavaEE 5 code can pour in :) I'm all done with the license header changes. I think we're good to branch. We still have some work to do before 1.2 is release ready. NOTICE/ LICENSE files need to be updated. There are also some non-APACHE copyrighted files. These need to be investigated... I'll keep working on getting the notice/license files updated and initiate looking at the non-apache copyrights... --kevan
