+1 to working off of a branch. In addition to keeping development moving, it's also a better approach for delivering service releases. That won't be much of an issue with 0.1, but it will be for 1.0.
-N ----- Original Message ---- From: Davanum Srinivas <[email protected]> To: [email protected] Sent: Friday, August 21, 2009 11:25:44 AM Subject: Re: Open trunk back for commits and future releases I agree that we should try working off a branch so that trunk is always open. Hope the maven gurus can shed light on if this is a possibility. thanks, dims On Fri, Aug 21, 2009 at 12:06 PM, Bryant Luk<[email protected]> wrote: > Hi, > > With Kevan, dims, and ant elder voting +1, I think the IPMC votes are > well underway for 0.1. Thanks Martin and everyone else for helping > with this release. I've certainly learned a lot. > > On that note, I think it's time to reopen trunk and committing some of > the patches that have been available. I'll start making some of the > changes from patches that have been out there. If someone objects, > these can be reverted easily. > > For future releases, the process should go more smoothly since a lot > of the issues shouldn't be repeated. However, I was hoping we could > also refine our release process a bit so that we make a branch to base > the release from instead of using trunk. That way activity can still > happen on trunk while the branch release tag is safe from any unwanted > changes. > > Thoughts? > > -- > > - Bryant Luk > -- Davanum Srinivas :: http://davanum.wordpress.com
