Re: [Sablevm-developer] Release progress - problems w/ 'make distcheck' of classpath

[Chris P. <chr...@ma...>]

Grzegorz B. Prokopski wrote:
> Hi all!
> 
> Shortly.
> - Take a look at http://devel.sablevm.org/wiki/ReleaseProcess
> That's more less what I had in mind. Comments?
> 
> - staging has now version '1.0.9+staging' - it should be less confusing
> (we'll make it 1.1.0+staging after 1.1.0 release, I guess).

Seems okay.  Except that staging changes frequently, so I suspect that 
when the version really does matter, we'll end up referring to it by 
revision number (e.g. staging-r1575).  I'm not even sure if `1.0.9' or 
`1.1.0' is necessary in the name ... isn't it just obvious that staging 
is changes against bugfree at all times, which in turn is changes 
against the latest release?  Then we never have to worry about naming 
the staging version.  Similarly for sandboxes (my version is `chris') 
and bugfree.  I don't know ... it's not a big deal.

I think staging needs to be frozen with respect to SableVM functionality 
once the regression tests have started until the big merge into bugfree 
is made.  But then I don't know -- do you want critical fixes to bugfree 
to happen on bugfree directly, and flow back into staging (or rather, be 
committed at the same time)?  Because if not, it seems better to keep 
staging frozen until the actual release tag is made (I think freezing 
for the shortest amount of time is best).

Anyway, whatever.  In practice there are only a handful of developers, 
so it's not mission-critical whatever you do.  The time spent figuring 
these things out and documenting them can offset the actual benefits.

Chris