New branches created (Re: I'd like to create branches for 2.1 and for tagging)

[David M Johnson <Da...@Sun.COM>]

The new branches are:
    /roller/branches/roller_2.1
    /roller/branches/roller_2.1_tagging

So...
- Final 2.1 fixes can occur in the roller_2.1 branch
- Tagging code can be committed in the roller_2.1_tagging branch
- And Roller 2.2 work can now commence in the trunk

- Dave



On Jan 30, 2006, at 6:12 PM, Elias Torres wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I'm ok with it.
>
> - -Elias
>
> Dave Johnson wrote:
>> I'd like to create two new branches:
>>
>> *** Release branch for 2.1
>>
>> Now that we're on a 2nd release candidate for Roller 2.1, I'd like to
>> move 2.1 to a branch for final fixes and then to a tag when we   
>> release.
>> We have lots of small fixes and improvements on tap for the  next
>> release and we need to get to work in the trunk.
>>
>> *** Development branch for tagging
>>
>> Our users are *very* eager to get their hands on tagging, but I think
>> we need to walk carefully here. Instead of committing the tagging   
>> code
>> to the main branch, I'd like have it committed to a development   
>> branch
>> for review. I'm suggesting this because 1) we're pretty stable   
>> now and
>> getting comfortable with the new caching system 2) there  seems to  
>> be a
>> some controversy about tagging related performance/ caching  
>> concerns and
>> 3) tagging is a significant change that needs  more than usual  
>> review. I
>> guess we could do it in the sandbox, like I  did for the initial  
>> Planet
>> Roller work, but a branch seems easier and  cleaner.
>>
>> Everybody OK with this?
>>
>> - Dave
>>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.1 (GNU/Linux)
>
> iD8DBQFD3p17tsNTCOFcV0oRAu+uAKCFMiN5z+Po5KyUVHe0MxoySH+VkgCfQPrH
> k9x5Q+JSBwyocaChbls9URo=
> =D/MQ
> -----END PGP SIGNATURE-----