File: RULES

package info (click to toggle)
libjgroups-java 2.12.2.Final-5
  • links: PTS, VCS
  • area: main
  • in suites: bullseye, buster, sid
  • size: 8,724 kB
  • sloc: java: 109,098; xml: 9,423; sh: 174; makefile: 4
file content (58 lines) | stat: -rw-r--r-- 2,066 bytes parent folder | download | duplicates (3)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58


		  Rules developers should adhere to
		  ---------------------------------



- The decision when to move a version number is taken by the project
  administrator (currently bela). Just drop me an email if you want to
  increment a minor version number and I'll ok it. This prevents
  multiple developers from incrementing the same version number. With
  minor relases this is usually not a big deal and I'll do it
  immediately.

- Do not modify core functionality (e.g. Protocol, GMS, FC, UNICAST, NAKACK, STABLE, CoordGmsImpl etc)
  before consulting with one of the project administrators.

- New tarballs are done by the project administrator. I may delegate
  this in the future (to a number of people), but I decide when to add
  a new tarball to the download section.

- Don't use any functionality found in JDKs higher than the one
  JGroups is currently using

- Don't use any functionality not found in the reference JDK
  (e.g. from Microsoft's proprietary JDK implementation)

- There are NO restrictions with respect to programming style. Just be
  coherent. SUN advocates use of fooBar() method style.

- If you modify a file 'owned' by someone else, try to adhere to
  his/her style. Don't try to impose your style on that
  person. Ownership is basically who created the file. Once you obtain
  the ownership you can change the file if you want to.

- Try to write test drivers for your module(s) and add them to
  JGroups/tests. We use TestNG (www.testng.org) for regression
  testing. It is pretty simple to add a new test to the directory,
  e.g. by just copying an existing test driver and modifying it.

- Add the <dollarsign>Id<dollarsign> identifier to the top of all your
  files (<dollarsign> is a $, it cannot be written out otherwise it
  would get expanded by the CVS)

- Use spaces instead of tabs, or make your IDE expand tabs to
  spaces. In Emacs this can be done via the following code:
  (setq-default indent-tabs-mode nil)




Bela Ban (bela@yahoo.com)
San Jose, March 13 2001
          Dec   11 2002
          April 5 2004