that's fine with me, but do we really have Roller 2.1 code ready to be committed? i have stuff in my workspace that is meant for 2.1, but it's not really ready to be committed yet. Are we that far away from a 2.0 release that we need the branch? Couldn't these things be finalized by the end of the week? AFAIK the only things outstanding are db script related.
-- Allen On Mon, 2005-11-07 at 06:27, Dave Johnson wrote: > Some of us are about to start post-2.0 work, and, in fact, I've already > got some changes to support the Atom protocol that I don't want to > commit to 2.0. > > So, it's not part of the Roller release plan, but I think we need a > roller_2.0 branch > http://rollerweblogger.org/wiki/Wiki.jsp?page=RollerReleasePlan > > The purpose of the branch would be to make the final preparations for > Roller 2.0 release. Once 2.0 is released, we'd merge roller_2.0 to > trunk and we'd copy roller_2.0 to tags. > > Any comments/concerns? > > - Dave >
