releases and branches (was "0.45.0 Released")

[Antonio Terceiro]

On Tue, Dec 10, 2013 at 04:56:23PM -0300, Rodrigo Souto wrote:
> Since I already talked about the "next" branch, for those who doesn't
> know, we created this branch in the need of reviewing code during the
> freeze. Since it turned out to be a good experience, I decided to make
> it an official branch. So during the development cycles, the "next"
> branch will be just the same as the master branch, but during the freeze
> it'll have new features that are going to the master branch after the
> freeze. (After writing so many "next" with quotes to avoid
> misinterpretations, I'm also starting to consider change this
> name...suggestions?).

I would suggest maybe doing different: instead of freezing master, we
could create a release branch off master at the time of the freeze,
called noosfero_$X_$Y, where the next release would  be noosfero $X.$Y.0
(e.g. "noosfero_0_46" for the next release). Then:

- master stays open to new features. This way we stay consistent with
  "new development always happens on master"

- eventual fixes to the code to be released go into noosfero_$X_$Y

- after the release, bug fixes go into noosfero_$X_$Y (we could drop the
  "stable" branch named as such)

- we can even maintain old noosfero_$X_$Y branches around, so that we
  could find people interested in maintaining older releases in their
  noosfero_$X_$Y branches.

-- 
Antonio Terceiro <terceiro at colivre.coop.br>
Colivre - Cooperativa de Tecnologias Livres
http://www.colivre.coop.br/


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://listas.softwarelivre.org/pipermail/noosfero-dev/attachments/20131210/cdba36c6/attachment.pgp>