From: Dave Chinner <david@fromorbit.com>
To: Ben Myers <bpm@sgi.com>
Cc: rjohnston@sgi.com, sandeen@sandeen.net, xfs@oss.sgi.com
Subject: Re: xfsprogs: update version for 3.2.0-alpha1
Date: Tue, 17 Sep 2013 08:38:55 +1000 [thread overview]
Message-ID: <20130916223855.GF19103@dastard> (raw)
In-Reply-To: <20130916205637.GD1935@sgi.com>
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...
>
> Update the VERSION and doc/CHANGES file for alpha release, 3.2.0-alpha1
>
> Signed-off-by: Ben Myers <bpm@sgi.com>
> Reviewed-by: Rich Johnston <rjohnston@sgi.com>
>
> ---
> VERSION | 4 ++--
> configure.ac | 2 +-
> doc/CHANGES | 4 ++++
> 3 files changed, 7 insertions(+), 3 deletions(-)
>
> Index: b/VERSION
> ===================================================================
> --- a/VERSION 2013-09-16 15:50:29.544368912 -0500
> +++ b/VERSION 2013-09-16 15:50:37.993732514 -0500
> @@ -2,6 +2,6 @@
> # This file is used by configure to get version information
> #
> PKG_MAJOR=3
> -PKG_MINOR=1
> -PKG_REVISION=11
> +PKG_MINOR=2
> +PKG_REVISION=0-alpha1
To make it easy for packaging, 3.99.0 would probably fit better with
various distro package naming/numbering schemes...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-09-16 22:39 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 [this message]
2013-09-18 21:35 ` Eric Sandeen
2013-09-23 12:26 ` Christoph Hellwig
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=20130916223855.GF19103@dastard \
--to=david@fromorbit.com \
--cc=bpm@sgi.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