On Tue, Sep 27, 2016 at 7:43 AM, Stephen Gallagher <sgallagh(a)redhat.com> wrote:
On 09/27/2016 02:48 AM, Jan Kurik wrote:
> On Mon, Sep 26, 2016 at 11:21 PM, Paul W. Frields <stickster(a)gmail.com> wrote:
>> On Fri, Sep 16, 2016 at 10:05:03AM +0200, Jan Kurik wrote:
>>> Thanks for reviewing the list during the meeting .
>>> As I have realized from the meeting minutes  and from private
>>> conversation with Stickster, there is a Change proposal  to add
>>> OSTree image for Workstation edition. Unfortunately this Change
>>> proposal has never been submitted for review nor approved by FESCo. Up
>>> to now it is still marked as "Incomplete". As we are far beyond
>>> deadline for accepting Change proposals for F25 release I would
>>> suggest to move this Change to F26 release. Is it acceptable for the
>>> WG ?
>>> If this is not acceptable and the WG would like to push to have this
>>> Change in F25, then we can ask FESCo for an exception to add this
>>> Change to F25 release. As this Change is "Self contained" and
>>> not have impact on any part of Fedora (except build of a compose), it
>>> might be IMO taken to consideration.
>>>  https://fedoraproject.org/wiki/Changes/WorkstationOstree
>> Hi Jan,
>> While the WG and rel-eng have done work to get ready for this Change,
>> presently it looks like we are only going to have something
>> experimental to offer for users. Is there any reason that pushing the
>> Change to F26 would *interfere* with that offering?
> Hi Paul,
> this should be agreed with FESCo, however from my POV it is fine to
> have an experimental deliverable available for F25, which will not be
> publicly announced and then go through the Change process and have the
> finalized version available for F26 as a regular deliverable. Please
> let me know if you are fine with this approach, so I can open a ticket
> to FESCo.
For that, you need the approval of rel-eng, as it will mean another medium to
produce, even if it's non-blocking.
14:54:13 <dgilmore> #info please file a issue in pagure or send an
email to the releng list when dealing with issues changing what or how
we deliver things
A number of issues with the existing way ostrees are created and
maintained came up in yesterday's releng meeting as well. By the sound
of it, they're not happy with how it presently works and doesn't
scale, so they want to scrap it and start over. That work may play
into additional deliverables availability in the short term. It also
sounds like they still need help.
If the experimental rpm-ostree workstation suggested for Fedora 25
were to mimick the Cloud atomic host variants' two week cadence,
perhaps it's possible to make it available asynchronously from
official Fedora 25 release?