just added

[bpratt]

BioALIEN Wrote:raph did contribute an update script which was later thrown away. Why? I don't know. What we need is a simple update method (automatic or manual) that could take people from Build A to Build B. It doesn't have to be very complicated.

Agreed, a way that people can confidently go from RC2c to the latest build.

Quote: We can start by posting a thread with "Changes from Build X to Build Y" and listing any alterations required. That way, us testers don't fall too much behind when we're testing each build and those of us who decide to use a latest build for their production site could go on using the bleeding edge code on their server in peace. I personally decided to use the latest build on a production environment. I rather use the latest code and risk having my server hacked than use RC2c and face an unstable panel. That's how much faith I've put into the latest build! It is a measure of how much work has gone into it by the devs. I am certain many of our members are doing the same thing!

I'm more than happy to move to the latest build, but I just don't feel confident of getting all the details/modifications done from nightly build to nightly build up to the latest nightly build.

Get those "Changes from Build x to Build Y" documentation done, and I'm sure we'll eventually get everyone up to the later builds.

Those of us on the old RC2c are wasting our time putting in bug reports, because they've been umpteen dozens of builds done since there, and what we find in this version is totally different to the current ones.

Quote:I'm not going to apologise for the long post, but I will leave you with actionable suggestions so we can resolve things around here:
1) Release ispCP RC3 based on current build. State that upgrade instructions will follow.
2) Write or update our documentation for moving from ispCP RC2c to RC3.
3) Write documentation for going from Build X to Build Y for every build that gets released.
4) Release ispCP RC4 by following 1 (above) and let the cycle continue until v1.0
5) Release ispCP 1.0 and promise an automatic update script for future builds.
6) Start writing documentation for migrating from VHCS 2.4.7 to ispCP 1.0. Let's survive to 1.0 then worry about bringing VHCS guys on board.

Damn good suggestions there... get a RC3 out to the masses of RC2c users, with hopefully upgrade instructions.

Any of us running RC2c will no doubt upgrade to RC3, and then finally we'll be able to start to report current bugs, rather than ones that have long since been resolved.


I believe Release Candidates should be no more than 2 or 3 months apart, and this current long gap is hurting us all.