On 26 Jun 07, at 2:05 PM 26 Jun 07, Patrick Schneider wrote:
Ok, so the new features start on trunk but the new feature is a
branch of trunk. The point being feature additions don't destabilize
the trunk. The series of branches associated with issues also
provides a clear path of what happened, branches named with something
like MNG-123-AndMaybeSomeQuickDescription make it easy to know what
it is and to look up the issue. For dead simple fixes things can go
into the trunk but anything requiring more then a few hours of work
should go into a feature branch of trunk. When it's merged back into
trunk, if it's possible it is then merged back into any version
branches (like 2.0.x).
I put that into the document. Sorry for not being more clear.
Gotcha -- this makes sense now. Guess I just needed it spelled out
a little
more explicitly ;o)
>
> Patrick
>
> On 6/25/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
>>
>> Hi,
>>
>> As part of trying to make the whole process of making changes and
>> adding new features transparent to everyone involved I've
whipped up
>> a little sketch for perusal:
>>
>> http://people.apache.org/~jvanzyl/DevProcess.png
>>
>> Basically it revolves around making sure things are documented
in the
>> Wiki and providing a clear record of the evolution of the project
>> that anyone can follow at any point in time. So far from
perfect but
>> I think a good starting point and I would like to field
feedback so I
>> can improve it. It basically revolves around the dashboard
where I've
>> tried to collect all relevant information about the project:
>>
>> http://docs.codehaus.org/display/MAVEN/Home
>>
>> And process is based around making proposals that eventually will
>> serve as the record of evolution of the project. The goal is
not to
>> have anything that's heavy, and that we might eventually be
able to
>> automate some data gathering but for the meantime it's not overly
>> onerous and provides some visibility we have not yet had to date.
>>
>> The proposals are all here:
>>
>> http://docs.codehaus.org/display/MAVEN/All+Proposals
>>
>> And they basically move from draft -> pending -> approved. I've
put
>> some notes in the diagram and I figured we could start with a
simple
>> proposal to see how it works and iron the kinks as we go. This is
>> experimental but I see it as the best way forward for getting a
clear
>> view of what's going on
>>
>> Thanks,
>>
>> Jason
>>
>> ----------------------------------------------------------
>> Jason van Zyl
>> Founder and PMC Chair, Apache Maven
>> jason at sonatype dot com
>> ----------------------------------------------------------
>>
>>
>>
>>
>>
---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
