From: Thien-Thi Nguyen <ttn@giblet.glug.org>
Cc: guile-devel@gnu.org
Subject: Re: Release management - take 1
Date: Wed, 24 Apr 2002 10:17:58 -0700 [thread overview]
Message-ID: <E170QP0-00085h-00@giblet> (raw)
In-Reply-To: <87hem1kyh0.fsf@raven.i.defaultvalue.org> (message from Rob Browning on Wed, 24 Apr 2002 08:39:07 -0500)
From: Rob Browning <rlb@defaultvalue.org>
Date: Wed, 24 Apr 2002 08:39:07 -0500
Sounds reasonable -- I've actually had a few false starts on such a
script here -- initially for my own use, but if it ended up being
good enough I had planned to add it to guile.
cool.
I have to say, though that so far I've still been more comfortable
just having the RELEASE list and doing each step by hand, but I agree
that a *good* script would likely be a win, so I'll keep at it.
i'm in parallel writing such a dist-guile (based on dist-guile-www)
aimed for 1.4.1 release (so you see, i'm bugging you to write this stuff
down so that i can follow your lead). it doesn't do all the things in
RELEASE, just the mechanical bits. will probably checkin today.
two weeks is probably better, making sure at least two weekends are
in there for people who need to do the work then.
good point. weekends are quite precious to volunteer efforts.
OK, I'll take my original and your comments and merge these into the
workbook. I may also take your suggestion (in another message) and
make doing this be the resolution to one of the "release critical"
bugs, but I really don't think this should hold up the 1.6.1, since
everyone here involved knows what's going on.
that's wishful thinking. the day everyone knows what's going on, the
universe will blink out of existence. remember that there are lurkers
(reading this) who may become guile maintainers in the future, and
indeed current maintainers (self included) who are depending on you to
do the thinking for them on these matters.
Accordingly I'd like to reserve the right to move the relevant todo
item to being 1.8 release critical if everything else is done, but
let's see how far I get by Monday.
i'm glad to see checkins of process-related docs.
thi
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-04-24 17:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-15 4:31 Release management - take 1 Rob Browning
2002-04-24 5:56 ` Thien-Thi Nguyen
2002-04-24 13:39 ` Rob Browning
2002-04-24 17:17 ` Thien-Thi Nguyen [this message]
2002-05-14 10:59 ` Thien-Thi Nguyen
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E170QP0-00085h-00@giblet \
--to=ttn@giblet.glug.org \
--cc=guile-devel@gnu.org \
--cc=ttn@glug.org \
/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.
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).