Justin Erenkrantz <justin@erenkrantz.com> writes:
> I think a lot of people are going to be out of town or busy with the
> families the next two weeks. So, the first week of January is
> probably the earliest I'd think is reasonable to have the initial 1.0
> issue list in place. Otherwise, we're running the risk of not having
> the 'right' people look at issues.
>
> I'd branch now (i.e. Monday or whatever), then allow commits to
> proceed as normal to trunk. If people think their commit should be in
> 1.0, they need to add it to the merging tracker - which we're having a
> parallel discussion on what that should be. ;-)
Oh, the 1.0 branch comes from the 0.35 tag anyway -- trunk commits are
not any more delayed now than after 1.0-stabilization is branched.
Nevertheless, let's try to be conservative about trunk commits. We
want to concentrate review energy on 1.0 as much as possible. I'm not
saying we should vote on the trunk commits (heaven forbid). Just
asking that committers hold off on new feature development and major
code changes for a while, so we can pay that much more attention to
the release.
Regarding dates:
Hmmm, yeah, you're right that a lot of people will be off line for the
holidays. I shouldn't try to rush so much. Let's say:
Thursday, Jan. 8th for all candidate changes listed and voting on them
to be complete.
Does that sound okay?
We shouldn't set a date for all the merges to be done, since we don't
yet know what we're merging. But I think it'll be easier just to set
the 1.0 release date, when we see what's on our plate as of Jan. 8th.
We're going to do the merges as quickly as possible (I'm personally
committing to that, you can bet), so that the changes will be in the
line and testable for as long as possible.
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Dec 19 21:46:17 2003