kilburn Wrote:Squrirelmail is distributed with the ispcp's core, so it's our responsibility to release a new version when it has to be updated.
Since that, these security release should not be "beta" "rc".
I am personnally excited every release for ispCP to see change in ispCP (not squirrel or else) and feel this project is rocking.
I did start admin stuff quite recently (16 month or so : kind of a green)
I did choose VHCS because ispCP was not stable yet.
I did change to ispCP 1 month later because of VHCS stories and innactivity (and I crashed my system)
Now the way this community works is GREAT.
For security release :
1) Keep same stable version number and notify (Squirrel Security Fix) (1.0.0_squirel_fix)
That way it is clear it is just the same ispcp with the fix
2) Also release a patch for the fix for people who doesn't want to do a full ispCP update for a security fix that is 100 char long.
Going thru updating ispCP can be long process on production server with all custom things and to verify everything is working properly after update. Plus doing it late night...
3) You need to rewrite the whole ispCP code...then release a new x.y.+ based on last release.
For stable release :
Slow versioning, wait for roadmap. Don't want to be version 10.0.0 next year. That makes me insecure.
If you feel you have enought stuff send the uncomplete stuff for next release and deploy.
Like it is right now.
Debian newly old school style.
Search
Member List
Calendar
Help
