Separate the update script?

[joximu]

Hi ispCP friends

we just had a small discussion (sort of) in the german forum dealing with the question if it's better to separate the development of the update script (vhcs->ispCP but also RC2->RCx) from the main ispCP development so that ispCP can be "finished" in a reasonable time.
My thoughts: when ispCP is stable (prooved) for some time, there will be enough people to support the development of the updater. At the moment there are not enough vhcs users to test the half finished script and snce it's a blocker, the whole development is more or less blocked.

So: what do you think about it.
Just to see where you are :-)

Joximu

[BeNe]

I´m with you Joximu!
We should sperate it...

Greez BeNe

[Diggo]

Same here.
I think people will be more motivated, if they're going to write a upgradescript for a stable version. Guess there will be even more testers then.

[rsmithgs]

Seperate it.

If need be I'm sure the community can come up with some kind of best practice migration document in the mean time

[H-Man]

Also we need the RC3! (more than 500 bugs on RC2!)

Please sepearate it!

[Zothos]

yay, separate it! You have my voice joximu.

[Solvik]

Separate it so i can update from my buggy trunk

[gOOvER]

Solvik Wrote:Separate it so i can update from my buggy trunk

But the update from RC2 to RC3 is also ind this Script. So it's not possible to update. Maybe you can make this manual.

[H-Man]

Than we will have the update vom RC2 to RC3! ;-) Alone...

[joximu]

As rsmithgs wrote (http://www.isp-control.net/forum/separat...#pid16666) there will be ways to do the update...