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

Re: release thoughts? (was: svn commit: rev 3163)

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2002-09-13 02:14:09 CEST

Garrett Rooney <rooneg@electricjellyfish.net> writes:

> On Thursday, September 12, 2002, at 07:33 PM, Greg Stein wrote:
>
> > Hmm. But a release doesn't have to have CN devs' changes in
> > it. Should we go
> > ahead and make a 0.14.3 release "soon", which incorporates all of this
> > recent work?
> >
> > To that end, I'd ask the devs: do you feel that some good forward
> > motion has
> > occurred since 0.14.2? Should we make a release to incorporate that?
> > When?
>
> personally, i think a release is in order relatively soon, if only to
> get all of philip's bug fixes out to the world so he doesn't have to
> keep saying 'i already fixed that in rev FOO'. ;-)
>
> on the other hand, if there's going to be another release of apr-util
> and apr soon (like the next day or so), then i would be in favor of
> waiting for that, since it would be quite nice to be able to point
> people at a real apr/apr-util release. we can't really send them to
> the 0.9.1 tarballs, since apr-util won't even configure out of the box.

I soooooooooo agree.

When we release 0.14.3, I wanna be able to tell people "this builds
against apr(-util) 0.9.1 and httpd-2.0.41." Bing, bang, boom, they
get the correct release tarballs, and it works.

Building against released tarballs provides warm fuzzy feelings,
while telling people to checkout bleeding edge cvs trees does not.

So can we wait till httpd-2.0.41 is released this weekend (and
apr-util as well)?

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Sep 13 02:15:49 2002

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.