Merge lp:~vila/brz/prepare-3.0.0 into lp:brz

Proposed by Vincent Ladeuil on 2018-09-15
Status: Merged
Approved by: Jelmer Vernooij on 2018-09-15
Approved revision: no longer in the source branch.
Merge reported by: The Breezy Bot
Merged at revision: not available
Proposed branch: lp:~vila/brz/prepare-3.0.0
Merge into: lp:brz
Diff against target: 49 lines (+28/-4)
1 file modified
doc/developers/releasing.txt (+28/-4)
To merge this branch: bzr merge lp:~vila/brz/prepare-3.0.0
Reviewer Review Type Date Requested Status
Martin Packman 2018-09-15 Approve on 2018-09-15
Review via email:

Commit message

A simplified process for alpha releases

Description of the change

I think this summarizes the discussion around 3.0aN releases

To post a comment you must log in.
Martin Packman (gz) wrote :

I'm not sure the announcing the source freeze bit is relevant, change look fine though.

review: Approve
Vincent Ladeuil (vila) wrote :

source freeze bit was modified to remove the mailing list that doesn't exist, it's not related to alpha releases, just feedback from previous MP

The Breezy Bot (the-breezy-bot) wrote :

Running landing tests failed

lp:~vila/brz/prepare-3.0.0 updated on 2018-09-15
7117. By Jelmer Vernooij on 2018-09-15

Fix sort order for walkdir items.

Merged from

7118. By Vincent Ladeuil on 2018-09-15

A simplified process for alpha releases

Merged from

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
=== modified file 'doc/developers/releasing.txt'
--- doc/developers/releasing.txt 2018-09-14 09:31:24 +0000
+++ doc/developers/releasing.txt 2018-09-15 13:29:38 +0000
@@ -163,6 +163,31 @@
163Doing a particular release163Doing a particular release
166alpha releases
1693.0.0 will start to be released as alpha as integrating plugins and porting
170to python3 (while maintaining python2 compatiblity) desserve to be testing
171in the wild by people understanding the risks.
173That being said, the whole test suite has been preserved and enriched in the
176Alpha releases will happen as source only (tarballs) and the process is
179Note that the intent is to come back to beta releases as soon as possible so
180the alpha releases won't happen again.
182The process for releasing an alpha release is therefore:
183- upload a tarball to launchpad,
184- upload a tarball to pypi,
185- mail,
186- post an annoucement on the home page.
188Uploading tarballs are described below, just use alpha versions (3, 0, 0,
189'alpha', 1) in ``./breezy/``
166Update the source code191Update the source code
@@ -460,10 +485,9 @@
460Announcing the source freeze485Announcing the source freeze
463#. Post to the ```` and488#. Post to the ```` list, saying that the source
464 ```` lists, saying that the source has489 has been frozen. Be extra clear that this is only a *source* release
465 been frozen. Be extra clear that this is only a *source* release targeted490 targeted at packagers and installer builders (see
466 at packagers and installer builders (see
467 <>). This is the cue for491 <>). This is the cue for
468 platform maintainers and plugin authors to update their code. This is492 platform maintainers and plugin authors to update their code. This is
469 done before the general public announcement of the release.493 done before the general public announcement of the release.


People subscribed via source and target branches