Debian 3.0 and release goals
-----BEGIN PGP SIGNED MESSAGE-----
In the release naming thread (I don't know whether it died down
already), there was a mention of 3.0 (right after 2.2, for one).
Now... I know `we'[1] don't want to set hard release goals anymore.
And I agree with that.
Someone (can't remember who) a while back mentioned something similar:
Define release goals for 3.0, and the release that happens to
implement exactly this is automatically named 3.0.
This might be confusing if we plan for an upcoming release 2.5 (or
whatever), which then happens to become 3.0. But since we don't
really do that (we don't think of 2.1, but of slink, right?), it won't
really be.
When we get close to a implementing the stated release goals, we can
hint at it, like "The next release has a good chance of being 3.0."
(This would need an accompanying explanation on the whys and hows, or
a link to such).
Of course, this scheme works for major releases (a different X in X.Y)
only.
Bye, J
[1] I'm not a developer, but I'm identifying with Debian's goals
100%... *and* Debian makes even its users feel very much part of the
community. This list in particular feels like sitting in the offices
at RedHat (for example), listening to shop-talk...
- --
Jürgen A. Erhard eMail: jae@laden.ilk.de phone: (GERMANY) 0721 27326
MARS: http://members.tripod.com/~Juergen_Erhard/mars_index.html
GNU Privacy Guard (http://www.d.shuttle.de/isil/crypt/gnupg.html)
"No matter how cynical I get, I can't keep up." -- Bruce Schneier
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: noconv
Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface
iQEVAwUBNhkqDgIG66LugGzRAQF6jwf/S5muUSSNay97ii2X8c1qFnPHCNT0DIYC
yV6csyT20Hm8EwG/zX171DBurkPEMsCxtQFDPOhjvjjVF0DSO+PKphZSbKfFzEie
5qZmGYW25vsiu8y1eOnwthUu1uEqf3VEVtb6bBA9yFCgcjTsyWC9ys57B2a8L1cZ
YSAqTCyFM4X1Kc7G2e6CWfsLQuubg/OId38G4YetUkBeaqb/CGWbrdyWxB4a6nxL
O4MeCpJhuTvxuz9zqKSgNC/KXanspNwpuYXUSVivkpeJmvLuFDkGXdFhNv5lCX+i
P+93yXyvYTahwsCSZHR99en81bcZBS/tp2eM1RT/FCLTS+oDvKaOyg=27
-----END PGP SIGNATURE-----
Reply to: