GitHubのミラーです
https://github.com/FascodeNet/alterlinux-calamares
Revisión | a5091c8c3b2ae15e255ff22acfa9d46ad4e37eec (tree) |
---|---|
Tiempo | 2021-03-15 05:49:15 |
Autor | Adriaan de Groot <groot@kde....> |
Commiter | Adriaan de Groot |
Docs: massage the release-howto notes
@@ -12,6 +12,7 @@ website will have to do for older versions. | ||
12 | 12 | This release contains contributions from (alphabetically by first name): |
13 | 13 | - Anke Boersma |
14 | 14 | - Anubhav Choudhary |
15 | + - Neal Gompa | |
15 | 16 | |
16 | 17 | ## Core ## |
17 | 18 | - Uploading your log files (in case of installation failure) has been |
@@ -23,6 +24,8 @@ This release contains contributions from (alphabetically by first name): | ||
23 | 24 | |
24 | 25 | ## Modules ## |
25 | 26 | - A new QML-based *finishedq* module has been added. (Thanks Anke) |
27 | + - The *packages* module no longer supports *urpmi*; no Calamares- | |
28 | + consumers with that package manager seem to exist. (Thanks Neal) | |
26 | 29 | - The *users* module now can set a fixed username and prevent editing. |
27 | 30 | The *presets* configuration entry in `users.conf` can set a *loginName* |
28 | 31 | and a *fullName* and (independently) enable or disable editing of |
@@ -11,8 +11,29 @@ | ||
11 | 11 | > |
12 | 12 | > Most things are automated through the release script [RELEASE.sh](RELEASE.sh) |
13 | 13 | |
14 | +## (0) During a release cycle | |
15 | + | |
16 | +* Fetch latest translations from Transifex. We only push / pull translations | |
17 | + from *calamares* branch, so longer-lived branches (e.g. 3.1.x) don't get | |
18 | + translation updates. This is to keep the translation workflow simple. | |
19 | + The script automatically commits changes to the translations. It's ok | |
20 | + to do this during a release cycle. Run `sh ci/txpull.sh` | |
21 | + to fetch translations and commit the changes in one go. | |
22 | +* Push the strings to Transifex. From a checkout, run `ci/txpush.sh` | |
23 | +* Update the list of enabled translation languages in `CMakeLists.txt`. | |
24 | + Check the [translation site][transifex] for the list of languages with | |
25 | + fairly complete translations, or use `ci/txstats.py --edit` for an automated | |
26 | + suggestion. If there are changes, commit them. | |
27 | + | |
14 | 28 | ## (1) Preparation |
15 | 29 | |
30 | +* Drop the RC variable to 0 in `CMakeLists.txt`, *CALAMARES_VERSION_RC*. | |
31 | +* Edit `CHANGES` and set the date of the release. | |
32 | +* Commit both. This is usually done with commit-message | |
33 | + *Changes: pre-release housekeeping*. | |
34 | + | |
35 | +## (2) Release Preparation | |
36 | + | |
16 | 37 | * Make sure all tests pass. |
17 | 38 | ``` |
18 | 39 | make |
@@ -22,27 +43,16 @@ | ||
22 | 43 | an additional environment variable to be set for some tests, which will |
23 | 44 | destroy an attached disk. This is not always desirable. There are some |
24 | 45 | sample config-files that are empty and which fail the config-tests. |
25 | -* Pull latest translations from Transifex. We only push / pull translations | |
26 | - from master, so longer-lived branches (e.g. 3.1.x) don't get translation | |
27 | - updates. This is to keep the translation workflow simple. The script | |
28 | - automatically commits changes to the translations. | |
29 | - ``` | |
30 | - sh ci/txpull.sh | |
31 | - ``` | |
32 | -* Update the list of enabled translation languages in `CMakeLists.txt`. | |
33 | - Check the [translation site][transifex] for the list of languages with | |
34 | - fairly complete translations, or use `ci/txstats.py` for an automated | |
35 | - suggestion. If there are changes, commit them. | |
36 | -* Push the changes. | |
37 | -* Check defaults in `settings.conf` and other configuration files. | |
38 | -* Drop the RC variable to 0 in `CMakeLists.txt`, *CALAMARES_VERSION_RC*. | |
39 | -* Edit `CHANGES` and set the date of the release. | |
40 | -* Commit both. This is usually done with commit-message | |
41 | - *Changes: pre-release housekeeping*. | |
42 | - | |
43 | - | |
44 | -## (2) Release Day | |
45 | - | |
46 | + Note that the release script (see below) also runs the tests and | |
47 | + will bail out if any fail. | |
48 | +* Make sure the translations are up-to-date. There is logic to check | |
49 | + for changes in translations: a movable tag *translations* indicates | |
50 | + when translations were last pushed, and the logic tries to enforce a | |
51 | + week of latency between push-translations and a release, to allow | |
52 | + translators to catch up. Run `ci/txcheck.sh` to confirm this. | |
53 | + Run `ci/txcheck.sh --cleanup` to tidy up afterwards, and possibly pass | |
54 | + `-T` to the release script to skip the translation-age check if you | |
55 | + feel it is warranted. | |
46 | 56 | * Run the helper script `ci/RELEASE.sh` or follow steps below. |
47 | 57 | The script checks: |
48 | 58 | - for uncommitted local changes, |
@@ -119,7 +129,7 @@ ssb rsa3072/0xCFDDC96F12B1915C | ||
119 | 129 | the Calmares site or as part of a release announcement). |
120 | 130 | - Send the updated key to keyservers with `gpg --send-keys <keyid>` |
121 | 131 | - Optional: sanitize the keyring for use in development machines. |
122 | - Export the current subkeys of the master key and keep **only** those | |
132 | + Export the current subkeys of the primary key and keep **only** those | |
123 | 133 | secret keys around. There is documentation |
124 | 134 | [here](https://blog.tinned-software.net/create-gnupg-key-with-sub-keys-to-sign-encrypt-authenticate/) |
125 | 135 | but be careful. |