On Jan 30, 2006, at 2:56 PM, Matt Raible wrote:
Sounds good to me - but I'm curious to know what remains on head, as
this is the "branch" I tend ot use.
I want to move 2.1 to a branch so we can move head with the 2.2 work
(see the JIRA roadmap) in the trunk. Allen and I are working to
finish the
2.2 items that we've signed up for by Feb. 16.
- Dave
Matt
On 1/30/06, Dave Johnson <[EMAIL PROTECTED]> 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
