Skip to content
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

Open
wants to merge 2 commits into
base: explanation/merges-and-syncs
Choose a base branch
from

Conversation

dviererbe
Copy link
Collaborator

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!

@dviererbe dviererbe added the documentation Improvements or additions to documentation label May 2, 2024
@dviererbe dviererbe added this to the 2.0 Release milestone May 2, 2024
@dviererbe dviererbe requested review from rkratky and s-makin May 2, 2024 15:40
@dviererbe dviererbe self-assigned this May 2, 2024
dviererbe added a commit that referenced this pull request May 2, 2024
dviererbe added a commit that referenced this pull request May 2, 2024
Copy link
Collaborator

@s-makin s-makin left a 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
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
as an example announcement for an archive opening.
as an example.

Comment on lines +47 to +48
Merging with Upstream & Feature Development
-------------------------------------------
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Language Pack Translation Deadline
Language pack translation deadline


.. _NonLanguagePackTranslationDeadline:

Non Language Pack Translation Deadline
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
and other issues are deprioritized to focus developers on this effort.
and other issues are deprioritised to focus developers on this effort.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants