[Bf-committers] 2.6 Release Cycle Proposal

[Knapp]

On 7/29/11, Sergey I. Sharybin <g.ulairi at gmail.com> wrote:
> Hi,
>
> I'll agree with Campbell. It'll be more convenient for some developers
> (for example, me).
>
> This even can work in such way:
> - Trunk is never frozen
> - Two weeks before release we create new branch (or replacing branch
> from previous release).
> - In trunk usual work could happen.
> - In that separated branch last changes, fixes, stabilization, blah blah
> happens.
> - Some individual fixes can be merged from trunk to that pre-release branch.
> - After release tagging happens based on that pre-release branch.
>
> It's just idea.
>
> And about proposal. It can't totally get us free from corrective
> releases, imo. Sometimes we're updating libraries and time to time
> errors happens when preparing new libraries -- wrong configuration,
> wrong compilation flag, forgotten feature to be included. Such things
> can be handled by corrective releases, but maybe someone got better
> ideas to handle such kind of problems?

This is not my area but is that not what alpha and beta releases are for?

-- 
Douglas E Knapp

Creative Commons Film Group, Helping people make open source movies
with open source software!
http://douglas.bespin.org/CommonsFilmGroup/phpBB3/index.php

Massage in Gelsenkirchen-Buer:
http://douglas.bespin.org/tcm/ztab1.htm
Please link to me and trade links with me!

Open Source Sci-Fi mmoRPG Game project.
http://sf-journey-creations.wikispot.org/Front_Page
http://code.google.com/p/perspectiveproject/