#5891 Deliverables and release engineering changes for Fedora.Next/Fedora 21
Closed: Fixed None Opened 10 years ago by jreznik.

Fedora Working Groups are discussing different options how to deliver specific Fedora Products. These deliverables has to be collected (and agreed on) to plan changes in Fedora release engineering process.

This ticket should serve to collect requirements from WGs in a centralized way (as there's possible overlap etc). For specific implementation details, new tickets will be created.


Fedora Cloud expects to deliver several variants (perhaps "spins") as images -- like the current qcow2/raw.xz and EC2 images, although now there will be a couple of them. That increase means we are hoping for more automated testing as well (and more automated workflow).

We also want to make an official Docker (container) image, which we will push to the docker index.
We've filed change proposals for these:

As well as related changes:

Fedora Cloud expects to deliver several variants (perhaps "spins") as images -- like the current qcow2/raw.xz and EC2 images, although now there will be a couple of them. That increase means we are hoping for more automated testing as well (and more automated workflow).

We also want to make an official Docker (container) image, which we will push to the docker index.
We've filed change proposals for these:

As well as related changes:

Currently, under releases/##/, we have

  • Everything/
  • Fedora/
  • Images/
  • Live/

What do you think about making this into:

  • Everything
  • Cloud
  • Server
  • Workstation
  • Other

With "Other" holding other spins, the arm images, etc.?

Currently, under releases/##/, we have

  • Everything/
  • Fedora/
  • Images/
  • Live/

What do you think about making this into:

  • Everything
  • Cloud
  • Server
  • Workstation
  • Other

With "Other" holding other spins, the arm images, etc.?

arm images should not be under other

I am working to be able to do a full compose to show everyone what things will look like.

arm images should not be under other

I am working to be able to do a full compose to show everyone what things will look like.

Replying to [comment:3 ausil]:

arm images should not be under other

Where should they go? A separate directory? "Other" isn't really very descriptive -- maybe that should be "ARM-Images" and "Spins"?

Replying to [comment:3 ausil]:

arm images should not be under other

Where should they go? A separate directory? "Other" isn't really very descriptive -- maybe that should be "ARM-Images" and "Spins"?

Replying to [comment:4 mattdm]:

Replying to [comment:3 ausil]:

arm images should not be under other

Where should they go? A separate directory? "Other" isn't really very descriptive -- maybe that should be "ARM-Images" and "Spins"?

lets just wait and see what comes up when we have a full compose to look at. but the arm Workstation image should go with the Workstation product tree

Replying to [comment:4 mattdm]:

Replying to [comment:3 ausil]:

arm images should not be under other

Where should they go? A separate directory? "Other" isn't really very descriptive -- maybe that should be "ARM-Images" and "Spins"?

lets just wait and see what comes up when we have a full compose to look at. but the arm Workstation image should go with the Workstation product tree

we really need to have this written down somewhere. eons ago I started a deliverables SOP for Fedora.last:

https://fedoraproject.org/wiki/User:Adamwill/Draft_releng_SOP_deliverables

but never got it finished, and it's currently a pain to read (I was prioritizing accuracy over ease of use in the first drafts, and never got around to the rewrite).

The Product WGs currently list their deliverables in (variously) their tech specs and/or PRDs, but these have proven to be inaccurate or outdated on more than one occasion already and we haven't released Alpha yet.

we really need to have this written down somewhere. eons ago I started a deliverables SOP for Fedora.last:

https://fedoraproject.org/wiki/User:Adamwill/Draft_releng_SOP_deliverables

but never got it finished, and it's currently a pain to read (I was prioritizing accuracy over ease of use in the first drafts, and never got around to the rewrite).

The Product WGs currently list their deliverables in (variously) their tech specs and/or PRDs, but these have proven to be inaccurate or outdated on more than one occasion already and we haven't released Alpha yet.

So, we delivered a f21 with various changes. ;)

Not sure there's anything left to do here... reopen if there is.

So, we delivered a f21 with various changes. ;)

Not sure there's anything left to do here... reopen if there is.

Metadata Update from @jreznik:
- Issue set to the milestone: Fedora 21 Alpha

7 years ago

Login to comment on this ticket.

Metadata