Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
RE: Feature freeze for 3.1.6? RE: pws-24
- X-seq: zsh-workers 6895
- From: "Andrej Borsenkow" <Andrej.Borsenkow@xxxxxxxxxxxxxx>
- To: "Peter Stephenson" <pws@xxxxxxxxxxxxxxxxx>, "Zsh hackers list" <zsh-workers@xxxxxxxxxxxxxx>
- Subject: RE: Feature freeze for 3.1.6? RE: pws-24
- Date: Mon, 28 Jun 1999 14:44:22 +0400
- Importance: Normal
- In-reply-to: <9906281002.AA40261@xxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm
>
> You're right that 3.1.5 and 3.1.6 don't look much alike. However, I want 4
> to be a non-beta release from the word go (ideally with not many major
> changes from `3.1.6', but that will depend how things go), and I'd like to
> stick to the convention that all `proper' releases are just X.Y, with extra
> tags only for intermediate (non-released) versions. How about something
> like 3.1.99? or even 3.99? or something?
>
If I remember correctly, when 3.0.0 came to life it was settled on a "Linux
versioning": x.y.z is a development release for odd y, and stable for even y,
with z being bug fix release. And major number (x) is incremented at your
discretion :-)
The vital point is, that 3.1.6 is just a bug fix in this scheme ... and more
than a year for a bug fix is certainly too much :-)
Related theme: what about public CVS for Zsh? In this case it won't suffer as
much from maintainer change and there will be no need for pws-NN releases any
more (as much as I like them :-) Is it possible to host Zsh source tree on
sunsite.auc.dk?
/andrej
Messages sorted by:
Reverse Date,
Date,
Thread,
Author