On 8/31/07, Hyrum K. Wright <email@example.com> wrote:
> Mark Phippard wrote:
> > On 8/30/07, Karl Fogel <firstname.lastname@example.org> wrote:
> >> "Mark Phippard" <email@example.com> writes:
> >>> I propose October 12th as that date, which gives us 6 full weeks of
> >>> development time, and if we get the pieces in place quickly for a
> >>> release candidate, gives us enough time to get the GA out before the
> >>> end of the year. Personally, I think we should shoot for end of
> >>> November, so that X-Mas and holiday season does not get in the way.
> >> +1
> >> I think it's time to set a date and mean it. We've got to get this
> >> thing out before the end of the year!
> > Thanks for responding. I thought this would have got more responses
> > than it has.
> > Hyrum, Erik, Vlad, Ivan, Eric, Blair ???
> > You've all contributed a lot already and recently. You must have opinions.
> I *always* have opinions. :)
> Personally, I still have a few tweaks to make to the 'log -g' and 'blame
> - -g' stuff, and I think I can have that done in the next couple of
> weeks. There are also a couple of known issues (they are in the issue
> tracker, iirc), and I plan to look at those also. I'm going to be busy
> with academic pursuits for the next few months, so my time to work on
> Subversion may be fairly limited.
If you think the issues are 1.5-critical just please make sure they
have the 1.5 milestone set. Obviously we can make all the additional
fixes and enhancements we want between now and the branch, but we
ought to make sure anything we feel has to be in the release has the
> I think branching 1.5 on October 12th would be good goal. But, I also
> think that the stabilization period is going to take a while. Merge
> tracking is Hard, and I just have this sneaky suspicion that we're going
> to discover some interesting bugs with the increased testing when we
> start releasing RCs. There's nothing wrong with that (I prefer known
> bugs to unknown ones), but it's something we should remember. There's
> just a lot in this release.
You are probably right. All the more reason to start the process as
soon as reasonable. Of course people could start doing code review
I am going to be updating our "Early Adopter" builds on openCollabNet.
Hopefully some of our customers will kick the tires some more and
help find issues. Our previous builds turned up a few items that made
it into the issue tracker.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Fri Aug 31 19:41:10 2007