From Fedora Project Wiki
< Changes
Churchyard (talk | contribs) m (→Scope) |
(Add trackers) |
||
| (5 intermediate revisions by 2 users not shown) | |||
| Line 41: | Line 41: | ||
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development | CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development | ||
--> | --> | ||
* Tracker bug: | * Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1765576 #1765576] | ||
* Release notes tracker: | * Release notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/415 #415] | ||
== Detailed Description == | == Detailed Description == | ||
| Line 65: | Line 65: | ||
== Scope == | == Scope == | ||
* '''Proposal owners:''' package {{package|breezy}} and its dependencies (done, see [https://bugzilla.redhat.com/show_bug.cgi?id=1754964 the package review]), flip the bcond in the package to provide/obsolete | * '''Proposal owners:''' package {{package|breezy}} and its dependencies (done, see [https://bugzilla.redhat.com/show_bug.cgi?id=1754964 the package review]), flip the bcond in the package to provide/obsolete bzr. | ||
<!-- What work do the feature owners have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | <!-- What work do the feature owners have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | ||
* '''Other developers:''' Test that your packages work with breezy ( | * '''Other developers:''' Test that your packages work with breezy ({{package|etckeeper}}, {{package|ikiwiki}}, {{package|python-vcstools}}, {{package|python-wstool}}, {{package|golang-github-masterminds-vcs}}, {{package|python-pip}} are impacted). Adapt, drop the dependency or retire the packages. | ||
* Release engineering: no impact with Release Engineering is anticipated <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | * Release engineering: no impact with Release Engineering is anticipated <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
| Line 136: | Line 136: | ||
TBD | TBD | ||
[[Category: | [[Category:ChangeAcceptedF32]] | ||
<!-- 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 --> | ||
Latest revision as of 13:14, 25 October 2019
Replace Bazaar with Breezy
Summary
This change is about replacing the 
bzr
Owner
- Name: Miro Hrončok
- Email: <mhroncok@redhat.com>
- Name: Marcel Plch
- Email: <mplch@redhat.com>
Current status
- Targeted release: Fedora 32
- Last updated: 2019-10-25
- Tracker bug: #1765576
- Release notes tracker: #415
Detailed Description
The bzr and git-remote-bzr, it contains /usr/bin/bzr (link to /usr/bin/brz) and /usr/bin/git-remote-bzr.
Packages
The reasons for this include:
- bzr is Python 2 only and Python 2 is retired
- bzr fails to build from source
- bzr fails to install
- bzr has no maintainer
Benefit to Fedora
Users of Fedora will be able to use bazaar repositories via breezy. If we don't do this, bzr would be simply removed without a replacement.
Scope
- Proposal owners: package
breezy
- Other developers: Test that your packages work with breezy (
- Release engineering: no impact with Release Engineering is anticipated
- Policies and guidelines: N/A (not a System Wide Change)
- Trademark approval: N/A (not needed for this Change)
Upgrade/compatibility impact
Eventually removed depndent packages need to be obsoleted.
Breezy aims to be compatible with bazaar, but there might be some differences.
How To Test
Test that installing bzr installs breezy, test that you can use it successfully. Test that bzr gets replaced by breezy when upgrading to Fedora 32.
User Experience
Users installing bzr will get breezy instead. The bzr command will be provided as a symbolic link to the brz (breezy) command. The basic API of that command should be the same.
Contingency Plan
- Contingency mechanism: (What to do? Who will do it?) Proposal owners will orphan both breezy and bzr (sorry, but not sorry).
- Contingency deadline: final freeze
- Blocks release? No
- Blocks product? No
Documentation
Release Notes
TBD