[+1]  Adopt the coding convention described.

Craig


This is a vote to define the coding conventions for the Derby project per the db project guidelines http://db.apache.org/source.html

Vote closes  10:00am, Wednesday, August  15.


[+1]  Adopt the coding convention described.

[-1 ] Do not adopt the coding convention described.


The conventions outlined below will be published on the wiki page http://wiki.apache.org/db-derby/DerbyContributorChecklist


Derby uses the "Code Conventions for the Java Programming Language"

(http://java.sun.com/docs/codeconv/html/CodeConvTOC.doc.html) with these

amendments:

- space indentation (no tabs).

- Derby does not discourage deferring variable declaration to the first use.

- Lines should be limited to 80 characters

- @author tags should not be used at all


Note: There is a great deal of existing code that does not match this

convention. Changes to existing code should match the surrounding code

for readability, matching tabs or spaces as appropriate (see Tabs) .

Patches should not have white space diffs. Code and diffs should be

readable in  context.



Craig Russell

Architect, Sun Java Enterprise System http://java.sun.com/products/jdo

408 276-5638 mailto:[EMAIL PROTECTED]

P.S. A good JDO? O, Gasp!


Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to