Public SourceMage Discussion List

[Benoit PAPILLAULT <benoit.papillault AT sourcemage.org>]

Seth Alan Woolley a écrit :
> === stable grimoire updating process ===
>
> We have three main grimoires, devel, test, and stable:
>
>   * devel contains all spells plus works-in-progress, identified by a 
>     WIP file in them.
>
>   * test contains all spells that should work but haven't had gauranteed 
>     testing.  The guru's intent is that, yes, this spell, to the best of 
>     my knowledge, will work as well as the previous versions.  If not, 
>     it goes in devel with a WIP.
>
>   * stable should have been well-tested.

This definition of stable is not quite clear, even if you describe it 
later in more details.

> === stable grimoire versioning ===
>
> To better track issues, the stable grimoire should have versions.  They 
> will be done like so:
>
> There will be three parts to the stable grimoire version:
>
>   * MAJOR VERSION: This shall be "0" at first, and changed only for 
>     major ISO releases.
>   
>   * MINOR VERSION: This shall be incremented, starting at "0", for each 
>     stable release between ISO releases.
>   
>   * REVISION: This shall be incremented whenever security updates or 
>     major bugfixes are integrated into stable grimoire between QA declares 
>     the release official.  It starts at zero.
>
> Each version number shall reset all inferior version numbers when they 
> are incremented.
>
> We will start at 0.0.0 stable release (I know, cool).  When a security 
> update is applied, it shall be 0.0.1.  When a stable-rc is made stable, 
> it will be 0.1.0, and a security update on that would be 0.1.1, and so 
> on, until the next ISO is released, which will make it 1.0.0.

I don't see the relationship between ISO release number and stable 
grimoire release version. Is that a way to know which grimoire version 
has been used for building the ISO?

BTW, does this mean that we will be able to "scribe add stable-rc" ?

> === ISO release process ===
>
> To better follow ISO development, the ISO process itself will be 
> recreated for each stable grimoire release.  If there are any major 
> issues with the ISO after one week of testing, it will continue with -rc 
> status.  So all ISOs will have -rc designation at first.  When no known 
> bugs exist for the ISO, it will be released as -rc still and aliased as 
> a major stable ISO after one week of community testing with no 
> additional bug reports and a release notes list of issues that are 
> acceptable to the QA TL, the ISO TL, and the PL, the PL of course able 
> to override any decision here.

I really like to have the ISO build process fully automated to be able 
to run it once a week for instance. However, right now, we have not 
reached this level yet :-(

Two points:

* ISO already has a naming scheme. This currently does not include "-rc" 
stuff. See http://wiki.sourcemage.org/index.php?page=ISO+numbering+scheme

* I don't like the "one week of testing" delay. One week can last and no 
one would have tested the ISO. I would replace it by "one successfull 
installation report (report yes, saying "it works" is not enought) + no 
bug reported after one week".

Another question about stable grimoire bugs: you should add a rule in 
your process where bugs reported on the stable grimoire should be fixed 
in the stable grimoire as well. This rule should be included in your QA 
process because fixing stable grimoire bugs should not make the stable 
grimoire worse.

With our current usage of bugzilla, the bug is marked FIXED whenever 
it's fixed in devel and integrated into test, EVEN if the initial bug 
has been reported on the stable grimoire. As our QA Lead, i'll let you 
elaborate on that...

Benoit PAPILLAULT, ISO guru