Gentlemen,
Sherif's point is another good one.
I don't think it will be such a major job to get this new facelift version
stable - after having had another evening on it last night. The beauty of
the discrete script arrangements implicit in the design, together with
reliance on only the now quite mature php, means that we are unlikely to
have a flaky system that works then doesn't for reasons that are very
difficult to determine. This I believe is another serious advantage we have
over many of the commercial accounting software vendors. Stability is always
going to be better when dependencies are fewer and we are not using bleeding
edge software as the basis of the system.
My preference is to minimise the administration of the software development
process and concentrate on new functionality so far as possible. To that end
I would like to use the CVS as the current developement version and release
file archives as production/stable only when it has undergone sufficient
testing.
I am keen to encourage other people to contribute too but this does carry
with it a requirement on me to audit the quality - which in itself is time
consuming. So far we have been fortunate to have highly skilled
contributions from Sherif and Shane. I am thinking that a code of practise
with just a minimal rule set as to how contributions can be made easily and
minimise the risks and administration. I will draft something up and get
your comments.
Phil
|
