esme-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Richard Hirsch <>
Subject Re: Committing code in trunk or RC1 branch
Date Thu, 25 Feb 2010 14:12:04 GMT
On Thu, Feb 25, 2010 at 2:59 PM, Ethan Jewett <> wrote:
> Do the changes need to go into the release we are currently trying to
> get pushed out? This would involve doing another vote. If not, then I
> think they should go into trunk.

What release are you talking about? RC1 or 1.0?  All the new code is
for 1.0 but not for RC1.

Seeing I'm not a configuration managment guru, my thought was to
continue work in the trunk and when reach another milestone (RC2) we
cut another release.

I'll wait and see what your thoughts on the release process.


> I still need to respond to the release strategy email and might not
> get to it until this weekend, but my opinion is that when we are
> attempting a release we should have a tag that tracks the release. The
> release tag is tightly controlled and any changes to the tag mean that
> we must put out a new release candidate to be voted on as whatever
> release we are trying to put out (1.0 in this case), but new code can
> continue to go into trunk unimpeded.
> Ethan
> On Thu, Feb 25, 2010 at 3:43 AM, Richard Hirsch <> wrote:
>> Yesterday I had some time during a long bus trip and worked on various
>> JIRA items. I made my changes in the trunk but now I'm wondering
>> whether I should have been working in the RC1 branch.
>> I'd like to get the change into SVN before others start changing code
>> as well. So, the question is where do I commit my code.
>> D.

View raw message