[Live-demo] Release Candidate Soon

[Alex Mandel]

RC1 was just an error on my part realized after the build had started,
hence the reversion to beta after that. The current RC numbering was to
ensure that post documentation freeze could not be confused with the
mislabed RC1/beta1. Normally I would have done RC1 after the doc freeze.

While I agree in principal here is how I see the naming:
alpha
Feature Freeze
beta
Documentation Freeze
rc

Theoretically after the Documentation Freeze the disc should be solid
and considered an RC, this time around has seen way too much action for
my comfort so close to release, though quite necessary. But according to
our schedule we are already into RC territory and I see no reason to not
continue the numbering increment, since it will provide continuity.
I believe changing the name now to anything other than final will just
confuse people later.

A noted exception, if we do start translating at some point that be
gamma(or still beta) between Doc Freeze and translation Freeze.

Thanks,
Alex

On 08/02/2010 09:19 AM, Brian Hamlin wrote:
> Hi All-
> 
>   First and foremost, this is a great moment for the LiveDVD project
> OSGeo projects have really come together, and thanks to the solid
> docs framework, this will be the most informative and professionally
> presented version yet. Excellent!
> 
>  A note on the build naming..
> In many years of writing shrinkwrap software in the pre-Internet days
> I have come across a few conventions for the basic terms
>   alpha, beta, release candidate, golden master, etc..
> 
> I think we got off on the wrong foot calling the last couple of builds
> RC-N  for release candidate.. its really not the right use of the term.
> 
> often, beta means "feature complete", while
> Release Candidate means what it sounds like, everything is in place
> for a final build and that iteration is done soley to correct important
> defects..
> 
> I suggest that we return to this convention for this important OSGeo
> product
> Since the letters 'rc' have already been used, we might consider a
> variation on the spelling to avoid a muddy history. or not, since the final
> of this process will really be its own piece of history..
> 
> I write this wordy email now because I really do think its worthwhile to
> get
> back on track with a solid naming convention, to match the solid work that
> has gone into this fine product.
> 
>   best regards
>    -Brian
> 
> ==
> Brian Hamlin
> planetwork.net
> OSGeo California Chapter
> (415) 717-4462 cell
> 
> _______________________________________________
> Live-demo mailing list
> Live-demo at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/live-demo
> http://wiki.osgeo.org/wiki/Live_GIS_Disc