New Versioning Policy

[momo]

Quote:1. Do as BioALIEN says, I like his idea.
2. Don't follow any convention about minor releases. The ones announced as stable are stables, the others aren't.
3. Append a "build" number, so "x.y.z" releases are the stable ones. "x.y.z-1.t" are betas/rc's. This way, we would release 1.0.1.xx (increasing xx) until 1.0.2 is ready, then 1.0.2.xx until 1.0.3 is ready, etc.)

This sounds good.

By the way, why do you need to release a security patch for something that isn't ispCP core ?
Isn't it admins responsibility to patch security holes for this ?