< Changes
No edit summary |
|||
| Line 57: | Line 57: | ||
The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing, and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication --> | The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing, and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication --> | ||
** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: | ** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: Not affected <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- Please check the list of Fedora release deliverables and list all the differences the feature brings --> | <!-- Please check the list of Fedora release deliverables and list all the differences the feature brings --> | ||
| Line 128: | Line 128: | ||
--> | --> | ||
[[Category: | [[Category:ChangeReadyForFesco]] | ||
<!-- When your change proposal page is completed and ready for review and announcement --> | <!-- When your change proposal page is completed and ready for review and announcement --> | ||
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | ||
Revision as of 07:27, 9 May 2017
Arbitrary Branching
Summary
Tooling changes to support the new way of branching for Fedora 27
Owner
- Name: Matt Prahl
- Email: mprahl@redhat.com
- Release notes owner:
Current status
- Targeted release: Fedora 27
- Last updated: 2017-05-09
- Tracker bug: <will be assigned by the Wrangler>
Detailed Description
To avoid maintaining multiple copies of this information, please read the Arbitrary Branching Focus Document (updated May 3rd, 2017) in the Factory2 space as a substitute for this document: https://fedoraproject.org/wiki/Infrastructure/Factory2/Focus/ArbitraryBranching
For further information, view this section of Ralph Bean’s presentation at DevConf: https://youtu.be/5gqccjyjwFk?t=26m27s
Benefit to Fedora
See the “Background on PkgDB” and “Why Make This Change?” sections in the Arbitrary Branching Focus document linked above.
Scope
- Proposal owners: We will do all of the work listed in the linked document.
- Other developers:
- We're relying on the infra team to get Pagure on top of dist-git.
- We're relying on releng to find any holes in our work plan and to help us make decisions on how to solve bugs.
- No direct work should be required from the general packaging group to support this Change.
- Release engineering: #6775
- List of deliverables: Not affected
- Policies and guidelines: Packaging guidelines would change and would be updated after the changes are implemented in staging.
- Trademark approval: N/A (not needed for this Change)
Upgrade/compatibility impact
Not backwards compatible but not significantly difficult to roll back because all changes will be done in Ansible.
How To Test
- Request new packages
- Request new branches with non-standard names (i.e. not f25, f26, etc.) and build with them
- Request new branches for standard names that are still supported (i.e. f25, f26, epel6, epel7) and build with them
- Retire a package
- Orphan a package
User Experience
See the “How To Make This Change?” section in the Arbitrary Branching Focus document linked above.
Dependencies
- Pagure over dist-git will need to be updated in staging
- Pagure over dist-git will need to be deployed in production
Contingency Plan
- Contingency mechanism: Re-enable PkgDB and roll back our script changes in Ansible
- Contingency deadline: N/A
- Blocks release? Yes, it blocks Fedora 27 Modularity. They will be filing a Change document in the coming months to describe the F27 structure
- Blocks product? Fedora 27
Documentation
Documentation on new processes would be provided at a later date if there is approval on this Change Proposal.