xfs
[Top] [All Lists]

Re: master branch fast-forwarded to v3.7-rc1, and corp-speak mumble

To: Eric Sandeen <sandeen@xxxxxxxxxxx>
Subject: Re: master branch fast-forwarded to v3.7-rc1, and corp-speak mumble
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Tue, 23 Oct 2012 08:32:19 -0400
Cc: Ben Myers <bpm@xxxxxxx>, xfs@xxxxxxxxxxx
In-reply-to: <507F132B.30000@xxxxxxxxxxx>
References: <20121016155640.GA1377@xxxxxxx> <507F132B.30000@xxxxxxxxxxx>
User-agent: Mutt/1.5.21 (2010-09-15)
On Wed, Oct 17, 2012 at 03:20:59PM -0500, Eric Sandeen wrote:
> Dave had concerns that a regression, which, although quickly fixed, was
> cited as the reason for missing a merge window.
> 
> This concerns me too, because it's not just SGI's timetables that matter
> here; others are also depending on this work getting upstream within certain
> deadlines as well.
> 
> Reading back through the list, I'm alarmed that SGI wants some unspecified
> "soak time," but not upstream, for new work.  There's no better place than
> an -rc1 to get soak & exposure for tested patches.  Bugs get found and fixed.
> I don't think the XFS developer community needs a lecture on patch submission
> processes and quality expectations.

The best place is the for-next branch.  We should aim for getting
patches in early in the window rather than last minute, which is way to
common in XFS land.

<Prev in Thread] Current Thread [Next in Thread>