"Mark Phippard" <markphip_at_gmail.com> writes:
> glasser seems to be raising 3 main issues to consider before RC:
> 1) Documentation of new features
> 2) Issue tracker sweep
> 3) XFail sweep
> Documentation is always an issue, other than finishing the release
> notes I do not see where we are lacking though. Especially if we are
> comparing this to our previous releases. The book is in better shape
> for 1.5 then it has been for any of the other post-1.0 releases. What
> other documentation is needed and where do we put it? You have
> singled out merge tracking, but what about other new features? I
> guess we can always do better, but we need to hold up an RC for this?
Specifically, I think we are lacking appropriate expectation management
on merge tracking. It's not enough to document what it does; we must
also document what it *doesn't* do (yet) that people might be expecting
it to do.
The most important place to do this is the release notes. The book
should also do it a bit, but that has to be carefully worded because
some of those missing features will be implemented during the time the
book is still in print.
> Issue tracker sweep. Not sure if you have something specific in mind,
> but it sure seems like we have paid more attention to the issue
> tracker for this release than any other. What were you looking for us
> to do? AFAIK, we have done everything that has been mentioned on this
> list, but I could be overlooking some stuff.
This is done AFAIK. We're also doing a revisions sweep to make sure
CHANGES and the release notes are complete; I should be done with that
today, though (only 1000 revs to go, thanks to the efforts of the
'manyhands' crew over the last week!).
> Finally, your first point was just about how we generally feel. All I
> can say is that I do not see how we are ever going to feel better
> other than proceeding towards release. If we just keep idling you are
> not going to wake up one morning and just decide you feel like we are
> ready. I do not think we would be running it for our own repository
> if we did not feel comfortable that it represented an improvement over
Agreed. But we do need to manage expectations, provide good docs, and
check over those XFails. I can look at the Xfails after finishing the
release notes, but it'd be great if someone could do it sooner...
Anyway: let's have a beta out there while the above is going on!
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-03-12 19:05:49 CET