C. Michael Pilato wrote on Tue, 5 Aug 2008 at 09:27 -0400:
> 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
> branches:
>
> 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?
>
>
+1, assuming that we have to have a 'Default' branch.
Daniel
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-08-05 16:00:54 CEST