Re: contingency plan for the failed-to-build spins/labs?

[Robert Mayr]

2016-06-20 19:13 GMT+02:00 Kevin Fenzi :

> So, we discussed this at the releng meeting this morning.
>
> #agreed The least amount of 1 off work is to ship some tested nightlies
> in /pub/alt/unoffical/release/24/ just the isos, signed checksums and
> some manifest files that list all the srpms to keep legal happy
>
> #info keeping the images seperate and named differently will ensure
> that the metadata and what is in PDC about the compose and release is
> correct
>
> So, the last nightlies I see for those 2 spins are:
>
> SoaS from the 14th (15th and 16th failed):
> http://koji.fedoraproject.org/koji/taskinfo?taskID=14484555
>
> Design (also from the 14th):
>
> http://koji.fedoraproject.org/koji/taskinfo?taskID=14484528
>
> Next steps:
>
> * would be nice if some folks could do some quick testing of these and
>   make sure they boot and run and such.
>
> * Then, Dennis can put them in alt somewhere with signed checksums and
>   manifests.
>
> * Websites would need to add some kind of blurb and point to them
>   instead of the main release versions. Someone want to file a ticket?
>
>
Filed:
https://fedorahosted.org/fedora-websites/ticket/397

-- 
Robert Mayr
(robyduck)
--
websites mailing list
websites@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/websites@lists.fedoraproject.org

[fedora-websites] #397: Write a blurb for labs/spins which failed the final compose

[fedora-websites]

#397: Write a blurb for labs/spins which failed the final compose
---+---
  Reporter:  robyduck  |  Owner:  webmaster
  Type:  task  | Status:  new
  Priority:  critical  |  Milestone:  ASAP
 Component:  General   |   Keywords:  easyfix
Blocked By:|   Blocking:
---+---
 After a discussion with releng and FPL we want to provide as many images
 as possible for end users, even if they fail the final compose. In fact,
 sometimes a spin/lab fails the compose for many reasons, and we need to
 drop them from the official images.

 While we cannot change this, we want to provide some unofficial images,
 like nightlies. From the last releng meeting:

 #agreed The least amount of 1 off work is to ship some tested nightlies
 in /pub/alt/unoffical/release/24/ just the isos, signed checksums and
 some manifest files that list all the srpms to keep legal happy

 #info keeping the images seperate and named differently will ensure
 that the metadata and what is in PDC about the compose and release is
 correct

 So, the last nightlies I see for those 2 spins are:

 SoaS from the 14th (15th and 16th failed):
 http://koji.fedoraproject.org/koji/taskinfo?taskID=14484555

 Design (also from the 14th):

 http://koji.fedoraproject.org/koji/taskinfo?taskID=14484528

 My idea is to make a blurb like we have for prerelease images in the
 download page and link to the nightlies. Nothing special, a templte would
 be cool, so we can activate it if needed.

 For SoaS, Design and Jam we will need it soon, release day is tomorrow, we
 should try to make it work ASAP.

-- 
Ticket URL: 
fedora-websites 
Fedora Website Team's Trac instance
--
websites mailing list
websites@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/websites@lists.fedoraproject.org

Re: contingency plan for the failed-to-build spins/labs?

[Matthew Miller]

On Mon, Jun 20, 2016 at 11:13:37AM -0600, Kevin Fenzi wrote:
> * Marketing/announcement needs to note that they exist, but are nightly
>   composes, not exactly the same as release. Can someone notify
>   marketing?

I can. I currently removed them from the annoucement but can either a)
put them back or b) write a separate post the day after.



-- 
Matthew Miller

Fedora Project Leader
--
websites mailing list
websites@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/websites@lists.fedoraproject.org

Re: contingency plan for the failed-to-build spins/labs?

[Kevin Fenzi]

So, we discussed this at the releng meeting this morning. 

#agreed The least amount of 1 off work is to ship some tested nightlies
in /pub/alt/unoffical/release/24/ just the isos, signed checksums and
some manifest files that list all the srpms to keep legal happy

#info keeping the images seperate and named differently will ensure
that the metadata and what is in PDC about the compose and release is
correct

So, the last nightlies I see for those 2 spins are: 

SoaS from the 14th (15th and 16th failed): 
http://koji.fedoraproject.org/koji/taskinfo?taskID=14484555

Design (also from the 14th):

http://koji.fedoraproject.org/koji/taskinfo?taskID=14484528

Next steps: 

* would be nice if some folks could do some quick testing of these and
  make sure they boot and run and such. 

* Then, Dennis can put them in alt somewhere with signed checksums and
  manifests. 

* Websites would need to add some kind of blurb and point to them
  instead of the main release versions. Someone want to file a ticket?

* Marketing/announcement needs to note that they exist, but are nightly
  composes, not exactly the same as release. Can someone notify
  marketing?

kevin


pgpbmeU3RPVAQ.pgp
Description: OpenPGP digital signature
--
websites mailing list
websites@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/websites@lists.fedoraproject.org

Re: contingency plan for the failed-to-build spins/labs?

[Matthew Miller]

On Mon, Jun 20, 2016 at 09:32:23AM -0500, Dennis Gilmore wrote:
> Jam failed due to package issues, its package set was not installable, dnf 
> aborted the transactionso anaconda failed to install, it will be getting 
> removed and will have to follow the process for a new spin if it is to ever 
> come back, same as any spin that misses the boat, however given that SoaS and 

Okay, that's fair for Jam.

> As we move into a more automated way doing one off things like this
> is going to get harder and harder to accomodate and do anything
> about. Relaistically at this point doing anything here is more up to

This seems backwards to me. As we get more complicated and develop
automation to assist with that complication, we need to get _more_
flexible, not less. I'd love for Spins to be able to ship when the SIG
for each one determines that their thing is ready - if someone wants to
fix up Jam, release it next month or whatever.

For that matter, it'd be nice to have the option for the main Editions
- if there's something that only affects Workstation or Server, don't
hold up the other (or the underlying release) for it.

From a PR point of view, the releases don't drive press like they used
to - I think we'd actually be better served by more, smaller
announcements. From a user adoption point of view, releases aren't the
driver either - data shows a download spike for new releases, but
overall the total Fedora users curve grows independently from that.
People come for whatever release is current and don't generally wait
for the splash of the next one.

-- 
Matthew Miller

Fedora Project Leader
--
websites mailing list
websites@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/websites@lists.fedoraproject.org

Re: contingency plan for the failed-to-build spins/labs?

[Robert Mayr]

2016-06-20 15:16 GMT+02:00 Matthew Miller :

> On Mon, Jun 20, 2016 at 09:15:41AM -0400, Matthew Miller wrote:
> > So, we have this bug* where some images are failing to be built, and it
> > happened that the SoaS spin and Design and Jam labs ended up not
> > succeeding in what became the official release. They aren't release
> > blocking, so this is fine "by the books", but it seems unfortunate to
> > miss them due to what's basically a tools bug rather than something
> > inherently wrong with them.
>
> Peter tells me there's a releng meeting in an hour or so... can we add
> this to that agenda?
>
> --
> Matthew Miller
> 
> Fedora Project Leader
> --
> websites mailing list
> websites@lists.fedoraproject.org
>
> https://lists.fedoraproject.org/admin/lists/websites@lists.fedoraproject.org
>


I agree, having some images not in the final (but also in testing) release
is not really a good publicity, but we cannot add them to the official GA
release if they missed the "GOLDen" RC build.
I'm with Adam here, we might add them to the nightlies. Also, as we are
working on a new alt.fedoraproject.org website, we could easily link to
them if needed. This could be a solution.
See the website in staging if you want to take a look:
https://alt.stg.fedoraproject.org

-- 
Robert Mayr
(robyduck)
--
websites mailing list
websites@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/websites@lists.fedoraproject.org

Re: contingency plan for the failed-to-build spins/labs?

[Matthew Miller]

On Mon, Jun 20, 2016 at 09:15:41AM -0400, Matthew Miller wrote:
> So, we have this bug* where some images are failing to be built, and it
> happened that the SoaS spin and Design and Jam labs ended up not
> succeeding in what became the official release. They aren't release
> blocking, so this is fine "by the books", but it seems unfortunate to
> miss them due to what's basically a tools bug rather than something
> inherently wrong with them.

Peter tells me there's a releng meeting in an hour or so... can we add
this to that agenda?

-- 
Matthew Miller

Fedora Project Leader
--
websites mailing list
websites@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/websites@lists.fedoraproject.org

contingency plan for the failed-to-build spins/labs?

[Matthew Miller]

So, we have this bug* where some images are failing to be built, and it
happened that the SoaS spin and Design and Jam labs ended up not
succeeding in what became the official release. They aren't release
blocking, so this is fine "by the books", but it seems unfortunate to
miss them due to what's basically a tools bug rather than something
inherently wrong with them.

Obviously they missed the official cut and won't get synced out with
the rest, but I think the download numbers for these are niche enough
that it's probably okay to host them separately.

As I understand it, someone could just keep submitting the builds until
they happen to work, right? (And this might actually provide some
valuable debug info, because we can compare what works and what
doesn't.) Then, we could put those in /pub/alt or something and have
the spins/labs websites link to that. (These could be then signed with
the official key and etc.)

Or, Adam W suggested that we could instead link to nightlies, with a
footnote or something on the websites.



* https://bugzilla.redhat.com/show_bug.cgi?id=1315541


-- 
Matthew Miller

Fedora Project Leader
--
websites mailing list
websites@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/websites@lists.fedoraproject.org