separate bodhi packages
Signed-off-by: Mark O Brien <markobri@redhat.com>
This commit is contained in:
parent
ccb94b5401
commit
b5796b34b5
1 changed files with 30 additions and 0 deletions
|
@ -3,3 +3,33 @@
|
||||||
|
|
||||||
Split Bodhi Into Separate Python Packages
|
Split Bodhi Into Separate Python Packages
|
||||||
=========================================
|
=========================================
|
||||||
|
|
||||||
|
|
||||||
|
Resources
|
||||||
|
---------
|
||||||
|
|
||||||
|
* Bodhi source code: https://github.com/fedora-infra/bodhi
|
||||||
|
* Python packaging docs: https://packaging.python.org/guides/packaging-namespace-packages/
|
||||||
|
* mini-initiative: https://pagure.io/fedora-infrastructure/issue/10368
|
||||||
|
|
||||||
|
|
||||||
|
Discussion
|
||||||
|
----------
|
||||||
|
|
||||||
|
Currently Bodhi is a number of packages combined. It may be beneficial to split
|
||||||
|
into its separate parts. This would allow for each package to be updated and
|
||||||
|
maintained at its own pace allowing for incremental improvements to bodhi. When
|
||||||
|
implemented a single part of Bodhi could be deployed at a time instead of having
|
||||||
|
to deploy the whole application in one go.
|
||||||
|
|
||||||
|
The main benefits of this would be an easier to manage application, an easier to
|
||||||
|
deploy application and a more regularly deployed application as a single issue
|
||||||
|
fix could be deployed at a time.
|
||||||
|
|
||||||
|
|
||||||
|
Conclusion
|
||||||
|
----------
|
||||||
|
|
||||||
|
This is work that would be of great benefit to the team but is not initiative
|
||||||
|
worthy on its own. Therefore a mini-initiative seems the best solution.
|
||||||
|
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue