From: Andrew Cagney <cagney@redhat.com>
To: frysk <frysk@sources.redhat.com>
Subject: meeting 2008-04-02 - versions and releases
Date: Wed, 02 Apr 2008 15:29:00 -0000 [thread overview]
Message-ID: <47F3A633.4000207@redhat.com> (raw)
We discussed versions and releases again; the intent is:
-> the release occurs the first Wednesday of each month:
- Monday/Tuesday do sanity checks and update NEWS
- Wednesday 0:00 GMT is tentative branch date
- Wednesday's meeting we check we're ok; review NEWS; and perhaps add
last minute fixes
-> version
- This release will be version 0.2; the next 0.3; and so on, if we reach
0.9 then it isn't anything special
-> NEWS
- going into the Wednesday meeting; we should add news items, but we'll
use Wednesday to review it
-> this month
We can get news stuff updated today and cut the official branch tonight
next reply other threads:[~2008-04-02 15:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-02 15:29 Andrew Cagney [this message]
2008-04-02 17:24 ` Sami Wagiaalla
2008-04-04 14:47 ` Phil Muldoon
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47F3A633.4000207@redhat.com \
--to=cagney@redhat.com \
--cc=frysk@sources.redhat.com \
/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).