Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

improve upgrade docs & process for small upgrades #554

Closed
craigh opened this Issue · 10 comments

2 participants

@craigh
Owner

The upgrade document is apparently only for upgrading from 1.2.x -> 1.3.x and doesn't seem to relate to small incremental upgrades like 1.3.3 -> 1.3.4. I would like to upgrade but I don't know if I need to run upgrade.php or not. So, I check upgrade.php and it looks like it is all related to the first option (1.2.x->1.3.x) and isn't obvious what will happen upgrading from 1.3.3 -> 1.3.4. I'd like to see the upgrade.php file more documented (both in docs and inline) and maybe less procedural code? At least the upgrade doc should be clarified before the 1.3.5 release.

@ghost

The UPGRADING doc could be renamed UPGRADING-1.2.md since it's the special case, then have a separate doc for 1.3+ upgrades.

@ghost

Running upgrade.php is mandatory.

@cmfcmf
Owner

Great that the news articles on 1.3.6 say it isn't......

@ghost

ping @craigh

Running upgrade.php, even if there is nothing to do, it updates the core version in the database which is necessary for future upgraders to know what's what.

@craigh
Owner

that's why I asked you to read the article ;-) You've corrected it I assume?

@craigh craigh referenced this issue from a commit
Commit has since been removed from the repository and is no longer available.
@craigh craigh referenced this issue
Merged

update upgrade.php for v1.3.6 -> 1.3.7 #1384

0 of 2 tasks complete
@craigh
Owner

so the documentation has been removed from the repo. the docs on the community site are ancient. They need to be somewhere. do we want them in a github wiki? the repo? https://github.com/zikula/zikula-docs ?

@drak @paustian @cmfcmf

@cmfcmf
Owner

Could someone with apropriate permission please update the german news article as well (that upgrade.php has to be run)? @rallek @guite

@craigh
Owner

so - @drak - where to put upgrading and install docs?

@ghost

Can we leave this until nearer release? We dont know what the upgrade process will be entirely yet.

@craigh
Owner

I guess so. I'm just trying to close tickets. (#1384)

ok - I JUST (re)noticed this file: https://github.com/zikula/core/blob/1.3/UPGRADE-1.3.7.md

I guess that goes toward the proper docs that need to be created eventually. It should be separated from site admins and devs though.

anyway, I wanted to change this line in the upgrade.php file: https://github.com/zikula/core/blob/1.3/src/upgrade.php#L131

it has wrong information/links.

@craigh craigh referenced this issue from a commit in craigh/core
@craigh craigh update upgrade.php for v1.3.6 -> 1.3.7 refs #554 bdd3813
@shefik shefik referenced this issue from a commit
Commit has since been removed from the repository and is no longer available.
@craigh craigh referenced this issue
Closed

1.4.0 Release task list #1540

16 of 23 tasks complete
@ghost ghost closed this in 223435b
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.