From: Christoph Hellwig <hch@infradead.org>
To: xfs@oss.sgi.com
Cc: Jakub Bogusz <qboosh@pld-linux.org>
Subject: Re: time for userspace releases?
Date: Fri, 2 Mar 2012 03:41:23 -0500 [thread overview]
Message-ID: <20120302084123.GA19172@infradead.org> (raw)
In-Reply-To: <20120112161227.GA3225@infradead.org>
On Thu, Jan 12, 2012 at 11:12:27AM -0500, Christoph Hellwig wrote:
> [looks like the list manager ate this mail the first time, sorry if
> anyone gets it twice]
>
> We have some important repair fixes pending, as well as major changes
> in xfsdump. Maybe it's time to schedule releases in about two weeks
> and get any outstanding changes in?
We've dragged this out another 1 1/2 month, so let's get the ball
rolling. I'd like to declare today feature and string freeze for
xfsprogs 3.1.8, and once Jakub has sent in the translations get it
out. We should try to get a 3.1.9 out relatively soon after that as
there is lots more repair work pending, as well as the userspace support
for separate group and project quotas. If we aim for a 2 to 3 month
release cycle we should be able to time it for the Linux 3.4 release.
There are no translations for xfsdump, but I'd propose to release it at
the same time. Given the significant changes I think the xfsdump
version should be bumped to 3.1.0.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-03-02 8:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-12 16:12 time for userspace releases? Christoph Hellwig
2012-03-02 8:41 ` Christoph Hellwig [this message]
2012-03-02 10:22 ` Stan Hoeppner
2012-03-02 22:10 ` Eric Sandeen
2012-03-03 20:37 ` Jakub Bogusz
2012-03-04 5:41 ` Christoph Hellwig
2012-03-04 6:37 ` Jakub Bogusz
2012-03-04 6:39 ` Christoph Hellwig
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=20120302084123.GA19172@infradead.org \
--to=hch@infradead.org \
--cc=qboosh@pld-linux.org \
--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