linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Alasdair G Kergon <agk@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] LVM2 release 2.02.03 / device-mapper 1.02.04
Date: Wed, 19 Apr 2006 17:23:23 +0100	[thread overview]
Message-ID: <20060419162323.GC24520@agk.surrey.redhat.com> (raw)
In-Reply-To: <BAY118-F337680DC84BF4A3A2F9875AFC70@phx.gbl>

On Tue, Apr 18, 2006 at 06:28:46AM +0700, Alexey Shinkin wrote:
> And both are still "development" , not "stable" ?
> What is criteria of "stability" and do you plan to release stable versions ?

The labelling is like a 'release candidate' process: if no significant
problems reveal themselves with a particular release after a
reasonable amount of time, and I believe it is at least as 'stable' as
the existing release labelled 'stable', I'll move the label forward.

None of the lvm2 2.02 releases so far deserved that label - there was
some problem or other with each of them.  With the current release,
I think we're quite close now.

> And how stable are versions that included in RedHat/Fedora Core 
> distributions ?

RHEL aims at stability and so takes bug fixes more quickly than it
takes enhancements and other changes.

Fedora tracks upstream development more closely.

Alasdair
-- 
agk@redhat.com

  reply	other threads:[~2006-04-19 16:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-14 21:43 [linux-lvm] LVM2 release 2.02.03 / device-mapper 1.02.04 Alasdair G Kergon
2006-04-17 23:28 ` Alexey Shinkin
2006-04-19 16:23   ` Alasdair G Kergon [this message]
2006-04-20 20:25 ` Simone Gotti
2006-04-21 14:25   ` Eric Edgar
2006-04-21 14:45     ` Old Fart
2006-04-21 14:53       ` Alasdair G Kergon
2006-04-21 15:13         ` Simone Gotti

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=20060419162323.GC24520@agk.surrey.redhat.com \
    --to=agk@redhat.com \
    --cc=linux-lvm@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 NNTP newsgroup(s).