source: extensions/net.sf.basedb.reggie/trunk/RELEASE @ 6309

Last change on this file since 6309 was 6309, checked in by Nicklas Nordborg, 13 months ago

References #1317: base.thep.lu.se is moving to https

Fixed links in the documentation of the Reggie extension.

File size: 3.0 KB
Line 
1===================================================
2Release procedure for the Reggie extension package
3===================================================
4
5Follow these instructions to release version A.B of
6this package. Please update the instructions if you
7find anything that is not correct or missing.
8
9 1. Make sure that all changes have been committed to
10    the trunk. Check with other developers if not
11    sure.
12
13 2. Update the version numbers.
14   
15    In build.xml:
16      <property name="version" value="A.B" />
17      <property name="delivery.version" value="..." />
18      <property name="depend.base-version" value="..." />
19   
20    The `delivery.version` property should only be changed if
21    the delivery client has been updated. 
22   
23    Run `ant update-version`. This should put the version
24    numbers in a lot of files, including,
25    META-INF/extensions.xml.
26   
27    Check (and update if needed) the README file and
28    and the wiki pages (see also step 8 and 9 below):
29   
30      https://baseplugins.thep.lu.se/wiki/net.sf.basedb.reggie
31      https://baseplugins.thep.lu.se/wiki/PluginDownload
32
33 3. Make sure that debug flags in javascript files have been reset.
34    Eg. search all *.js files for 'var debug' and check that it doesn't
35    say 'var debug = 1', 'var debug = true' or something similar.
36
37 4. Make sure that the code compiles and can be packaged.
38 
39    ant package
40   
41    will create the file 'reggie-A.B.tar.gz' in
42    the project directory.
43 
44 5. Make sure that the installation of Reggie works
45    and that the installation instructions are up to date.
46   
47 6. When everything is OK, commit any changes to subversion.
48
49 7. Create a tag in subversion:
50
51    svn copy https://baseplugins.thep.lu.se/svn/extensions/net.sf.basedb.reggie/trunk \
52        https://baseplugins.thep.lu.se/svn/extensions/net.sf.basedb.reggie/tags/A.B \
53        -m "Tagging release A.B"
54
55 8. Check out the tagged version in a new directory and create the release
56    package. NOTE! Do not use the package from step 4 since it may contain
57    non-versioned files from the regular working copy.
58   
59    ant package
60
61    Upload the packaged release as an attachment to:
62    https://baseplugins.thep.lu.se/wiki/net.sf.basedb.reggie
63
64 9. Edit the https://baseplugins.thep.lu.se/wiki/net.sf.basedb.examples.reggie
65    page:
66   
67    * Add a new entry to the Download table
68    * Change the README link to point to the tagged release. Use
69      the following wiki code:
70      [source:/extensions/net.sf.basedb.reggie/tags/A.B/README README]
71    * Check the information on the download page
72      https://baseplugins.thep.lu.se/wiki/PluginDownload
73      and make sure it is correct
74
7510. Create a new milestone: 'Reggie vA.B+1'
76
7711. Close the 'Reggie vA.B' milestone. Move
78    any remaining tickets to the newly create milestone.
79
8012. Update the version numbers.
81 
82    In build.xml: <property name="version" value="A.(B+1)-dev" />
83    Run `ant update-version` and commit the changes to
84    subversion:
85     
86    svn commit -m "Preparing for future release A.B+1"
87     
Note: See TracBrowser for help on using the repository browser.