Closed milanm closed 4 years ago
I sympathise that the upgrade process could be made simpler and more intuitive.
We already have release notes which take quite a bit of time and effort to edit and keep up-to-date, especially given Academic is a very flexible framework - so we attempt to consider a unified upgrade path that can work for many different setups and configurations.
Unfortunately, although Academic is extremely popular, it does not currently have many regular contributors contributing to the roadmapped milestones and the release process. To develop automatic and robust upgrade scripts/tooling would require significant additional effort and hence it would help to have more regular contributors to enable high effort features like this.
Also, this feature is perhaps something that might be better suited to being implemented in Hugo. If Hugo team defined a process and tooling for upgrading themes including config and front matter, that could provide a standardised approach for upgrading any theme.
This issue has been automatically marked as stale because it has not had any recent activity. The resources of the Academic team are limited, and so we are asking for your help.
If this is a bug and you can still reproduce this error on the master
branch, please reply with all of the information you have about it in order to keep the issue open.
If this is a feature request, and you feel that it is still relevant and valuable, please tell us why.
This issue will automatically close soon if no further activity occurs. Thank you for your contributions.
Its really hard to catch with new versions, as there are multiple things to be manually fixed in the every version. If you miss a few versions there is a lot of work to be done. Consider making some updater to automatically update to new versions when they are released.