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

[Grzegorz B. P. <ga...@de...>]

W li=B6cie z sob, 14-02-2004, godz. 12:30, Chris Pickett pisze:=20
> Grzegorz B. Prokopski wrote:
> > Hi all!
> >=20
> > Shortly.
> > - Take a look at http://devel.sablevm.org/wiki/ReleaseProcess
> > That's more less what I had in mind. Comments?
> >=20
> > - staging has now version '1.0.9+staging' - it should be less confusi=
ng
> > (we'll make it 1.1.0+staging after 1.1.0 release, I guess).
>=20
> Seems okay.  Except that staging changes frequently, so I suspect that=20
> when the version really does matter, we'll end up referring to it by=20
> revision number (e.g. staging-r1575).  I'm not even sure if `1.0.9' or=20
> `1.1.0' is necessary in the name ... isn't it just obvious that staging=
=20
> is changes against bugfree at all times, which in turn is changes=20
> against the latest release?  Then we never have to worry about naming=20
> the staging version.  Similarly for sandboxes (my version is `chris')=20
> and bugfree.  I don't know ... it's not a big deal.

I tried to use the subversion's magic string substitution or even the
svnversion utility to put the revision number there, but I am afraid
it can't be done easily, unless we want to generate configure.ac from
some other file or sth. like that (hmm... maybe use sed and generate
it from itself in ./autogen.sh and on make dist? feel free to try it!)

But I am sure staging shouldn't claim to be just "1.0.9" or any other
release. I wanted to put "staging" name initialy, but I guess
"1.0.9+staging" or (hopefuly soon) "1.1.0+staging" should at least give
some more informations if we ask a user to do 'sablevm -V' for us.

> I think staging needs to be frozen with respect to SableVM functionalit=
y=20
> once the regression tests have started until the big merge into bugfree=
=20
> is made.  But then I don't know -- do you want critical fixes to bugfre=
e=20
I agree. You should go and modify ReleaseProcess wiki page w/ this info.
Other ideas/improvements are also appreciated. I tried to make it more
a "checklist" so that we didn't forget about anything, and a guideline.

Cheers,

					GBP

--=20
Grzegorz B. Prokopski <ga...@de...>
Debian GNU/Linux      http://www.debian.org
SableVM - LGPLed JVM  http://www.sablevm.org
Why SableVM ?!?       http://devel.sablevm.org/wiki/WhySableVM