4 # DEVELOPER_GUIDELINES 2009-03-19
7 o Try to mimick the style of the code that you are working in.
9 o Include a usage statement with every function/subroutine, no matter how
10 simple and self-explanatory that function is. Example:
12 # Combine essid and bssid to make a config file section name
16 # 'essid' -- string - AP ESSID
18 # 'bssid' -- string - AP BSSID
22 # string -- the bssid concatenated to a colon, concatenated to the essid
23 def make_section_name( essid, bssid ):
24 return essid + ':' + bssid
26 o Always give people credit in the CREDITS file.
31 --------------------------------------------------------------------------------
33 --------------------------------------------------------------------------------
34 o The current development branch is "master". It is intended for
35 feature additions and funky stuff. Unless you're just fixing a bug, or
36 updating the stable documentation, this is what you want.
39 --------------------------------------------------------------------------------
41 --------------------------------------------------------------------------------
42 o wifi-radar uses custom versioning (X.Y.[abf]Z):
44 X = major architectural change
46 o no special meaning is given to an odd or even number
47 [abf] = alpha, beta, or final
49 o aZ : no stability guarantees between releases
50 o bZ : new features are possible, but less wild than alpha
53 o Development releases may be made available unofficially.