Current time: 10-27-2021, 04:03 AM Hello There, Guest! (LoginRegister)


Post Reply 
New Versioning Policy
Author Message
sci2tech Away
Senior Member
****

Posts: 1,285
Joined: Jan 2007
Reputation: 23
Post: #31
RE: New Versioning Policy
Please provide more idea. This way we will adopt best of this, and have a beter version policy.
08-21-2009 09:03 PM
Visit this user's website Find all posts by this user Quote this message in a reply
momo Offline
Junior Member
*

Posts: 148
Joined: Jun 2008
Reputation: 1
Post: #32
RE: New Versioning Policy
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.
(This post was last modified: 08-21-2009 10:02 PM by momo.)
08-21-2009 10:01 PM
Find all posts by this user Quote this message in a reply
monotek Offline
Junior Member
*

Posts: 65
Joined: Dec 2006
Reputation: 0
Post: #33
RE: New Versioning Policy
I read about a repack of 1.0.3 in the timeline:

http://www.isp-control.net/ispcp/changeset/2428

Does this mean that there will be a second version of 1.0.3?

If so, please call it 1.0.4 instead.

A repack with same version name will only confuse people.
(This post was last modified: 12-24-2009 09:51 AM by monotek.)
12-24-2009 09:49 AM
Find all posts by this user Quote this message in a reply
Nuxwin
Unregistered

 
Post: #34
RE: New Versioning Policy
Changeset 2428

Timestamp:
12/21/09 04:00:53 (3 days ago)
Author:
nuxwin
Message:

Created new branch to fixed critical bugs before repack 1.0.3
Files:

1 copied

*
branches/omega-1.0.3-1 (copied) (copied from tags/omega-1.0.3)



No comment...
12-24-2009 10:00 AM
Quote this message in a reply
monotek Offline
Junior Member
*

Posts: 65
Joined: Dec 2006
Reputation: 0
Post: #35
RE: New Versioning Policy
Sorry for asking but maybe you can remember 1.0.0 and 1.0.0 updated...

1.0.3.1 woul be ok too.
12-24-2009 10:10 AM
Find all posts by this user Quote this message in a reply
RatS Offline
Project Leader
******

Posts: 1,854
Joined: Oct 2006
Reputation: 17
Post: #36
RE: New Versioning Policy
we learn from mistakes, too ... no worries.
12-24-2009 11:50 AM
Visit this user's website Find all posts by this user Quote this message in a reply
monotek Offline
Junior Member
*

Posts: 65
Joined: Dec 2006
Reputation: 0
Post: #37
RE: New Versioning Policy
thanks for info and merry xmas to the whole ispcp team :-)
12-24-2009 06:43 PM
Find all posts by this user Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 1 Guest(s)