source: docs/HACKING @ 168

Last change on this file since 168 was 168, checked in by boris, 19 years ago
  • created a documentation folder (docs) and moved HACKING manual there
File size: 1.6 KB
Line 
1Stuff that are nice to know if you want to hack on MDT.
2
3I. Making a release
4
5I.I. Motivational blurb
6
7The intention of this section is to serve as both a cheat sheet while making a
8release and to formalize the release building process. A more formal release
9procedure should help avoid making stupid misstakes and hopefully improve the
10quality of the releases. All in all, doesn't everyone love processes?
11
12I.II. The release procedure
13
14 * start with a clean workspace, e.g. use File->Switch Workspace and switch to
15   an empty folder
16   
17 * checkout (as Plugin-Projects) from whatever branch/revision you want to make
18   a release:
19   
20    - org.modelica.mdt
21    - org.modelica.mdt.tests
22   
23 * run the regression tests
24   If some of the tests fail, go back to the drawing board.
25   
26 * remove all projects from the workspace
27 
28 * make a version tag in the repository
29 
30 * checkout from version tag location in the repository:
31
32    - org.modelica.mdt
33    - org.modelica.mdt.feature
34    - org.modelica.mdt.site
35 
36 * update version number in org.modelica.mdt/plugin.xml
37 
38 * run 'PDE tools'->'Build site' from the context menu of
39   org.modelica.mdt.site/site.xml
40
41 * export the update site to a public webserver, use 'Export'->'File System'
42   wizard. Make sure that both features and plugin directories are exported.     
43   
44 * test with a clean eclipse installation that the MDT-plugin installs correctly
45   from the update site. Use the Help->'Software Updates'->'Find and Install...'
46   Check that it runs as expected.
47   
48 * enjoy the release party!
49 
Note: See TracBrowser for help on using the repository browser.