You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by "C. Michael Pilato" <cm...@collab.net> on 2008/08/07 13:14:25 UTC

Release stream openness indications in STATUS

Would anybody mind us adopting a habit of maintaining, in the STATUS files 
of our release stream branches, our official position on the maintenance of 
that branch?  I thinking something like the following, to be placed at the 
very top of the branch STATUS file:

1.0.x - 1.3.x:

   * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
   *                                                       *
   *  This release stream is closed to further changes.    *
   *                                                       *
   * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

1.4.x:

   * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
   *                                                       *
   *  This release stream has been superceded by 1.X, but  *
   *  remains open to receive fixes for serious and        *
   *  security-related bugs.                               *
   *                                                       *
   * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

1.5.x:

   * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
   *                                                       *
   *  This release stream is open to bug fixes.            *
   *                                                       *
   * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

It's just a tiny little way for folks to quickly know the status of a given 
release stream without doing version arithmetic and being aware of our 
2-streams-open policy or exceptions to it.

Thoughts?

-- 
C. Michael Pilato <cm...@collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand


Re: Release stream openness indications in STATUS

Posted by Julian Foad <ju...@btopenworld.com>.
On Thu, 2008-08-07 at 09:14 -0400, C. Michael Pilato wrote:
> Would anybody mind us adopting a habit of maintaining, in the STATUS files 
> of our release stream branches, our official position on the maintenance of 
> that branch?  I thinking something like the following, to be placed at the 
> very top of the branch STATUS file:
> 
> 1.0.x - 1.3.x:
> 
>    * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
>    *                                                       *
>    *  This release stream is closed to further changes.    *
>    *                                                       *
>    * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
> 
> 1.4.x:
> 
>    * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
>    *                                                       *
>    *  This release stream has been superceded by 1.X, but  *
>    *  remains open to receive fixes for serious and        *
>    *  security-related bugs.                               *
>    *                                                       *
>    * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
> 
> 1.5.x:
> 
>    * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
>    *                                                       *
>    *  This release stream is open to bug fixes.            *
>    *                                                       *
>    * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
> 
> It's just a tiny little way for folks to quickly know the status of a given 
> release stream without doing version arithmetic and being aware of our 
> 2-streams-open policy or exceptions to it.
> 
> Thoughts?

Reasonable, but shouldn't we (as well or instead) be closing dead
branches by deleting them from the /branches directory? It looks like
there are several dead ones, not just 1.x.x but 'ebcdic' for example.

- Julian



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: Release stream openness indications in STATUS

Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
C. Michael Pilato wrote on Thu, 7 Aug 2008 at 09:14 -0400:
> Would anybody mind us adopting a habit of maintaining, in the STATUS files of
> our release stream branches, our official position on the maintenance of that
> branch?  I thinking something like the following, to be placed at the very top
> of the branch STATUS file:
> 
> 1.0.x - 1.3.x:
> 
>   * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
>   *                                                       *
>   *  This release stream is closed to further changes.    *
>   *                                                       *
>   * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
> 
> 1.4.x:
> 
>   * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
>   *                                                       *
>   *  This release stream has been superceded by 1.X, but  *
>   *  remains open to receive fixes for serious and        *
>   *  security-related bugs.                               *
>   *                                                       *
>   * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
> 
> 1.5.x:
> 
>   * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
>   *                                                       *
>   *  This release stream is open to bug fixes.            *
>   *                                                       *
>   * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
> 
> It's just a tiny little way for folks to quickly know the status of a given
> release stream without doing version arithmetic and being aware of our
> 2-streams-open policy or exceptions to it.
> 
> Thoughts?
> 
> 

Perhaps also mention the expected change to the status:

    This release stream is open to bug fixes.  When 1.Y.0 is released,
    this stream will be closed to any changes except security-related
    bugs.

    This release stream is open for serious and security-related bugs
    only.  This stream will be closed to any changes on January 1.



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org