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

RE: project_status.html

From: Sander Striker <striker_at_apache.org>
Date: 2003-07-07 13:10:25 CEST

> From: 'Roman Neuhauser' [mailto:neuhauser@bellavista.cz]
> Sent: Monday, July 07, 2003 12:31 PM

> [please respect my MFT header. also, quoting some of my message would
> be nice so that I (or others who don't use threading MUAs don't have
> to wade through lots of mail to find out what you're replying to]

> # jszakmeister@actelesys.com / 2003-07-07 05:57:14 -0400:
>> Relax, Subversion *just* got a new release manager and he's getting up to
>> speed on the release process. :-) This is the first time that I recall them
>> being late on a release since I started watching this list March of last
>> year.
> Actually, I'm quite relaxed. I don't have any problems with
> subversion getting beind the schedule to any stretch of time, it's
> just that the html page (or the data it's generated from, I don't
> know) is out of sync with reality.

This happens sometimes. It's just a matter of someone scraping enough
of his free time to update it. Usually the Chicago team sets the release
dates, and the release manager updates the page when a release is done.
If there is inaccurate data for a few days, so be it. A release date is
an intent to release on or around that date, not a hard deadline IMO.

>> You can find the CHANGES file you seek in the online repository. Just point
>> your favorite browser to http://svn.collab.net/repos/svn/trunk/CHANGES. The
>> CHANGES file will show what was included in a release.
> fine. would be nice if this would be linked from the status page.

Patches welcome. The site is in http://svn.collab.net/repos/svn/trunk/www/.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jul 7 13:11:23 2003

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.