Re: versioning & release schedule
Doug Alcorn (alcornd@earthlink.net)
11 Dec 1998 17:02:17 -0500
--Multipart_Fri_Dec_11_17:02:16_1998-1
Content-Type: text/plain; charset=US-ASCII
--
(__) Doug Alcorn
oo ) alcornd@earthlink.net
|_/\
--Multipart_Fri_Dec_11_17:02:16_1998-1
Content-Type: message/rfc822
To: Ethan <allanon@crystaltokyo.com>
Cc: AS Team -- Andrew Sullivan <asullivan@sprint.ca>,
David Mihm <davemann@ionet.net>,
Michal Vitecek <fuf@fuf.sh.cvut.cz>,
Guylhem Aznar <guylhem@oeil.qc.ca>,
Sasha Vasko <Sasha_Vasko@osca.state.mo.us>, sashav@sprintmail.com,
Albert Dorofeev <albert@mail.dma.be>
Subject: Re: versioning & release schedule
References: <Pine.LNX.3.95.981211132158.10633G-100000@crystaltokyo.com>
Mime-Version: 1.0 (generated by tm-edit 7.108)
Content-Type: text/plain; charset=US-ASCII
From: Doug Alcorn <alcornd@earthlink.net>
Date: 11 Dec 1998 16:44:43 -0500
Message-ID: <m3u2z2mjzo.fsf@trident.sonoco.com>
Ethan <allanon@crystaltokyo.com> writes:
> Since there shouldn't be many patches, I suggest we release a new version
> whenever we have a new patch, increment the patchlevel (1.6.x, x ==
> patchlevel), and make a tarball of the new version available on f.a.o, as
> well as the patch. Since the tarballs take a lot of space, I also suggest
> we remove intermediate versions. ie, keep 1.6.0 and the latest 1.6.x, and
> remove 1.6.1, 1.6.2, ..., 1.6.(x - 1).
I agree with this. However, some more specifics. First, I think we
need dual directories on fao: devel and stable. Then the patches to
1.6.0 should go in stable/patches. Second, in the toplevel dir of
fao put a symlink from AfterStep-current.tar.gz to what ever is the
latest AfterStep-1.6.x-tar.gz in the stable dir.
>
> For the devel tree, at least until we get CVS, patches should be fine,
> with a release schedule somewhat like we've been doing with the betaX's.
>
I agree with this too.
--
(__) Doug Alcorn
oo ) alcornd@earthlink.net
|_/\
--Multipart_Fri_Dec_11_17:02:16_1998-1--