From: Sami Wagiaalla <swagiaal@redhat.com>
To: Phil Muldoon <pmuldoon@redhat.com>
Cc: Andrew Cagney <cagney@redhat.com>, frysk <frysk@sources.redhat.com>
Subject: Re: meeting 2008-03-19 - version numbers
Date: Tue, 01 Apr 2008 21:13:00 -0000 [thread overview]
Message-ID: <47F2A55A.70205@redhat.com> (raw)
In-Reply-To: <47E13868.7060507@redhat.com>
>> b) move to regular (monthly?) patch-level releases; e.g., 0.8.1,
>> 0.8.2, ...
> I've no objections to this. But:
>
> - What release schedule? Weekly? Monthly?
I propose:
- monthly releases with news items.
- We create a NEWS file that we dump every release.
>
> - How will we be smoke testing the results to ensure sanity (ie the last
> patch pushed screwed some stuff up). Our test cases can catch a lot of
> this? What is the release checklist?
>
We make sure all the tests pass, and add tests are user report problems.
We can also push a package to updates testing test it for a week then
move it. Although I personally prefer the smoke test it and get it out
there ASAP approach.
> - Because we are moving to a more formal release deadline, how do
> development practices change, if at all?
>
I dont know. Depends on what is motivating this change and what options
we have to solve it.
> - What is our release matrix. Fedora 8 now, and Rawhide. But will it
> then be F8, F9 and rawhide all in sync? Will the release be to rawhide
> first, then a monthly push from rawhide to Fedora *?
>
We are a young project so we want to stay agile as much as possible. So
I suggest we release to rawhide and the latest fedora.
> - How can we detect regressions in stability and features
>
Tests, and users(frysk team ? :))
prev parent reply other threads:[~2008-04-01 21:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-19 15:11 Andrew Cagney
2008-03-19 16:00 ` Andrew Cagney
2008-03-19 16:00 ` Phil Muldoon
2008-03-26 11:53 ` Mark Wielaard
2008-04-01 21:13 ` Sami Wagiaalla [this message]
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=47F2A55A.70205@redhat.com \
--to=swagiaal@redhat.com \
--cc=cagney@redhat.com \
--cc=frysk@sources.redhat.com \
--cc=pmuldoon@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).