Upgrade from 1.8.2 to 1.9

[aksinghv]

Hi,

I haven't tried but i am seeking information. Currently, I have my Testlink on 1.8.2. Now, I want to try tl19.0. If i upgrade the db from 1.8.2 to 1.9, can i use the db in 1.8.2?

IF this is not possible then i will create a dummy testing and try using 1.9.

Has anyone tried above?

Regards,
Anjani Singh

[Amaradana]

I also love to give a try for 1.9. But i am not sure where to get the file, can you please tell, where to download 1.9. Is that released? as for my knowledge this is not yet released.

[havlatm]

TestLink 19.0 is planned early in 2048.
We work hard on 1.9 version now. There is not available release at the moment because key changes are not ready yet.
You definitely cannot reuse DB schema between major releases (1.8 -> 1.9). New features requires also new DB schema.
Of course you can download the code directly from CVS with anonymous access.

[ccc123]

i tried this link from sourceforge:
but i just got empty folder :

SVN browse code, statistics svn co https://testlink.svn.sourceforge.net/svnroot/testlink testlink

CVS browse code, statistics, last commit on 2009-10-12 cvs -d:pserver:anonymous@testlink.cvs.sourceforge.net:/cvsroot/testlink login

cvs -z3 -d:pserver:anonymous@testlink.cvs.sourceforge.net:/cvsroot/testlink co -P modulename

could you pls point me to the details?
i have SVN and tortoiseSVN installed.

[havlatm]

Use CVS as described on sourceforge.net. No SVN.

[mukul]

Hi,

If I take the code from CVS and plan to update it every fortnight, will I be able to backup and restore the database? I hope "db schema" used in cvs code is same as that will be in final release.
If yes, is there any documentation available for the same?
I don't want to install 1.8 now n then 2 months later move to 1.9 which will involve new "db schema".

Regards
Mukul

[havlatm]

We grant DB schema support from RC1 release. I.e. you can use 1.9 version only on your responsibility without our support.
I recommend to use 1.8 version in any case now. We are preparing a migration script from 1.8 version, so there is no significant overhead for migration process.