Hi Desktop/Workstation team,
as we are moving forward with Fedora 26 I would like to make sure we have all the deliverables, which might or might not be blocking for the release, identified on time. As such, I would like to ask you to review the list of deliverables the Desktop/Workstation team delivers for Fedora 26 release. The list is available on https://fedoraproject.org/wiki/Fedora_Program_Management/ReleaseBlocking/Fed... .
In case you find any discrepancy in the list, feel free to correct it or let me know and I will correct it then.
Thanks for your help and Best Regards, Jan
On Thu, Jan 12, 2017 at 11:43:58AM +0100, Jan Kurik wrote:
Hi Desktop/Workstation team,
as we are moving forward with Fedora 26 I would like to make sure we have all the deliverables, which might or might not be blocking for the release, identified on time. As such, I would like to ask you to review the list of deliverables the Desktop/Workstation team delivers for Fedora 26 release. The list is available on https://fedoraproject.org/wiki/Fedora_Program_Management/ReleaseBlocking/Fed... .
In case you find any discrepancy in the list, feel free to correct it or let me know and I will correct it then.
Just to make sure it's clear...
Workstation Live ISO x86_64: blocks release Workstation netinst ISO x86_64: blocks release Workstation ostree x86_64: doesn't block release ...and no other arches are considered blocking.
I think the question here is whether ostree should block. To the best of my knowledge no one's discussed that deliverable with release engineering enough that we could logically block the F26 release for it.
To be a bit more pointed: Unless someone who understands how to compose and deliver an ostree Workstation talks to rel-eng, and establishes that it can be automatically built in advance of Alpha/Beta, along with e.g. the Atomic Host releases, we can't logically block the release on it. This is not a "tell rel-eng a few weeks before release" task. ;-) Also, a release blocker should have test planning built up around it, and AFAIK that doesn't exist yet either.
On Mon, Jan 16, 2017 at 8:41 AM, Paul W. Frields stickster@gmail.com wrote:
Just to make sure it's clear...
Workstation Live ISO x86_64: blocks release Workstation netinst ISO x86_64: blocks release Workstation ostree x86_64: doesn't block release ...and no other arches are considered blocking.
I think the question here is whether ostree should block. To the best of my knowledge no one's discussed that deliverable with release engineering enough that we could logically block the F26 release for it.
It will take a special effort to get the installer to better support ostree layouts. Right now the installer's custom partitioning is fairly broken with ostree installations. If ostree images are made blocking, that'll mean the installer bugs relating to this all become release blocking bugs. The alternatives are:
a. Fix the bugs. b. Inhibit the presentation of any custom or advance partitioning installer UI, in effect the installer only supports one known well tested layout and the user can't get into trouble. c. Change the release criteria in a way that obviates both a and b.
a. is ideal; b. may inevitably end up being more realistic; c. is probably untenable.
Sample of what I've run into but I think the main issues are: /boot must be separate it can't be a directory on root fs; any mount point must go in /var, there's no way to mount /opt /var or /home but this needs to be automated on behalf of the user rather than expecting them to know this. Also it needs to know that ostree owns /var in that it's established via bind mount, so separate /var really isn't allowed right now, although subdirectories of /var could be separate volumes.
https://bugzilla.redhat.com/show_bug.cgi?id=1395910 https://bugzilla.redhat.com/show_bug.cgi?id=1289752 https://bugzilla.redhat.com/show_bug.cgi?id=1382873
desktop@lists.stg.fedoraproject.org
-
Chris Murphy -
Jan Kurik -
Paul W. Frields