• 21 January 2009: minutes
• 10 October 2008: minutes
• 16 January 2008: minutes
• 6 November 2007:

The information in this document in good part reflects and extends the Tag & Release policy document of Geant4.

1. General Policy
2. Technical Information

1. General Policy

The following points applies when a patch to an existing Geant4 release is made:

• Every class should have at least one constructor and a destructor even if it does nothing or is defined to do nothing. If a class does not have a constructor there is no guarantee of how objects of that class will be initialized, whilst data members should be explicitly initialized therein. When the constructor dynamically allocates memory, a destructor must be added to return the memory to the free pool when an object gets cleaned up.

• The public, protected and private keywords must be used explicitly in the class declaration in order to make easier code readability.
• English and self-explaining names for constants, variables and functions should be used for code readability. Possibly avoid the use of underscore "_" characters within variables or function names (ex. theTotalEnergy, SetEnergyTable(), GetTrackPosition(), ...).
• The code must be properly indented (ex.