Easiest way to upgrade from 1.2.2 to 1.2.3

[R0BINH00D]

Is there a way just to replace the updated files?

Sorry if it's a stupid question.

Dan

[RonnyK]

Dan,

for 1.2.2 to 1.2.3 is a diff-version available, with only the touched files.

As Sven wrote, it is just a mather of transfering the newer files over the existing ones. That is all, as there is no DB-change in this upgrade.

Ronny

[Pierre M.]

Once again the release annonce lacks simple, clear release notes.

I'd like every release annonce to state :

To upgrade from version prior to X, download package A and do this/that.
To upgrade from version Y, download package B and do this/that.
To upgrade from version above Z, download package C and do this/that.

(and "this/that" could be just "follow the upgrade procedure").

Users happyness is only 3 lines away. I look forward to reading this with the next release annonce.

Pierre M.

[Ted]

I look forward to reading this with the next release annonce.

I'm fine with this.  Can you write up what you would want it to say, so I can use it as a template?  Right now, the release process takes at least an hour.  It was 10-11 pm and I still had other work I had to finish before I could go to bed (and get up at 5.30a), so needless to say, brevity was my best option.  If we have a set of text I could use and just modify for these situations, it would be great.  Obviously, some releases might require different instructions, but 90% of them are the same thing...

Thanks!

[Pierre M.]

@Ted : I hope my message wasn't unfriendly. I appreciate very much the devteam response to the 1.2.2 issue and the very quick release of 1.2.3. I understand it was in a hurry, because of a security fix and in such a case releasing quickly is more important than wording. Thank you very much for this.

Now we are no more in the hurry of a security fix. I was thinking the needed template was the one I've written above :

To upgrade from version prior to X, download package A and do this/that.
To upgrade from version Y, download package B and do this/that.
To upgrade from version above Z, download package C and do this/that.

(and "this/that" could be just "follow the upgrade procedure").

I'd love to write the full guide and not only the template, but I don't know the internals of CMSms : database schema upgrade, how the installation/upgrade wizzard works... relating to version numbers. Sometimes an intermediate version install is required. Sometimes modules break or become deprecated. May be people who have installed and upgraded several versions with version jumps know which combinaitions work and which intermediate steps are needed (but I don't know). This is why I have suggested a template table. Once it will be filled up to current 1.2.3 it will be no pain to add the information for following releases, each 1.2.x and 2.x. Wouldn't it be cool if people knowing the internal "ruptures" post here "under version X" and "above version Z" guidelines or more ?

Happy new year everyone !

Pierre M.

[Pierre M.]

Thank you Sven for your response.

I like the drawing : simple, easy to read and to proceed, and easy to maintain. It is a nice picture of what I've tried to explain with "under X" and "above Z" : follow the arrow of your context.

The "heavy industrial" upgrade document seems to me "overthing" for CMSms. May be ~2 lines would suffice :
-modules M2, M4, and M5 pass the upgrade.
-modules M1 and M3 don't pass it. They are deprecated, users should use alternate Mx
The upgrade status of other modules is unknown.

Pierre M.