Changes between Version 21 and Version 22 of Obsolete/Development/Templates/RelTagging

Timestamp:

Sep 15, 2006, 9:18:29 PM (18 years ago)

Author:

/C=FR/O=CNRS/OU=UMR8607/CN=Michel Jouvin/emailAddress=jouvin@…

Comment:

--

Obsolete/Development/Templates/RelTagging

@@ -17 +17 @@
 == Updating templates/branches ==
 
-No change must be done directly in a branch (`branches/version`), they should go to the trunk first (see [wiki:Development/RepUpdate Updating the repository]). Branch changes '''must''' be merge of changes from `trunk` and the commit message must state clearly the trunk revision interval corresponding to the commit. Generally, a branch commit includes several unrelated changes from trunk : this is not a problem as long as the commit message states it.
+No change must be done directly in a branch (`branches/version`), they should go to the trunk first (see [wiki:Development/Templates/RepUpdate Updating the repository]). Branch changes '''must''' be merge of changes from `trunk` and the commit message must state clearly the trunk revision interval corresponding to the commit. Generally, a branch commit includes several unrelated changes from trunk : this is not a problem as long as the commit message states it.
 
 The easiest way to incorporate relevant changes from the trunk into a branch is to use ``svn merge`` with a revision interval starting at the last revision merged into the branch (you can get it from the last commit message).
@@ -62 +62 @@
 As with branch commit, the message must be explicit about the main changes introduced and use the format proposed for branch commit.
 
-After creating the new tag, it is necessary to build a tarball corresponding to the release and attach it to the [wiki:Download Download] page. To create the tarball, first do a `svn export` of the tag and then a compressed tar of the export. For example, to create the tarball corresponding to release [milestone:gLite-3.0.2-2 gLite-3.0.2-2] :
+After creating the new tag, it is necessary to build a tarball corresponding to the release and attach it to the [wiki:Download/QWGTemplates Download] page. To create the tarball, first do a `svn export` of the tag and then a compressed tar of the export. For example, to create the tarball corresponding to release [milestone:gLite-3.0.2-2 gLite-3.0.2-2] :
 {{{
 cd /tmp
@@ -101 +101 @@
 
 Mailing list to send release announcement to are :
- * Quattor users mailing list mailto:project-lcg-gdb-quattor-wg@cern.ch
- * QWG mailing list
+ * Quattor users mailing list : [mailto:project-lcg-gdb-quattor-wg@cern.ch project-lcg-gdb-quattor-wg@cern.ch]
+ * QWG mailing list : mailto:project-quattor@cern.ch project-quattor@cern.ch]
 
 Update of the QWG wiki involves :
  * Updating the [wiki:WikiStart#Lastreleases main page].
- * Updating the milestone entry (`Roadmap`menu) corresponding to the release or, if none exists, create a new one and rename existing milestones if relevant.
+ * Updating the milestone entry (`Roadmap` menu) corresponding to the release or, if none exists, create a new one and rename existing milestones if relevant.
  * Updating the appropriate release notes by adding one entry to the release history as a link to the relevant milestone.