Changes between Version 25 and Version 26 of ReleaseGuidelines

Timestamp:

09/14/12 11:43:27 (12 years ago)

Author:

andrew_b

Comment:

--

ReleaseGuidelines

@@ -7 +7 @@
  * for stable: [https://www.midnight-commander.org/report/18 search] tickets with 'stable-candidate' keyword and in 'testing' stage, then apply commits to stable branch from all found tickets;
  * download translations from Transifex.net by command [http://help.transifex.net/features/client/index.html tx]{{{ pull --all}}} (see before: [wiki:TxRepoSetup how to set up local tx-repository])
- * store translations in gir-repo by commands:
+ * store translations in git repo by following commands:
 {{{
 cp -f $TX_REPO/<master|stable>/*.po $GIT_REPO/po
@@ -16 +16 @@
 git push origin <master|*-stable>
 }}}
- * Create new NEWS wiki-page for next version with empty template. Template may be copied from current NEWS wiki-page (without lists of tasks and bugreports);
- * Add content of current NEWS wiki-page to the doc/NEWS file in GIT-repo. Save in git by commands:
+ * create new NEWS wiki page for next version with empty template. Template may be copied from current NEWS wiki page (without list of tasks and bugreports);
+ * add content of current NEWS wiki page to the doc/NEWS file in git repo. Save it in git by following commands:
 {{{
 git add doc/NEWS
@@ -23 +23 @@
 git push origin <master|*-stable>
 }}}
- * create new tag in git by command (see before: [wiki:GpgSetUpForSigningReleases how to set up your gpg-key for signing releases])
+ * create new tag in git by command (see before: [wiki:GpgSetUpForSigningReleases how to set up your gpg key for signing releases])
 {{{
 git tag -s <version>
@@ -38 +38 @@
  * make checksums for archives:
 {{{
-sha256sum mc-*tar.* >sha256.sum
+sha256sum mc-*tar.* > sha256.sum
 }}}
  * upload source packages and checksums to the special upload area;
@@ -51 +51 @@
 === Notes: ===
  * Cleanup branch should be named as XXXX_cleanup; where XXXX it's a number of current release ticket.
- * The cleanup branch should be created by demand and should be voted and merged to main branch ASAP. Don't keep the cleanup branch in development stage longer that this needed.
+ * The cleanup branch should be created by demand and should be voted and merged to main branch ASAP. Don't keep the cleanup branch in development stage longer that it needed.
  * Activity around cleanup branch should occur in release ticket.
- * Cleanup branch should be deleted after merging to main branch. Cleanup branch may be recreated with same name in any count of times.
+ * Cleanup branch should be deleted after merging to main branch. Cleanup branch may be recreated with same name with any count of times.
  * Cleanup branch shouldn't be merged to main branch in a week before release