From: Christoph Hellwig <hch@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: sandeen@sandeen.net, Ben Myers <bpm@sgi.com>,
rjohnston@sgi.com, xfs@oss.sgi.com
Subject: Re: xfsprogs: update version for 3.2.0-alpha1
Date: Mon, 23 Sep 2013 05:26:23 -0700 [thread overview]
Message-ID: <20130923122623.GA2199@infradead.org> (raw)
In-Reply-To: <20130916223855.GF19103@dastard>
On Tue, Sep 17, 2013 at 08:38:55AM +1000, Dave Chinner wrote:
> On Mon, Sep 16, 2013 at 03:56:37PM -0500, Ben Myers wrote:
> > xfsprogs: update version for 3.2.0-alpha1
>
> I'd say this is a major feature and infrastructure
> update across the entire xfsprogs package, and in that case a
> PKG_MAJOR bump is warranted, not PKG_MINOR.
>
> i.e. We're shooting for a 4.0 release, not 3.2...
I tend to disagree with the 4.0 bump.
2.0 was when the new xattr ABI was introduced, and 3.0 was when we
pulled fsr over from xfsdump to xfsprogs as well as drastically reducing
the amount of installed headers.
While the v5 support is a major internal change I think 3.2 would fit
better for this.
I'd also be tempted to just cut 3.2.0 instead of an alpha version - just
keep the v5 support experimental, maybe under a configure option.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-09-23 12:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-16 20:56 xfsprogs: update version for 3.2.0-alpha1 Ben Myers
2013-09-16 22:03 ` Eric Sandeen
2013-09-16 22:38 ` Dave Chinner
2013-09-18 21:35 ` Eric Sandeen
2013-09-23 12:26 ` Christoph Hellwig [this message]
2013-09-23 14:04 ` Eric Sandeen
2013-09-23 15:07 ` Ben Myers
2013-09-23 15:09 ` Eric Sandeen
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=20130923122623.GA2199@infradead.org \
--to=hch@infradead.org \
--cc=bpm@sgi.com \
--cc=david@fromorbit.com \
--cc=rjohnston@sgi.com \
--cc=sandeen@sandeen.net \
--cc=xfs@oss.sgi.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