From Fedora Project Wiki
No edit summary
Line 38: Line 38:
* [https://fedoraproject.org/wiki/Changes/Server_Drop_i686 Drop support for shipping i686 media for Server - F25]
* [https://fedoraproject.org/wiki/Changes/Server_Drop_i686 Drop support for shipping i686 media for Server - F25]
* Release automation for Docker & Atomic - F25
* Release automation for Docker & Atomic - F25
** Docker / 1st Phase
** Docker / 1st Priority
*** [http://taiga.fedorainfracloud.org/project/acarter-fedora-docker-atomic-tooling/us/451 Atomic redesigned workflow & toolchain]
*** [http://taiga.fedorainfracloud.org/project/acarter-fedora-docker-atomic-tooling/us/451 Atomic redesigned workflow & toolchain]
*** [http://taiga.fedorainfracloud.org/project/acarter-fedora-docker-atomic-tooling/us/455 Rel-eng-o-tron to orchestrate automated processes]
*** [http://taiga.fedorainfracloud.org/project/acarter-fedora-docker-atomic-tooling/us/455 Rel-eng-o-tron to orchestrate automated processes]
*** [http://taiga.fedorainfracloud.org/project/acarter-fedora-docker-atomic-tooling/backlog?tags=container_release Docker container automated 2 week releases - F25 Candidate]
*** [http://taiga.fedorainfracloud.org/project/acarter-fedora-docker-atomic-tooling/backlog?tags=container_release Implement container automated 2 week releases]
*** Libreleng -  putting releng functions into a common shared location so our scripts can use them
*** Libreleng -  put releng functions into a common shared location so our scripts can use them
*** Taskotron
*** Taskotron
**** disposable clients
**** disposable clients
**** Dist-git style tasks
**** Dist-git style tasks
**** Integration with DockerAutoTest
**** Integration with DockerAutoTest
** Atomic / 2nd Phase
** Atomic / 2nd Priority
*** Automated signing in Sigul
*** Taskotron
*** Taskotron
**** Integration with UAT Framework
**** Integration with UAT Framework
Line 54: Line 55:
**** Integration with OpenQA
**** Integration with OpenQA
*** [http://taiga.fedorainfracloud.org/project/acarter-fedora-docker-atomic-tooling/backlog?tags=atomic_repomanagement&status=145,146,147,151,182 Atomic ostree repo management]
*** [http://taiga.fedorainfracloud.org/project/acarter-fedora-docker-atomic-tooling/backlog?tags=atomic_repomanagement&status=145,146,147,151,182 Atomic ostree repo management]
*** Including Bodhi support for non-rpm content
*** Bodhi support for non-rpm content
*** Move ostree creation out of Bodhi
* Move to createrepo_c (required before python3) - F25 Candidate
* Move to createrepo_c (required before python3) - F25 Candidate
* DVD ISO support in Koji - F25 Candidate
* DVD ISO support in Koji - F25 Candidate

Revision as of 21:03, 2 February 2016

Monthly Stakeholder Meetings

Priorities

Immediate Priorites

F24 Commitments

Deliverable Approval Status Dev Status Notes
Layered image builds Accepted In Progress Includes work for OpenShift in Fedora below
OpenShift in Fedora Accepted Done
PDC deployed & populated with product / release data Accepted Done
Pungi 4 upgrade and Pungi roadmap Accepted In Progress
Move to livemedia-creator for live cds & disk images Accepted In Progress
Signed repos in koji Accepted In Progress
Content signing can be automated through Sigul or another tool Planning Not Started

Backlog

Note: Backlog items are not necessarily complete or groomed; if you have questions about the goal of these items, ask the team!

  • Documentation of rel-eng process so that internal release engineers can contribute
  • Development & Deployment Process Improvement / Standardization
  • Drop support for shipping i686 media for Server - F25
  • Release automation for Docker & Atomic - F25
  • Move to createrepo_c (required before python3) - F25 Candidate
  • DVD ISO support in Koji - F25 Candidate
  • Move from yum to dnf (required before python3)
  • Docker images can be built in Oz / ImageFactory OR in OSBS to align with internal teams for all supported arches (F26 candidate)
  • Port to python 3 - Pungi, Mash, releng scripts, fedpkg, rpkg, etc
    • Requires roadmap for testability so that we can verify our migration
  • Method for releasing zero day fixes quickly - https://fedorahosted.org/rel-eng/ticket/5886
  • Consolidate hubs for primary and secondary arches
  • RHEL process checks done internally that should also be done in Fedora (ie license checking, rpmdiff / static analysis, etc)
  • Koji 2.0
  • ET / Bodhi alignment
  • RHEL.next support
  • Ability to create embargoed builds in tools (at least koji & bodhi) and lift the embargo after release so that security can get embargoed changes out quickly
  • Any opportunities for leveraging Level 1 support
  • rel-eng scripts cleanup
  • rel-eng tools are not easily testable or contributed to
  • changes can be tested in an integrated environment before releasing to production
  • Critical system / use case integration with gilmsg where appropriate in release tooling
  • Development release gating with sanity testing / stability
  • Fedora Rings / Alephs
  • Layered images _not_ from RPMs — source-to-image or other
  • Releng CI (on Jenkins)

Completed