On 4 October 2016 at 13:59, Josh Berkus <jberkus(a)redhat.com> wrote:
On 10/04/2016 08:13 AM, Colin Walters wrote:
>
> On Tue, Oct 4, 2016, at 09:46 AM, Paul W. Frields wrote:
>> >
>> > I think mattdm would agree we don't want to potentially,
>> > *indefinitely* block a six-month release with a deliverable that can
>> > be fixed and re-released in two weeks.
> It's not that simple - this is a messy topic. What I think this
> is about isn't delaying or blocking - it's *prioritization*. If
> an issue comes up in Anaconda or systemd or whatever
> that affects the "next AH", we need those teams to priortize
> those fixes the same as they do for Workstation or Server.
Yes, this is exactly the problem I'm raising. We've had an issue with
F25-base Atomic not booting for a couple weeks now, and until the last
couple of days, nobody has been working on it. It seems to be a simple
fact of the Fedora release cycle that if something isn't
release-blocking, it doesn't get done. This isn't new, it's an issue
which has plagued Fedora Atomic for, as far as I can tell, its entire
existence.
The corollary is that if the people who are supposed to be working and
caring for an edition are not doing the work already, making it
release blocking doesn't magically fix it. What happens instead is
that people who are doing that work on other editions have to add this
to their last dash get it across the line.
If people aren't all that interested in a Fedora Cloud or Fedora
Atomic it would be better that the resources were spent where they
could be concentrated. I say this with the same view towards Fedora
Server or Fedora <fill in any arch but x86_64>. If all we are doing is
making it so people not really interested in it HAVE to carry it
onward then it is a worse failure than saying "we would have been
better off in Arch or Madreia or Ubuntu Atomic" because we will have
lost all four F's. People won't be having Fun, they won't have
Freedom, they won't be Friends because of bitterness, and it will all
build up to make sure nothing is 'First'. If that means that all we
do is build a couple of desktop distros then so be it.. at least
people will be working on something that meets those 4 Fs.
And, like I said, this also ties into the F25 cycle
getfedora.org
redesign. We simply can't go ahead with a redesign which emphasizes
Atomic over the cloud base image if F25-base Atomic isn't ready at
release time. We'll have to hold that back, and that's something the
design team needs to know.
--
--
Josh Berkus
Project Atomic
Red Hat OSAS
_______________________________________________
cloud mailing list -- cloud(a)lists.fedoraproject.org
To unsubscribe send an email to cloud-leave(a)lists.fedoraproject.org
--
Stephen J Smoogen.