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

Re: Features, releases and team work

From: Karl Fogel <kfogel_at_red-bean.com>
Date: 2007-03-28 21:46:51 CEST

"Erik Huelsmann" <ehuels@gmail.com> writes:
> I see a big difference in philosophy here and I do think it's not
> something to shrug about really, because as long as we don't actually
> choose for one or the other, I'm feeling we're going to have last
> weeks discussion on every release.

Sorry, I didn't mean to imply that I was shrugging off the issue.

One thing that might help would be for us to stop insisting that every
minor release number must mean at least one major new feature.
Instead, it could just be that we feel the code has progressed far
enough, and enough bugs have been fixed (but not backported), that
it's time for something bigger than a patch release.

I think this would cut down on a lot of frustration, because people
who have made improvements (including minor new features that wouldn't
by themselves justify a release under the current system) would see
them get out the door sooner. At the same time, if a major feature is
close to being done, we can try to coordinate it with the release --
no need to be dogmatic either way about it.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Mar 28 21:47:08 2007

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.