-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add initial content for explanantion/development process #54
base: explanation/merges-and-syncs
Are you sure you want to change the base?
Add initial content for explanantion/development process #54
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry for the delay in my review, this fell off my radar with the sprint. Mainly US -> UK spelling and de-capitalising headers, although I have a couple of other questions/suggestions as well. I don't know if we're still using US spelling in the Packaging Guide, but if we are there are some spellings that will need to go from UK to US (you've got a mixture of both in here :D)
Each release cycle follows the same general pattern, with the following | ||
major phases. Ubuntu contributors are expected to follow this process closely | ||
to ensure that their work is aligned with that of others. Because of the | ||
time-based release cycle, Ubuntu contributors must be well-coordinated to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
time-based release cycle, Ubuntu contributors must be well-coordinated to | |
time-based release cycle, Ubuntu contributors must coordinate well to |
|
||
The Ubuntu infrastructure is prepared for a new development branch at the | ||
beginning of each cycle. The package build system is set up, the toolchain | ||
is organized, :term:`seeds` are branched, and many other pieces are made ready |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is organized, :term:`seeds` are branched, and many other pieces are made ready | |
is organised, :term:`seeds` are branched, and many other pieces are made ready |
See also the article, :doc:`/explanation/releases`, for more details about the | ||
release cadence. | ||
|
||
Beginning a new Release |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Beginning a new Release | |
Beginning a new release |
|
||
.. note:: | ||
See the `Ubuntu 24.04 LTS (Noble Numbat) archive opening announcement email <https://lists.ubuntu.com/archives/ubuntu-devel-announce/2023-October/001341.html>`_ | ||
as an example announcement for an archive opening. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
as an example announcement for an archive opening. | |
as an example. |
Merging with Upstream & Feature Development | ||
------------------------------------------- |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Merging with Upstream & Feature Development | |
------------------------------------------- | |
Merging with upstream and feature development | |
--------------------------------------------- |
containing a specified package or to determine whether the specified | ||
package is part of the supported seed. | ||
|
||
If the outputted list is empty, uploading it during a freeze should be |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If the outputted list is empty, uploading it during a freeze should be | |
If the list output is empty, uploading it during a freeze should be |
|
||
.. _LanguagePackTranslationDeadline: | ||
|
||
Language Pack Translation Deadline |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Language Pack Translation Deadline | |
Language pack translation deadline |
|
||
.. _NonLanguagePackTranslationDeadline: | ||
|
||
Non Language Pack Translation Deadline |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Non Language Pack Translation Deadline | |
Non-language-pack translation deadline |
Translations done up until this date will be included in the final release's | ||
language packs. | ||
|
||
Finalization |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Finalization | |
Finalisation |
As the final release approaches, the focus narrows to fixing "showstopper" | ||
bugs and thoroughly validating the installation images. Every image is tested | ||
to ensure that the installation methods work as advertised. Low-impact bugs | ||
and other issues are deprioritized to focus developers on this effort. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
and other issues are deprioritized to focus developers on this effort. | |
and other issues are deprioritised to focus developers on this effort. |
This PR adds the initial content for the explanation article of the Ubuntu development process.
Note: This PR is targeted against #53 for better readability of the diff. Set the base to the
2.0-preview
branch before merging!