From: Ralf Angeli <angeli@caeruleus.net>
To: Jason Rumney <jasonr@gnu.org>
Cc: Nick Roberts <nickrob@snap.net.nz>,
Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel@gnu.org
Subject: Re: pretest 22.0.100
Date: Thu, 17 May 2007 15:45:09 +0200 [thread overview]
Message-ID: <87abw3tvh6.fsf@neutrino.caeruleus.net> (raw)
In-Reply-To: <464C57DE.2020906@gnu.org> (Jason Rumney's message of "Thu, 17 May 2007 14:25:50 +0100")
* Jason Rumney (2007-05-17) writes:
> After 18.9 came 18.10, likewise with 19.9 and 19.10. There is no good
> reason to change the rules only for pretests.
,----[ http://www.gnu.org/prep/maintain/html_node/Test-Releases.html ]
| In this method, if you are about to release version 4.6 but you want to
| do a pretest first, call it 4.5.90. If you need a second pretest, call
| it 4.5.91, and so on. If you are really unlucky and ten pretests are not
| enough, after 4.5.99 you could advance to 4.5.990 and so on. (You could
| also use 4.5.100, but 990 has the advantage of sorting in the right
| order.)
`----
--
Ralf
next prev parent reply other threads:[~2007-05-17 13:45 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-12 16:47 We can use python.el Richard Stallman
2007-05-12 17:52 ` Chong Yidong
2007-05-12 18:17 ` Juanma Barranquero
2007-05-12 23:03 ` Chong Yidong
2007-05-12 23:36 ` Juanma Barranquero
2007-05-12 23:54 ` Chong Yidong
2007-05-13 1:38 ` Glenn Morris
2007-05-14 8:08 ` Richard Stallman
2007-05-14 8:43 ` Jason Rumney
2007-05-14 14:55 ` Chong Yidong
2007-05-14 17:45 ` Glenn Morris
2007-05-14 18:05 ` Henrik Enberg
2007-05-15 9:47 ` Richard Stallman
2007-05-15 14:11 ` Chong Yidong
2007-05-16 1:39 ` Richard Stallman
2007-05-16 2:51 ` Chong Yidong
2007-05-16 6:02 ` Jan Djärv
2007-05-13 10:33 ` Jason Rumney
2007-05-14 8:09 ` Richard Stallman
2007-05-12 19:02 ` pretest 22.0.100 (was: We can use python.el) Reiner Steib
2007-05-12 22:51 ` pretest 22.0.100 Chong Yidong
2007-05-14 17:01 ` Stefan Monnier
2007-05-14 19:11 ` Juanma Barranquero
2007-05-14 21:26 ` Nick Roberts
2007-05-16 15:48 ` Stefan Monnier
2007-05-17 12:42 ` Andreas Schwab
2007-05-17 12:49 ` Jason Rumney
2007-05-17 13:15 ` David Kastrup
2007-05-17 13:25 ` Jason Rumney
2007-05-17 13:34 ` David Kastrup
2007-05-17 13:45 ` Ralf Angeli [this message]
2007-05-17 13:57 ` Ulrich Mueller
2007-05-17 14:02 ` Alfred M. Szmidt
2007-05-17 13:39 ` Jay Belanger
2007-05-17 14:20 ` Stefan Monnier
2007-05-17 14:32 ` Juanma Barranquero
2007-05-17 16:43 ` Another pretest after 22.0.99 (was: pretest 22.0.100) Reiner Steib
2007-05-13 1:27 ` We can use python.el Michaël Cadilhac
2007-05-14 8:08 ` Richard Stallman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87abw3tvh6.fsf@neutrino.caeruleus.net \
--to=angeli@caeruleus.net \
--cc=emacs-devel@gnu.org \
--cc=jasonr@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=nickrob@snap.net.nz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).