* [PATCH] xfstests: prepare for marking an initial versioned release
@ 2011-10-05 22:43 Alex Elder
2011-10-06 19:52 ` Christoph Hellwig
0 siblings, 1 reply; 4+ messages in thread
From: Alex Elder @ 2011-10-05 22:43 UTC (permalink / raw)
To: xfs
I would like to start marking versioned releases of xfstests. The
following adds the release script used in the other XFS user space
packages. I have arbitrarily set the version to 3.0.0 to make it
more in line with the other XFS user space packages as well. I
created an initial CHANGES file with a simple summary of some
recently-added tests.
Signed-off-by: Alex Elder <aelder@sgi.com>
---
VERSION | 2 +-
doc/CHANGES | 21 +++++++++++++++++++++
release.sh | 25 +++++++++++++++++++++++++
3 files changed, 47 insertions(+), 1 deletion(-)
Index: b/VERSION
===================================================================
--- a/VERSION
+++ b/VERSION
@@ -1,7 +1,7 @@
#
# This file is used by configure to get version information
#
-PKG_MAJOR=1
+PKG_MAJOR=3
PKG_MINOR=0
PKG_REVISION=0
PKG_BUILD=1
Index: b/doc/CHANGES
===================================================================
--- /dev/null
+++ b/doc/CHANGES
@@ -0,0 +1,21 @@
+
+xfstests-3.0.0 (5 October 2011)
+ - This is the first versioned release recorded for the
+ xfstests suite. Tests 240-262 have been added to the
+ suite (to date) in 2011.
+ - Here are some one-line summaries for some recently-added
+ tests:
+ - 250: bmap BTREE corruption regression
+ - 251: concurrent FITRIM operations
+ - 252: fallocate hole punching
+ - 253: xfs_db metadump filename obfuscation
+ - 254: btrfs subvolume and snapshot
+ - 255: generic fallocate hole punching
+ - 256: full filesystem hole punching
+ - 257: getdents64() returning usable d_off values
+ - 258: file timestamps prior to the epoch
+ - 259: filesystem creation on just under 4TB storage
+ - 260: FITRIM argument handling
+ - 261: libxcmd giving up on bogus mtab entry
+ - 262: quota reporting doubled project quota values
+
Index: b/release.sh
===================================================================
--- /dev/null
+++ b/release.sh
@@ -0,0 +1,25 @@
+#!/bin/bash
+#
+# Automate generation a new release
+#
+
+. ./VERSION
+
+version=${PKG_MAJOR}.${PKG_MINOR}.${PKG_REVISION}
+date=`date +"%-d %B %Y"`
+
+echo "Updating CHANGES"
+sed -e "s/${version}.*/${version} (${date})/" doc/CHANGES > doc/CHANGES.tmp && \
+ mv doc/CHANGES.tmp doc/CHANGES
+
+echo "Commiting CHANGES update to git"
+git commit -s -a -m "${version} release"
+
+echo "Tagging git repository"
+git tag -s -a -m "${version} release" v${version}
+
+# echo "Creating source tarball"
+# make dist
+
+echo "Done."
+echo "Please remember to push out tags using \"git push --tags\""
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: [PATCH] xfstests: prepare for marking an initial versioned release
2011-10-05 22:43 [PATCH] xfstests: prepare for marking an initial versioned release Alex Elder
@ 2011-10-06 19:52 ` Christoph Hellwig
2011-10-06 20:03 ` Alex Elder
0 siblings, 1 reply; 4+ messages in thread
From: Christoph Hellwig @ 2011-10-06 19:52 UTC (permalink / raw)
To: Alex Elder; +Cc: xfs
On Wed, Oct 05, 2011 at 05:43:11PM -0500, Alex Elder wrote:
> I would like to start marking versioned releases of xfstests. The
> following adds the release script used in the other XFS user space
> packages. I have arbitrarily set the version to 3.0.0 to make it
> more in line with the other XFS user space packages as well. I
> created an initial CHANGES file with a simple summary of some
> recently-added tests.
Whye the bump to 3.x?
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH] xfstests: prepare for marking an initial versioned release
2011-10-06 19:52 ` Christoph Hellwig
@ 2011-10-06 20:03 ` Alex Elder
2011-10-10 16:29 ` Christoph Hellwig
0 siblings, 1 reply; 4+ messages in thread
From: Alex Elder @ 2011-10-06 20:03 UTC (permalink / raw)
To: Christoph Hellwig; +Cc: xfs
On Thu, 2011-10-06 at 15:52 -0400, Christoph Hellwig wrote:
> On Wed, Oct 05, 2011 at 05:43:11PM -0500, Alex Elder wrote:
> > I would like to start marking versioned releases of xfstests. The
> > following adds the release script used in the other XFS user space
> > packages. I have arbitrarily set the version to 3.0.0 to make it
> > more in line with the other XFS user space packages as well. I
> > created an initial CHANGES file with a simple summary of some
> > recently-added tests.
>
> Whye the bump to 3.x?
Like I said, it was somewhat just to align it better with
the other XFS user space packages. One could also think
about lining it up with kernel versions as well, and we
could plan on releasing a new edition of xfstests roughly
corresponding with the Linux releases.
But it really is arbitrary, and if you have a reason to
use something else, great, we'll use it. If not, it
doesn't much matter.
-Alex
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH] xfstests: prepare for marking an initial versioned release
2011-10-06 20:03 ` Alex Elder
@ 2011-10-10 16:29 ` Christoph Hellwig
0 siblings, 0 replies; 4+ messages in thread
From: Christoph Hellwig @ 2011-10-10 16:29 UTC (permalink / raw)
To: Alex Elder; +Cc: Christoph Hellwig, xfs
On Thu, Oct 06, 2011 at 03:03:14PM -0500, Alex Elder wrote:
> > On Wed, Oct 05, 2011 at 05:43:11PM -0500, Alex Elder wrote:
> > > I would like to start marking versioned releases of xfstests. The
> > > following adds the release script used in the other XFS user space
> > > packages. I have arbitrarily set the version to 3.0.0 to make it
> > > more in line with the other XFS user space packages as well. I
> > > created an initial CHANGES file with a simple summary of some
> > > recently-added tests.
> >
> > Whye the bump to 3.x?
>
> Like I said, it was somewhat just to align it better with
> the other XFS user space packages. One could also think
> about lining it up with kernel versions as well, and we
> could plan on releasing a new edition of xfstests roughly
> corresponding with the Linux releases.
>
> But it really is arbitrary, and if you have a reason to
> use something else, great, we'll use it. If not, it
> doesn't much matter.
I don't really care that much, but doing a 1.0 release for the first
public release is what I'd expect. To be honest until it is in a shape
where it can nicely packaged (e.g. different directory for operations
vs source code/scripts) I'm not even sure it warrants 1.0 and shouldn't
be 0.1 intead.
>
> -Alex
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
---end quoted text---
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2011-10-10 16:29 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-10-05 22:43 [PATCH] xfstests: prepare for marking an initial versioned release Alex Elder
2011-10-06 19:52 ` Christoph Hellwig
2011-10-06 20:03 ` Alex Elder
2011-10-10 16:29 ` Christoph Hellwig
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox