Anaconda is totally trashing the F18 schedule (was Re: f18: how to install into a LVM partitions (or RAID))
rwheeler at redhat.com
Wed Oct 31 15:53:51 UTC 2012
On 10/31/2012 11:39 AM, Eric Sandeen wrote:
> On 10/31/12 10:20 AM, "Jóhann B. Guðmundsson" wrote:
>> On 10/31/2012 02:57 PM, Ric Wheeler wrote:
>>> A good place to see a summary of the broad community work is the annual Linux Storage and File System Workshop (LSF). You can google for the recent notes, usually well covered on LWN.net.
>>> The most general list and lowest traffic is: linux-fsdevel at vger.kernel.org
>>> MD team list is: linux-raid at vger.kernel.org
>>> The device mapper team list is: dm-devel at redhat.com
>>> Each local file system has its list:
>>> xfs at oss.sgi.com
>>> linux-btrfs at vger.kernel.org
>>> linux-nfs at vger.kernel.org
>>> linux-ext4 at vger.kernel.org
>>> SCSI issues are:
>>> linux-scsi at vger.kernel.org
>>> S-ATA issues are:
>>> linux-ide at vger.kernel.org
>> These are all upstream mailing list none specific to the distribution
>> so perhaps it's time for you guys within the Fedora distribution to
>> unite under such list so other developers, user and alike can contact
>> you and other interested parties that might be subscribed to that
>> list with heads up for changes like the one that Anaconda made...
> It might be useful to have a storage list for Fedora, but I'm on the
> I'm on fedora-devel, fedora-kernel, and the anaconda lists already.
> I'm in #fedora-devel, #fedora-kernel, and #anaconda on IRC too.
> It's not clear to me that the root cause for low communication on this
> change was "too few lists."
> Now that I've actively searched for it, I do find, deep in a thread
> about "partitioning expectations for F18," a tester who was surprised
> by the change back in August. The surprise makes me think it probably
> wasn't well communicated to anyone, originally. For example, not
> communicated to the fedora test lists, even though they existed.
> (I'm not on _that_ list, so if I'm wrong, please forgive me).
> I also found your "Does this mean we can ( finally ) disable lvm and
> related services by default" comment in that thread, which gives me a
> little better context for your passion on this topic. ;)
Maybe having a fedora specific file & storage, low traffic list would be a great
way to get focused, cross team exchanges.
I certainly have enough email to drown in, but this could be actually a positive
More information about the devel