New Versioning Policy

[momo]

About this news :

http://www.isp-control.net/news/news/isp...olicy.html

Nice
Good idea.

[Donni]

I fully agree. This should have already been done earlier, but better late than never ;-) I think it is the right decission. I hope that these "z"-Bugfix Releases will be released quite often - Not only to fix bugs but to keep up with the development of the integrated 3rd party software like phpMyAdmin etc.

CU
Donni

[RatS]

Hi Donni, thank you for your support. But we don't have the manpower for release often. The main problem is that it always takes around 1-1.5h to tag, pack, announce and make packages available. There is a formalised process to run, before release.

[Donni]

Sad to hear that, but I see where the problem is and I can understand that there are more important things to do than packaging...

But just to be sure that I got you right: Would a security problem for example like that in Squirrel Mail yesterday result in a V1.0.z release?

[RatS]

it will ... I'm packing omega 1.0.1 right now

[Donni]

Good news! I was a little afraid that this would end up in a "VHCS 2.4.7.1 Security Patch"-desaster. I think you know what I mean. I'm really glad that you don't do the same mistakes that were made by the old VHCS "team"...

[RatS]

The only disaster is the release process. It is not yet updated to the new policy. I hope I don't need to update the tag...

[monotek]

Will this update result in a new "1.0.0. updated" release again?

I think that would not be good.

If something changed in the source code (no matter what) the version number (z) should change too.

[petzsch]

There is a Version 1.0.2 on sf.net which extacts as a "tmp" directory (.tar.bz2 file).

The CHANGELOG is not updated and it is not mentioned on the isp-control.net download page (http://www.isp-control.net/download.html ). Is this package production ready and tested?

[RatS]

I fixed the files, sorry! The announcement is done.