Processes

Differences between revisions 1 and 61 (spanning 60 versions)
Revision 1 as of 2011-09-19 15:42:59
Size: 3260
Editor: 71-209-42-171
Comment: 2011-09-19; CharlieKravetz; a process/checklist to assist in getting all the items done for Xubuntu releases
Revision 61 as of 2015-01-13 11:36:53
Size: 6678
Editor: xdsl-83-150-81-40
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
#title Xubuntu Release Process #title Xubuntu Processes
Line 5: Line 5:
||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents>>|| = Xubuntu Processes =
Line 7: Line 7:
This page describes processes for Xubuntu development. All the processes and schedules should be used as a guidelines: This page ''mostly'' exists for us to document '''what we do''', not to tell us '''what to do'''. Minor issues and obvious shortcomings can be fixed without consulting, for larger-scale changes consult the team.
Line 8: Line 9:
To be carried out by: The Xubuntu Release Manager, with support from the Xubuntu Development Team and advice from the [[https://launchpad.net/~ubuntu-release|Ubuntu release team]]  * '''[[Xubuntu/Processes/ReleaseCycle|Release cycle]]'''
 * '''[[Xubuntu/Processes/Maintenance|Regular maintenance]]''' of assets (wiki, website)
Line 10: Line 12:
Goals: == Additional information ==
Line 12: Line 14:
 * Ensure that all ISOs are suitable for release.
 * This process should apply to alphas, betas, [[ReleaseCandidate|ReleaseCandidates]], final releases, and milestones.
 * Ship it!
In addition to the Xubuntu processes described below, there are several generic Ubuntu processes that are useful for the team and described elsewhere:
 * [[FreezeExceptionProcess|Freeze exception process]] for getting to upload changes after a relevant freeze
 * [[SponsorshipProcess|Sponsorship process]] for getting new package uploads in the archive
Line 16: Line 18:
== T minus 14 days == == Mailing list ==
Line 18: Line 20:
 1. Forward notifications of milestone freeze to xubuntu-devel@lists.ubuntu.com mailing list.
 1. Insure freeze times are posted in #xubuntu-devel and xubuntu-devel@lists.ubuntu.com mailing list.
 1. Freeze Day - notify developers of freeze and change topic in #xubuntu-devel.
=== Developer list moderation ===
Since the developer list is meant exclusively for development coordination, people who send inappropriate mails to the list will eventually receive a moderation flag. The process is as following:
 1. User sends an inappropriate message to the list
 2. Any moderator sends a private mail to them (and CC's -owner) explaining the situation and that they should not send further inappropriate messages to the list
 3. User sends another inappropriate message to the list
 4. (Ideally the same) moderator follows up with -owner to get a moderation flag added to the user.
 5. A list owner adds a moderation flag for the user; after this, all messages from the user need to be manually approved. List owners can drop the moderation flag discretly if it seems the user improves mail quality after getting the moderation flag.
Line 22: Line 28:
== T minus 7 days == == Meetings ==
Line 24: Line 30:
 1. Request Xubuntu developers availability for milestone testing.
 1. Review [[https://wiki.ubuntu.com/Xubuntu/Testing | testing pages]] to insure they are up to date.
 1. Remind project lead to begin preparing release notes.
=== Meeting chairs ===
The community meetings are held in #xubuntu-devel and chaired by the Xubuntu team leads. The chairing team leader is cycled based on the team name. The actual upcoming chair list can be found in the comments of the [[Xubuntu/Meetings|Meetings]] page.
Line 28: Line 33:
== T minus 5 days == The chair is responsible for scheduling and announcing the meeting on the development mailing list, and for updating the wiki with the meeting time.
Line 30: Line 35:
 * Testing should smoketest the images to insure they install. During any of the sections in the meeting, the chair can assign action items to individuals or teams with their permission. The chair should take care to copy these items to blueprint work items where applicable.
Line 32: Line 37:
== T minus 3 days == === Meeting minutes ===
Line 34: Line 39:
 1. Testing begins on the images available.
  * For alpha images, use the [[https://wiki.ubuntu.com/Xubuntu/Testing/TestingInfo/Short | short tests]].
  * For beta, rc, and final images, use the [[https://wiki.ubuntu.com/Xubuntu/Testing/TestingInfo/Long | long tests]].
  * All tests are recorded/tracked using the Ubuntu QA [[http://iso.qa.ubuntu.com/qatracker/build/xubuntu/all | ISO tracker]].
 1. Coordinate all testing with Ubuntu QA in #ubuntu-testing.
 1. Start the news article for the release; this is to be published on [[http://xubuntu.org | the website]] at the time of the release.
The team minutes will need to be added to the wiki after the meeting has ended. To do this, go to [[Xubuntu/Meetings/Archive/Minutes]] and use the input box for creating a minutes page. You will get the content for the page directly from [[meetingology]]s Moin output URL.
Line 41: Line 41:
== T minus 1 day == After you have created a minutes page, don't forget to update the '''Include''' in [[Xubuntu/Meetings]] as well as copy items marked with #done to the monthly team report at [[Xubuntu/TeamReports]].
Line 43: Line 43:
 1. Add release notes to the wiki.
  * Alpha notes are combined with Ubuntu release notes at https://wiki.ubuntu.com/ReleaseName/TechnicalOverview .
  * Beta and rc notes can be combined as alpha or, if significant changes were made should be separate under https://wiki.ubuntu.com/Xubuntu/ReleaseName/Milestone (example: https://wiki.ubuntu.com/Xubuntu/LucidLynx/Final).
== Packages related to Xubuntu ==
Line 47: Line 45:
== Release Day == === Xubuntu packageset ===
The Xubuntu team maintains a certain subset of packages in the Ubuntu archive. The per-release packageset lists are available at [[http://people.canonical.com/~ubuntu-archive/packagesets/]].
Line 49: Line 48:
 1. Review the Technical Overview/Release Notes to insure everything is accurate.
 1. Monitor for release announcement and PASS IT ON when announced.
  * Publish news on the Xubuntu website.
  * For the final release, insure the website download page is updated for the new release.
 1. Review bugs to insure all bugs found during testing are listed at https://wiki.ubuntu.com/Xubuntu/Bugs/ReleaseName .
 1. Update the [[https://wiki.ubuntu.com/Xubuntu/TeamReports | Team Report]].
 1. Add milestone review to [[https://wiki.ubuntu.com/Xubuntu/Meetings | meeting agenda]].
  * Reviewing as soon as possible helps to learn what we could have done better.
  * This is also a great time to congratulate the team for a job well done.
=== PPA's ===
The Xubuntu developers use several PPA's (personal package archives) for staging, testing and previewing new packages and package versions. These PPA's can be found under the [[LaunchpadHome:xubuntu-dev|~xubuntu-dev page at Launchpad]].
Line 59: Line 51:
== T plus 7 days == Currently, the official PPA's for development use are:
Line 61: Line 53:
 * Review this page and update it as needed for the next milestone/release period.
 * Reviewing as soon as possible helps keep this as up to date as possible.
||<^ #eeeeee 20%> '''[[https://launchpad.net/~xubuntu-dev/+archive/ubuntu/xubuntu-staging|Xubuntu Staging]]''' || This is a staging PPA for Xubuntu. The packages and package versions in this PPA are being prepared for inclusion in Xubuntu. The packages are uploaded for the convenience of people testing these new package versions and features. Some of them are daily builds used in testing. ||
||<^ #eeeeee> '''[[https://launchpad.net/~xubuntu-dev/+archive/ubuntu/extras|Xubuntu Extras]]''' || This is a preview PPA for Xubuntu. The packages in this PPA are considered for inclusion in the Ubuntu repositories and/or Xubuntu at a later time. The packages are uploaded for the convenience of people willing to preview the new features. ||

== Package translations ==
These are the packages that the Xubuntu team considers important and should take a precedence when translating:

=== The packages only exist in Xubuntu ===
These packages only exist in Xubuntu, so their translation is up to the Xubuntu translators solely. These are of high importance for the Xubuntu team.

 * [[https://translations.launchpad.net/xubuntu-docs|Xubuntu Documentation]]
 * [[https://translations.launchpad.net/xubuntu-default-settings|Default settings for Xubuntu]]
 * [[https://translations.launchpad.net/ubuntu/vivid/+source/ubiquity-slideshow-ubuntu/+pots/ubiquity-slideshow-xubuntu|Ubiquity slideshow for Xubuntu]] (note that the link is ''release-specific'', always check you are translating the current development version)

=== (Mainly) built for/used by Xubuntu ===
These packages exist outside Xubuntu, but they are mainly built to fit a need in Xubuntu. Unless/until they are spread much wider than now (and have gathered the interest of other translation groups), the Xubuntu translators should take care of getting their translations.

 * [[https://translations.launchpad.net/lightdm-gtk-greeter/|LightDM GTK+ Greeter]]
 * [[https://translations.launchpad.net/light-locker-settings|Light Locker Settings UI]]
 * [[https://translations.launchpad.net/menulibre|Menulibre]]
 * [[https://translations.launchpad.net/mugshot|Mugshot]]

=== Used by and essential for Xubuntu ===
These packages are used by Xubuntu and provide essential features to the Xubuntu experience. when these are translated, the base system is immediately more usable for more people.

 * [[https://translations.launchpad.net/catfish-search|Catfish]]
 * [[https://www.transifex.com/projects/p/xfce4-whiskermenu-plugin/|Whiskermenu]]

== XPL nominee wiki page requirements ==

To increase transparency and to make sure relevant information is available for the Xubuntu team members to vote, the nominees are required to provide a wiki page with at least the following information:
 * A brief history of the nominee in the FOSS world
 * Activities in any relevant teams
 * Thoughts about the Xubuntu development, including the biggest challenges and possibilities
 * Areas of interest as a XPL, including any changes the nominee is wishing to see in the team

Xubuntu Processes

This page describes processes for Xubuntu development. All the processes and schedules should be used as a guidelines: This page mostly exists for us to document what we do, not to tell us what to do. Minor issues and obvious shortcomings can be fixed without consulting, for larger-scale changes consult the team.

Additional information

In addition to the Xubuntu processes described below, there are several generic Ubuntu processes that are useful for the team and described elsewhere:

Mailing list

Developer list moderation

Since the developer list is meant exclusively for development coordination, people who send inappropriate mails to the list will eventually receive a moderation flag. The process is as following:

  1. User sends an inappropriate message to the list
  2. Any moderator sends a private mail to them (and CC's -owner) explaining the situation and that they should not send further inappropriate messages to the list
  3. User sends another inappropriate message to the list
  4. (Ideally the same) moderator follows up with -owner to get a moderation flag added to the user.
  5. A list owner adds a moderation flag for the user; after this, all messages from the user need to be manually approved. List owners can drop the moderation flag discretly if it seems the user improves mail quality after getting the moderation flag.

Meetings

Meeting chairs

The community meetings are held in #xubuntu-devel and chaired by the Xubuntu team leads. The chairing team leader is cycled based on the team name. The actual upcoming chair list can be found in the comments of the Meetings page.

The chair is responsible for scheduling and announcing the meeting on the development mailing list, and for updating the wiki with the meeting time.

During any of the sections in the meeting, the chair can assign action items to individuals or teams with their permission. The chair should take care to copy these items to blueprint work items where applicable.

Meeting minutes

The team minutes will need to be added to the wiki after the meeting has ended. To do this, go to Xubuntu/Meetings/Archive/Minutes and use the input box for creating a minutes page. You will get the content for the page directly from meetingologys Moin output URL.

After you have created a minutes page, don't forget to update the Include in Xubuntu/Meetings as well as copy items marked with #done to the monthly team report at Xubuntu/TeamReports.

Xubuntu packageset

The Xubuntu team maintains a certain subset of packages in the Ubuntu archive. The per-release packageset lists are available at http://people.canonical.com/~ubuntu-archive/packagesets/.

PPA's

The Xubuntu developers use several PPA's (personal package archives) for staging, testing and previewing new packages and package versions. These PPA's can be found under the ~xubuntu-dev page at Launchpad.

Currently, the official PPA's for development use are:

Xubuntu Staging

This is a staging PPA for Xubuntu. The packages and package versions in this PPA are being prepared for inclusion in Xubuntu. The packages are uploaded for the convenience of people testing these new package versions and features. Some of them are daily builds used in testing.

Xubuntu Extras

This is a preview PPA for Xubuntu. The packages in this PPA are considered for inclusion in the Ubuntu repositories and/or Xubuntu at a later time. The packages are uploaded for the convenience of people willing to preview the new features.

Package translations

These are the packages that the Xubuntu team considers important and should take a precedence when translating:

The packages only exist in Xubuntu

These packages only exist in Xubuntu, so their translation is up to the Xubuntu translators solely. These are of high importance for the Xubuntu team.

(Mainly) built for/used by Xubuntu

These packages exist outside Xubuntu, but they are mainly built to fit a need in Xubuntu. Unless/until they are spread much wider than now (and have gathered the interest of other translation groups), the Xubuntu translators should take care of getting their translations.

Used by and essential for Xubuntu

These packages are used by Xubuntu and provide essential features to the Xubuntu experience. when these are translated, the base system is immediately more usable for more people.

XPL nominee wiki page requirements

To increase transparency and to make sure relevant information is available for the Xubuntu team members to vote, the nominees are required to provide a wiki page with at least the following information:

  • A brief history of the nominee in the FOSS world
  • Activities in any relevant teams
  • Thoughts about the Xubuntu development, including the biggest challenges and possibilities
  • Areas of interest as a XPL, including any changes the nominee is wishing to see in the team

Xubuntu/Processes (last edited 2016-02-16 17:58:09 by xdsl-83-150-81-40)