Re: Repository and release numbering changes

Chris Pickett wrote:
> My biggest request is that the new trunk keep the same history as
> staging, so that I can easily merge the diff between the last time I
> updated to staging (about 1.1.9) and some arbitrary revision in the future.

It will.

> I think what I'm suggesting would be something like the GCC versioning
> system / development model (x.y.z, x is major version number, y is minor
> version number, z is fixes developed in the highest y (read:
> experimental / moderately unstable new stuff) that get backported to all
> y's since the highest x).  Is this too much work for you to manage?

Chris, I am willing to appoint you as "backport maintainer", if you
accept the job.  (I personally have no time to dedicate to this.)

Etienne

--
Etienne M. Gagnon, Ph.D.            http://www.info2.uqam.ca/~egagnon/
SableVM:                                       http://www.sablevm.org/
SableCC:                                       http://www.sablecc.org/

_______________________________________________
SableVM-devel mailing list
[email protected]
http://sablevm.org/lists/control/listinfo/sablevm-devel

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCNufIjyrJi4rH84gRAhrsAJwLXIFjOtmnoXLuBP80hTQyQjjU+QCfVdLE
xWI1tXJpJUxdwQhLh0bEqsg=
=+xFK
-----END PGP SIGNATURE-----