From Fedora Project Wiki
No edit summary
No edit summary
Line 26: Line 26:
|-
|-
| [http://taiga.fedorainfracloud.org/project/acarter-fedora-docker-atomic-tooling/us/211 Signed repos in koji] || Accepted || In Progress ||
| [http://taiga.fedorainfracloud.org/project/acarter-fedora-docker-atomic-tooling/us/211 Signed repos in koji] || Accepted || In Progress ||
|}
== F25 Planning ==
{|
! Deliverable !! Approval Status !! Dev Status !! Notes
|-
| [http://taiga.fedorainfracloud.org/project/acarter-fedora-docker-atomic-tooling/us/451 Docker & Atomic redesigned workflow] || - || - || -
|-
| Taskotron support for container testing || - || - || -
|-
|-
| [http://taiga.fedorainfracloud.org/project/acarter-fedora-docker-atomic-tooling/backlog?status=145,146,151,182&tags=auto_signing Content signing can be automated through Sigul or another tool] || Planning || Not Started ||
| [http://taiga.fedorainfracloud.org/project/acarter-fedora-docker-atomic-tooling/backlog?status=145,146,151,182&tags=auto_signing Content signing can be automated through Sigul or another tool] || Planning || Not Started ||
|-
| Docker 2 week build/test/release workflow automated via Jenkins || - || - || -
|-
| Mark an arch / artifact non-blocking || - || - || -
|-
| OSBS integration with Pulp || - || - || -
|-
| xdg app prototype in OSBS || - || - || -
|-
| RHEL.next support: Modularity || - || - || -
|-
| New Releng Deliverable: Cockpit container || - || - || -
|-
| New Releng Deliverable: Workstation OSTree || - || - || -
|-
| [https://fedoraproject.org/wiki/Changes/Server_Drop_i686 Drop support for shipping i686 media for Server] || - || - || -
|}
|}


== Backlog ==
== Backlog ==
Line 36: Line 62:
* [http://taiga.fedorainfracloud.org/project/acarter-fedora-docker-atomic-tooling/backlog?tags=documentation Documentation of rel-eng process so that internal release engineers can contribute]
* [http://taiga.fedorainfracloud.org/project/acarter-fedora-docker-atomic-tooling/backlog?tags=documentation Documentation of rel-eng process so that internal release engineers can contribute]
* [http://taiga.fedorainfracloud.org/project/acarter-fedora-docker-atomic-tooling/backlog?tags=process&status=145,146,147,151,182 Development & Deployment Process Improvement / Standardization]
* [http://taiga.fedorainfracloud.org/project/acarter-fedora-docker-atomic-tooling/backlog?tags=process&status=145,146,147,151,182 Development & Deployment Process Improvement / Standardization]
* [https://fedoraproject.org/wiki/Changes/Server_Drop_i686 Drop support for shipping i686 media for Server - F25]
* Move to createrepo_c (required before python3)
* Support for Fedora OSTree Based Workstation - F25
* Bodhi support for non-rpm content
* Cockpit as a release deliverable - F25
* Container test status results reported from Taskotron via fedmsg / email / UI
** This would apply to any other layered images
* Release automation for Atomic
* Release automation for Docker & Atomic - F25
** 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/455 Rel-eng-o-tron to orchestrate automated processes]
*** [http://taiga.fedorainfracloud.org/project/acarter-fedora-docker-atomic-tooling/backlog?tags=container_release Implement container automated 2 week releases]
*** Libreleng -  put releng functions into a common shared location so our scripts can use them
*** Taskotron
**** disposable clients
**** Dist-git style tasks
**** Integration with DockerAutoTest
**** Results reported via fedmsg / email / UI
** Atomic / 2nd Priority
*** Automated signing in Sigul
*** Taskotron
*** Taskotron
**** Integration with UAT Framework
**** Integration with UAT Framework
Line 59: Line 72:
**** 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]
*** Bodhi support for non-rpm content
*** Move ostree creation out of Bodhi
*** Move ostree creation out of Bodhi
* Move to createrepo_c (required before python3) - F25 Candidate
* [http://taiga.fedorainfracloud.org/project/acarter-fedora-docker-atomic-tooling/backlog?tags=installmedia DVD ISO support in Koji - F25 Candidate]
* [http://taiga.fedorainfracloud.org/project/acarter-fedora-docker-atomic-tooling/backlog?tags=installmedia DVD ISO support in Koji - F25 Candidate]
* Move from yum to dnf (required before python3)
* Move from yum to dnf (required before python3)
Line 67: Line 78:
* Port to python 3 - Pungi, Mash, releng scripts, fedpkg, rpkg, etc
* Port to python 3 - Pungi, Mash, releng scripts, fedpkg, rpkg, etc
** Requires roadmap for testability so that we can verify our migration
** 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
* add index.asc files for cloud images for virt-builder - https://fedorahosted.org/rel-eng/ticket/5805
* add index.asc files for cloud images for virt-builder - https://fedorahosted.org/rel-eng/ticket/5805
* Consolidate hubs for primary and secondary arches
* Consolidate hubs for primary and secondary arches
Line 73: Line 83:
* Koji 2.0
* Koji 2.0
* ET / Bodhi alignment
* 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
* 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
* Any opportunities for leveraging Level 1 support

Revision as of 21:40, 19 April 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

F25 Planning

Deliverable Approval Status Dev Status Notes
Docker & Atomic redesigned workflow - - -
Taskotron support for container testing - - -
Content signing can be automated through Sigul or another tool Planning Not Started
Docker 2 week build/test/release workflow automated via Jenkins - - -
Mark an arch / artifact non-blocking - - -
OSBS integration with Pulp - - -
xdg app prototype in OSBS - - -
RHEL.next support: Modularity - - -
New Releng Deliverable: Cockpit container - - -
New Releng Deliverable: Workstation OSTree - - -
Drop support for shipping i686 media for Server - - -


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
  • Move to createrepo_c (required before python3)
  • Bodhi support for non-rpm content
  • Container test status results reported from Taskotron via fedmsg / email / UI
  • Release automation for Atomic
      • Taskotron
        • Integration with UAT Framework
        • Integration with Autocloud OR porting functionality & tests to Taskotron
        • Integration with Tunir OR porting functionality & tests to Taskotron
        • Integration with OpenQA
      • Atomic ostree repo management
      • Move ostree creation out of Bodhi
  • 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
  • add index.asc files for cloud images for virt-builder - https://fedorahosted.org/rel-eng/ticket/5805
  • 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
  • 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

Retrieved from "https://fedoraproject.org/w/index.php?title=ReleaseEngineering/PriorityPipeline&oldid=443606"