Processes

Differences between revisions 57 and 58
Revision 57 as of 2014-10-24 09:32:13
Size: 15172
Editor: knome
Comment:
Revision 58 as of 2014-10-31 15:20:54
Size: 15171
Editor: slickymaster
Comment:
Deletions are marked like this. Additions are marked like this.
Line 59: Line 59:
 * [[https://translations.launchpad.net/ubuntu/utopic/+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)  * [[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)

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.

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.

Release cycle

The release cycle consists of 5 more or less overlapping stages, which are:

Planning

Developing

Testing

Releasing

Maintaining

Planning

Planning the release is conducted in three phases:

  • Brainstorming
  • Approving blueprints
  • Finalizing specifications

In the brainstorming phase the contributors determine what they would like to work on during the release cycle, including proposals for changes in default applications. Anybody can items to the list. Settling on the goals in advance will make planning, focusing and estimating the likelihood for the features to be implemented easier.

After the brainstorming is over and before or on the Feature Definition Freeze day, the Xubuntu team will approve or reject the proposed blueprints. Any items with no assignee or rationale will be automatically rejected, but having them will not guarantee that the blueprint is approved. Other criteria include, but are not limited to: likelihood of getting the feature implemented, maintenance weight in the future, possible stability issues, influence on other blueprints, et cetera. The approved blueprints compose the roadmap for the release being developed.

After blueprints are approved, they should be finalized and detailed specifications should be written. These specifications should document the proposed changes and help guide the implementation. The Ubuntu freezes define the deadlines for implementation.

Developing

In addition to implementing the features and/or improvements set in the roadmap, there are a number of tasks which will occur during each release cycle:

  • Xubuntu packages will be synced or merged with Debian as appropriate
  • Bugs reported by users will be reviewed, fixed, and/or passed upstream
  • Attempt to reduce our delta by pushing appropriate patches upstream
  • Evaluate the seeds to ensure we are shipping the optimal software
  • Work on improving and updating the Xubuntu documentation and artwork

Testing

Throughout the release cycle and even more so nearing the end, we will test Xubuntu to ensure that Xubuntu is a quality product that we are proud of. This includes testing that changes we have been making meet the release goals, work as expected, and do not cause regressions. Any tests run should be reported to the QA trackers. To read more about conducting tests and reporting them, refer to the QA tracker wiki page.

The Xubuntu testing team will help ensure that when milestone ISOs are released, all tests are completed and results reported to the tracker. Xubuntu testers will also test the daily builds, upgrading through supported release paths and running the development version of Xubuntu on a daily basis to help detect problems. The most important goals for testing the daily images are simply to find as many bugs as possible and report them with sufficient detail to the tracker along with the ISO testing result.

The Xubuntu testing team also helps test applications that are included in Xubuntu and make sure sufficient amount of testing is made and results reported to the packages tracker. Additional testing should be conducted when a new default application is to be included in the next Xubuntu release.

The team uses the following schedule for testing:

7 days before release

Gather people for milestone testing

5 days before release

Smoketest images - automatic, reported by Jenkins

3 days before release

Start milestone testing once appropriate testing area set up

Release day

Mark images ready on the ISO tracker once the release team is confident to do so

Releasing

When it comes time to deploy a release (both milestones and final) several conditions must be met:

  • Appropriate testing has been done on the image
  • There are no known bugs which cause data loss or damage to hardware
  • The image must not be oversized
  • Xubuntu must be of sufficient quality that it would not damage Xubuntu's, Ubuntu's, or any of the other flavors' reputation/image.

When a release is made, the Xubuntu Release Team must follow the release process specified below. The release process ensures that the new release has sufficient release notes and release announcement and that all release-specific communication is updated to inform about the new release. Where needed, advice from the Ubuntu release team should be asked for.

User Interface Freeze

Upload artwork and slideshow packages

Documentation String Freeze

Update translation templates
Upload documentation packages

Non-Language Pack Translation Deadline

Upload documentation and slideshow packages

14 days before release

Reminder to update the website FAQ (final release only)

7 days before release

Start preparing release notes and release announcement

Release day

Publish release announcement and notes
Update the website, IRC channel topics and social media outlets with new release information

After release (final release only)

Update the developer wiki to next release
Set up appropriate branches (documentation, ...) in Launchpad
Review and update this page

Maintaining

After a release is made, bugs and problems are bound to be reported. The period between the release and the start of the next release cycle is the optimal time to perform Stable Release Updates (SRU) for major bugs as long as developers do not forget to fix the issue in the next release as well, once the repository opens. Once the next release cycle has started, primary focus will be on the next release and the severity/importance of the SRU candidates will be more important when it comes to deciding whether an SRU will be performed or not.

Wiki maintaining

Update on release

Xubuntu/Toolbox/Menu

 Update the middle column header

Xubuntu/Roadmap/Goals/Codename

 Add a new roadmap page (easiest way is to copy over the old one)

Xubuntu/Roadmap

Point the include to the new roadmap subpage

 Xubuntu/Roadmap/Specifications/Codename

Add a new page with navigation: <<Navigation(children,1)>>

Xubuntu/Roadmap/Specifications

Update the form to point new specifications under the correct subpage

Update monthly

Xubuntu/TeamReports

Add links to xubuntu.org posts and meetings, also Team updates from meetings, see also: TeamReporting

Website maintaining

The website is a WordPress instance maintained by Canonical IS and overseen by the Xubuntu web team who can submit tickets to Canonical for any problems. Bugs for the team to review can be submitted on Launchpad.

Update on release

Update on point releases

Update on release EOL

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 knome)