[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

milestones and quality

From: Karl Fogel <kfogel_at_newton.ch.collab.net>
Date: 2002-02-09 06:08:43 CET

A one-sentence summary of this message might be:

       "Mike Pilato and I have decided to stop trying
        to be smarter than the dev list."

The details are:

Mike, Greg Stein, Ben and I talked, and decided to take the diff/merge
changes out of Milestone 9. They're proving quite complex, and more
peer review is needed. Rushing will only result in poor quality.
(Anyone who saw this coming will kindly *not* say "I told you so." :-)

In a separate thread following this message, I'll discuss what Mike
and I have got so far regarding the big diff code refactorization, and
hopefully get lots of feedback and ideas. Milestone 10 (Subversion
0.10, no that's not a decimal point) will be the implementation of
"svn merge", most likely on top of a refactored "svn diff".

Milestone 9, meanwhile, becomes the "svn switch" command, the
resolution of some repository stability problems (not all of them, but
it's a lot more stable than it used to be), and the scores of little
features and bugfixes that have happened since M8.

Those small improvements weren't on the orginal roadmap, but there
have been 318 (!) commits since M8 (revision 909), and cumulatively
they amount to a lot of change. Greg Stein points out that it's a
good time to start maintaining a CHANGES file -- would anyone like to
volunteer? This would be much less detailed than the output of "svn
log"; it would just list, in order of importance, the user-visible
changes since 0.8 was released.

Greg, what was that url you gave me, had a good example of a CHANGES
file? Was it



To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:37:05 2006

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.