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

Re: Subversion 1.5.1 Released

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: Tue, 05 Aug 2008 09:27:55 -0400

Daniel Shahaf wrote:
> Hyrum K. Wright wrote on Mon, 4 Aug 2008 at 14:31 -0700:
>>> -------Original Message-------
>>> From: Kenneth Porter <shiva_at_sewingwitch.com>
>>> Subject: Re: Subversion 1.5.1 Released
>>> Sent: 04 Aug '08 14:32
>>> On Monday, August 04, 2008 11:19 AM -0700 "Hyrum K. Wright"
>>> <hyrum_wright_at_mail.utexas.edu> wrote:
>>> > Heh. I think that's what scared me away from doing announcement on
>>> > Freshmeat initially. (After that, it was just sloth, as I started
>>> > worrying about other aspects of the release process.) I just updated the
>>> > URLs on the main Freshmeat project page to the latest 1.5.1 tarballs, but
>>> > I'm a bit confused on how to go about creating/announcing a release.
>>> I went back through the archives looking for "freshmeat" and found this
>>> ancient thread and mention of "notes/releases.txt" but can't find that file
>>> in the repo in the current trunk or in obsolete-notes off the root. What
>>> became of it?
>> That would be http://subversion.tigris.org/release-process.html That document doesn't say a whole lot about *how* to update Freshmeat, just that it should probably be done.
> Freshmeat's FAQ has an entry[1] "I released a new version of my program,
> what now?", presumably that's what we need to do now?
> [1] http://freshmeat.net/faq/view/20/

Yes, yes, I know how to add new releases. But Freshmeat has this
two-dimensional concept of releases. There are branches, and there are
releases along those branches. Currently, we have the following tips to our

    Default 1.4.3
    1.0.x 1.0.9
    Development 1.4.6

I *think* these were intended to be defined as:

    Default - the latest official release
    1.0.x (and similar) - maintenance releases along a minor version line
    Development - pre-release snapshots

If 1.4.6 had been added to "Default", I think the picture would be clearer.

In a perfect world, I'd suggest: We create a 1.4.x branch and add 1.4.6
(again) to it. We create a 1.5.x branch and add 1.5.0 and 1.5.1 to it. We
also add 1.5.0 and 1.5.1 to Default.

But I'm not sure that Freshmeat admins like to have duplicated releases in
different branches. So perhaps the easiest thing to do would be to abandon
the ".x" branches, and stick with Default and Development. (And maybe ask a
Freshmeat admin if 1.4.6 can be moved from Development to Default.)

Shall I move ahead with one of these plans?

C. Michael Pilato <cmpilato_at_collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand

Received on 2008-08-05 15:28:16 CEST

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.