How to update a product and commit it back

Please note: this document assumes that

1) You are using a unix-based OS
If you are using Windows, what are you waiting for to switch?

2) You have Subversion installed
If not, just install it using the Ports system. We recommend you do not use Fink.

3) You have write permissions to the VS repository
If you don't, ask for it.


REPOSITORY WORKFLOW
version 1.2 - 22 July 2006
Maintainer of this document: Atmasamarpan, together with Priyadarshan

Note: YOU ARE KINDLY REQUESTED TO PLEASE READ AT LEAST THE CHANGES
Changes are highlighted by BLUE face.

DEVELOPMENT

0.
Do not work unless and until you have a JIRA ticket open. No JIRA ticket, no development, please!. [You can open a ticket yourself if necessary!]

1.
A script or product will not be numbered in the trunk anymore. The VERSION.txt file will contain only and exactly the string that is associated to the respective ticket in JIRA (under the label "Affects Version/s".)
An EXAMPLE for vsCore would be (excluding the quote signs): "1.0-alpha-"

2.
Every time you commit to the repository, please add a proper line at the top of HISTORY.txt, specifying **exactly**:
- [added:, if new feature] or [fixed:, if bug fix] + URL to JIRA ticket + title of JIRA ticket
[name of developer that is committing]

(Please preserve the dash on the first line; the name of developer in brackets on the second line has to be left aligned with "fixed" or "added")

EXAMPLE 1:
- added: http://jira.vasudevaserver.org/browse/COR-13 Better place for site-wide properties
[dhyani]

EXAMPLE 2:
- fixed: http://jira.vasudevaserver.org/browse/COR-20 CSS does not show correctly in skin
[tejaswi]

3.
The first line of the HISTORY.txt addition (as seen above) is also the text to use as comment when you commit to the repository.

4.
After committing to the repository, please comment in the proper JIRA ticket the Revision Number returned by your svn client. The Revision Number pinpoints and guarantees the state of your code at any given moment.


STAGING

5.
If you need to stage a product on Stage or Sandbox, use the new URLs. For example, if you want to install “vsProduct“, revision number 755, use

To STAGE
http://supreme.vasudevaserver.net:7077/produpdate?repo=pub&product=vsProduct&tag=r755

To SANDBOX
http://akasha.vasudevaserver.net:7077/produpdate?repo=pub&product=vsProduct&tag=r755

[Please note that now it requires two parameters:
a) Product to install (example: vsCore)
b) Revision Number under which you committed the product (example: 755) ]

4.
After step 4, on the proper JIRA ticket request testing specifying the Revision Number of the product you want to be tested. [Please, DO NOT REQUEST TESTING without testing your code yourself thoroughly first!]

GOING LIVE

5.
Once your product has been tested and it is ready to go live, the tester will give the go ahead using the same JIRA ticket as above (and specifying the Revision Number.)

6.
A release manager (at this time, only Atmasamarpan or Priyadarshan) will specify which version number a given product will be assigned, writing it on the same ticket as above. The release manager will create a tag with any subversion client. A script will assign to VERSION.txt a string like this (excluding the quote signs): "1.0-alpha-r980"

7.
A system administrator will deploy the product on Production with the tag and refresh the product or restart both zope instances through zmi.