Diese Seite mit anderen teilen ...

Informationen zum Thema:
Forum:
WinDev Forum
Beiträge im Thema:
4
Erster Beitrag:
vor 1 Jahr, 6 Monaten
Letzter Beitrag:
vor 1 Jahr, 6 Monaten
Beteiligte Autoren:
Steve Hodgman, Peter Holemans, Fabrice Harari

What is recommended Upgrade Procedure when using SCM?

Startbeitrag von Steve Hodgman am 01.04.2016 21:18

G'day all,
I have all my code in SCM.
There are many internal components shared across many separate projects.
I want to upgrade to V20 (Yes, I know I am a little late) to first verify that everything works before fully committing the upgrade from V19

I was wondering how others deal with this process.
Do you "copy sideways", use a Branch?
My concern is that if something breaks in the latest version then how do I revert?
Thanks,
Steve H.

Antworten:

Hi Steve,

I'm ot using the SCM, so there may be a less brute force approach, but in your case I would start by doing a full backup of the SCM DB, directly in the HF control center.

Best regards

von Fabrice Harari - am 04.04.2016 13:40
Hi Steve,

Best way is to use a branch that keeps a copy of the V19 project in SCM.

Cheers,

Peter H.

von Peter Holemans - am 04.04.2016 13:53
Yes, Thanks Fabrice, I was planning on a backup of the SCM :-)

Peter, I reckoned that a Branch was the way to go but I could not work out how the Internal Components would be handled. They are shared among other projects and they would need to be "branched" as well.

After reading the online SCM doco and having a ponder this is what I think I will do.

I have a Project that is"the home" of all of my Internal Components. I was thinking that I should open that and create a branch with new folder for the V20 version. Then open the branched project in V20 and upgrade the branched components to V20 and check everything back in.

Then for each project that uses the internal Components I would need to:
1) Create a branch with new folder for that project.
2) Open the Branched project in V19 and remove all of the Internal Components that it uses (lots of errors generated but everything still ok)
3) Open the Branched project in V20 to upgrade the base project code.
4) I would then need to manually add all of the required Branched (V20) Internal components to this project.
5) Recompiling should result in no errors (of course!)
6) Repeat this process for each project that I want to upgrade to V20.

Sounds a little convoluted but that is the only way I can see to keep the project as is (V19) while having V20 code available for evaluation, testing and new development.

As I drop support for a version (say V19) I would "Retrieve Modifications" from the V20 Branch so then I would have V20 as the main project/Component folders.

The Branch and Sub-Branch model sounds like it would allow more than two versions to be supported. Just repeat the above process with sub-branches from the Branch. Not sure I will be doing that as it sounds un-necessary in my case.

Anyway, thanks for the responses and I will proceed with V20 and see how it goes. First thing though is a SCM Backup!
Cheers,
Steve H.

von Steve Hodgman - am 04.04.2016 23:42
Zur Information:
MySnip.de hat keinen Einfluss auf die Inhalte der Beiträge. Bitte kontaktieren Sie den Administrator des Forums bei Problemen oder Löschforderungen über die Kontaktseite.
Falls die Kontaktaufnahme mit dem Administrator des Forums fehlschlägt, kontaktieren Sie uns bitte über die in unserem Impressum angegebenen Daten.