| 1 |
|
| 2 |
|
| 3 |
Rules developers should adhere to |
| 4 |
--------------------------------- |
| 5 |
|
| 6 |
|
| 7 |
|
| 8 |
- The decision when to move a version number is taken by the project |
| 9 |
administrator (currently bela). Just drop me an email if you want to |
| 10 |
increment a minor version number and I'll ok it. This prevents |
| 11 |
multiple developers from incrementing the same version number. With |
| 12 |
minor relases this is usually not a big deal and I'll do it |
| 13 |
immediately. |
| 14 |
|
| 15 |
- Do not modify core functionality (e.g. Protocol, GMS, FC, UNICAST, NAKACK, STABLE, CoordGmsImpl etc) |
| 16 |
before consulting with one of the project administrators. |
| 17 |
|
| 18 |
- New tarballs are done by the project administrator. I may delegate |
| 19 |
this in the future (to a number of people), but I decide when to add |
| 20 |
a new tarball to the download section. |
| 21 |
|
| 22 |
- Don't use any functionality found in JDKs higher than the one |
| 23 |
JGroups is currently using |
| 24 |
|
| 25 |
- Don't use any functionality not found in the reference JDK |
| 26 |
(e.g. from Microsoft's proprietary JDK implementation) |
| 27 |
|
| 28 |
- There are NO restrictions with respect to programming style. Just be |
| 29 |
coherent. SUN advocates use of fooBar() method style. |
| 30 |
|
| 31 |
- If you modify a file 'owned' by someone else, try to adhere to |
| 32 |
his/her style. Don't try to impose your style on that |
| 33 |
person. Ownership is basically who created the file. Once you obtain |
| 34 |
the ownership you can change the file if you want to. |
| 35 |
|
| 36 |
- Try to write test drivers for your module(s) and add them to |
| 37 |
JGroups/tests. We use TestNG (www.testng.org) for regression |
| 38 |
testing. It is pretty simple to add a new test to the directory, |
| 39 |
e.g. by just copying an existing test driver and modifying it. |
| 40 |
|
| 41 |
- Add the <dollarsign>Id<dollarsign> identifier to the top of all your |
| 42 |
files (<dollarsign> is a $, it cannot be written out otherwise it |
| 43 |
would get expanded by the CVS) |
| 44 |
|
| 45 |
- Use spaces instead of tabs, or make your IDE expand tabs to |
| 46 |
spaces. In Emacs this can be done via the following code: |
| 47 |
(setq-default indent-tabs-mode nil) |
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
Bela Ban ([email protected]) |
| 53 |
San Jose, March 13 2001 |
| 54 |
Dec 11 2002 |
| 55 |
April 5 2004 |
| 56 |
|
| 57 |
|
| 58 |
|