New release schedule proposal

[Rodrigo Souto]

Hey there Braulio,

I think the code reviewing process should happen all the way through the
release instead of a specific time. It would be specially good if all
the community engaged on the review process. About the time for user
tests, it should happen after the RC1 release, where the test package is
uploaded to the test repository and then we would update our alpha
server with it so that everyone can test it in a "production" (on a
rails sense) environment.

Bráulio Bhavamitra escreveu isso ai:
> Yesterday on the noosfero community meeting it was discussed about
> inserting into the release schedule a time for a list of testers and code
> reviewers to work.
> 
> I've just replied Terceiro's comments about this on
> http://listas.softwarelivre.org/pipermail/noosfero-dev/2013-August/000443.html
> .
> 
> best regards,
> bráulio
> 
> 
> On Fri, Aug 9, 2013 at 2:41 PM, Rodrigo Souto <rodrigo at colivre.coop.br>wrote:
> 
> > Hello everybody,
> >
> > In the last versions, we've being observing a reasonable decrease in the
> > quality of our releases specially related to code stability. After some
> > discussions inside Colivre, we concluded some points that most probably
> > are contributing to this problem:
> >     * Rushed releases
> >     * Variable release intervals
> >     * Small release testing time
> >
> > So to solve this problems, we worked to create a proposal of a new
> > release schedule in order to solve this problems and we'd like everyone
> > to contribute to it. After the discussion the content of the proposal
> > will be formated properly and included on our wiki page. Here it follows:
> >
> > ==
> >
> > ---++ Proposal
> >
> > 1. Fixed new features release time of 3 months. Changes in this time
> > should not be negotiable (after defined here) in order to maintain
> > stability.
> >
> > 2. Inclusion of RC1 and RC2 versions in the official schedule.
> >
> > ---++ Definitions
> >
> >    * RC1: First release candidate version
> >       * No new feature will be accepted after this version
> >       * Package released in the test repository
> >       * Conclusion of release notes
> >    * RC2: Second release candidate version
> >       * May be released only if necessary
> >       * Package released in the test repository
> >       * Contain fixes for the features on RC1
> >
> > ---++ Schedule
> >
> > After 2 months and 2 weeks from the release start:
> >
> > Day 0: RC1 Release
> > Day 0 + 1 week: RC2 Release (if necessary)
> > Day 0 + 2 weeks: Final Release
> >
> > ---++ Exceptions
> >
> > If needed, there might be alpha and beta releases before the RC1 in
> > order to test features that are too big or too dangerous! Between these
> > alpha and beta releases and the RC1 there might be new features
> > inclusions.
> >
> > --
> > Rodrigo Souto <rodrigo at colivre.coop.br> :: 55 71 8131-7714
> > Colivre - Cooperativa de Tecnologias Livres
> > http://www.colivre.coop.br/
> >
> > _______________________________________________
> > Noosfero-dev mailing list
> > Noosfero-dev at listas.softwarelivre.org
> > http://listas.softwarelivre.org/cgi-bin/mailman/listinfo/noosfero-dev
> >
> >
> 
> 
> -- 
> "Lute pela sua ideologia. Seja um com sua ideologia. Viva pela sua
> ideologia. Morra por sua ideologia" P.R. Sarkar
> 
> EITA - Educação, Informação e Tecnologias para Autogestão
> http://cirandas.net/brauliobo
> http://eita.org.br

> _______________________________________________
> Noosfero-dev mailing list
> Noosfero-dev at listas.softwarelivre.org
> http://listas.softwarelivre.org/cgi-bin/mailman/listinfo/noosfero-dev


-- 
Rodrigo Souto <rodrigo at colivre.coop.br> :: 55 71 8131-7714
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: 490 bytes
Desc: Digital signature
URL: <http://listas.softwarelivre.org/pipermail/noosfero-dev/attachments/20130813/94d69e2b/attachment.pgp>