Skip to content
This repository has been archived by the owner on Aug 20, 2020. It is now read-only.

Releasing

Jump to bottom
kalyan kondapally edited this page Dec 2, 2013 · 20 revisions
Table of Contents
# Release We will perform a release every six weeks. Theoretically, this is to make a release every time Chromium makes a stable release (which is every six weeks). For now, we plan to do only major releases and no minor releases(Unless really needed). We have a milestone attributed to every release, this can be used to follow the fixes/features in our [issue tracker](https://github.com/01org/ozone-wayland/issues?milestone=1&state=open).

At this given point, we plan to only have one channel (stable). You can read more information about release channels here

# Branch Points

2013

Release Date(Thursday of the week) MileStone
33 Dec 19th
Santa
2014
Release Date(Thursday of the week) MileStone
34 Feb 20th
Valentine
35 April 3st
Easter
36 May 15th
Spring
37 Jun 26rd
Summer
38 Aug 21th
Harvest
39 Oct 2nd
Autumn
40 Nov 13th
ThanksGiving
## Source Release

We do a pre-release tag on the above-mentioned dates. The pre-release will be done with tip of the master on that given day. Next, few days will be more of a testing period and ensuring a stable release. At this point, stable means an at-least to be able to launch the browser and no new regressions. Once ready, we tag the release. The release tag may happen with same commit as pre-release tag or another depending on any issues found during testing phase. One should be able to download the source code tar ball from [release section] (https://github.com/01org/ozone-wayland/releases).

Every release has notes containing the following information:

  1. Release and milestone information.
  2. Supported Mesa and Wayland version.
  3. Bugs fixed in release.
  4. New features supported.
  5. Contributor names.

Before upgrading any existing release, please [read] (http://www.chromium.org/getting-involved/dev-channel#TOC-What-should-I-do-before-I-change-my-channel-) this.

## Binary Release

We don't intend to support any binary release. Nevertheless, we provide binaries for certain distributions for developers/individuals interested in giving feedback. Use it at your own risk. These will be generated from the source package tagged for a particular release. The name of source and corresponding binary tarball will be the same. Binaries can be downloaded from here

## Ozone-Wayland developers- Tagging a Release This section is for Project Maintainers who are responsible for doing the release.

TODO: Add instructions to tag/pre-release tag using command line.

A good starting point is to read GitHub documentation related to making releases

One need to follow these steps for tagging a new release:

  1. Create a release branch from tip of master branch and do a pre-release tag. One can do this directly in GitHub release section. For tag version provide the output of the command ./chrome --version. For release title provide 'Chromium Wayland Browser + tag version'. Check This is a pre-release option.
  2. Test for any regressions.
  3. If any additional changes needed from the Ozone - Wayland side, push the changes to release and master branch. Any changes needed from chromium side, add them into patches and push them to release branch only.
  4. Tag release. If nothing has changed from pre-release tag version, edit the pre-release tag and uncheck pre-release option. If we had pushed more changes into the release branch, tag tip of release branch(similar to 1 but don't select pre-release option).
  5. Delete any pre-release tags. Delete any release branch older than three release cycles.
  6. Generate binaries from source package and upload them to 01.org. There's a simple hack for preparing the binary, where it shows how to create a tarball from the build directory that excludes a few files.
Clone this wiki locally