New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't find any documentation on how to upgrade CakePHP generally #4105
Comments
@PoeticIntensity could you broadly outline what content you would expect from such a guide? Some bullet point list would be a good start. sarcasmOn |
There are tons of blog post and resources around it. Not sure that and a lot of other things are suited for cakephp docs, as they usually go out of scope of the actual documentation and would create a thousand pages "bible" of pages that will be harder to read through. |
I'm 👍 on getting some documentation on upgrading between minor versions. The CakePHP core team knows how to upgrade their apps - seems simple enough - but we can definitely provide a good workflow for more junior developers. For instance, I've seen people ask if they should just start with a fresh
Here is what I normally do (and can probably be made into a small section on the migration page):
|
I think including a short section on how to upgrade between patch and minor versions is probably useful. |
I think CakeFest is a good time to re-discuss this. Conference attendees might be interested to participate as some might need to upgrade yet. |
I've added upgrade notes to the 3.5 migration guide. Would it make sense to have minor or patch version upgrade instructions in the installation docs? |
Does |
The way I have it now composer won't update dependencies. We should probably tell people to use |
Migration guides for specific versions are a great help, but it would be awesome if there was a page that describe best practices on how to upgrade between cake versions generally. Both from git / svn / non-versioned code / etc...
savant told me to open this issue in IRC. If the page already exists, it's on him. :)
The text was updated successfully, but these errors were encountered: