146
edits
Upgrade Mastodon: Difference between revisions
Steps to be followed for merging glitch + upstream stable release + instance's stable features
(Steps to be followed for merging glitch + upstream stable release + instance's stable features) |
|||
| Line 3: | Line 3: | ||
== Stages == | == Stages == | ||
=== History: Steps that were followed for Merging glitch + 4.2RC + our instance's features === | === Steps to be followed for '''merging glitch + upstream stable release + instance's stable features''' === | ||
* Sync the <code>[https://github.com/NeuromatchAcademy/mastodon/tree/glitch-clean-sync glitch-clean-sync]</code> branch to <code>glitch-soc/mastodon:main</code>: Open the branch page and click "'''sync fork'''" | |||
** The purpose of this branch is solely to serve as a replica of the parent <code>glitch-soc/mastodon:main</code> branch and so <code>[https://github.com/glitch-soc/mastodon/tree/glitch-clean-sync glitch-clean-sync]</code> is a locked read-only branch by design to protect it from force-pushes. | |||
*Create a new branch called custom-glitch(insert version number) from the <code>[https://github.com/NeuromatchAcademy/mastodon/tree/glitch-clean-sync glitch-clean-sync]</code> branch. For example, if we are upgrading to v4.2, the branch will be <code>[https://github.com/NeuromatchAcademy/mastodon/tree/custom-glitch4.2 custom-glitch4.2]</code> | |||
<syntaxhighlight lang="bash">git checkout origin/glitch-clean-sync | |||
git checkout -b custom-glitch4.2 </syntaxhighlight> | |||
* Merge <code>[https://github.com/NeuromatchAcademy/mastodon/tree/dev-stable dev-stable]</code> to the custom glitch branch | |||
<syntaxhighlight lang="bash">git merge origin/dev-stable </syntaxhighlight> | |||
* This branch should ideally have no merge conflicts if all the steps to keep the dev-stable branch clean and stable have been followed. | |||
** All the stable features stay on the <code>[https://github.com/NeuromatchAcademy/mastodon/tree/dev-stable dev-stable]</code> branch. To ensure that this branch stays clean, branch protections have been enabled. | |||
** Any features that have passed all the tests, have no errors (including linting errors), received approval from at least 1 reviewer, and are ready to be merged should be merged from the feature branch to the dev-stable branch in a separate process. See [[Mastodon/Hacking]] for details on contributing custom features to dev-stable. | |||
==== History: Deprecated Steps that were followed for Merging glitch + 4.2RC + our instance's features ==== | |||
all branches refer to those in [https://github.com/NeuromatchAcademy/mastodon NeuromatchAcademy/mastodon] unless specified otherwise. | all branches refer to those in [https://github.com/NeuromatchAcademy/mastodon NeuromatchAcademy/mastodon] unless specified otherwise. | ||
| Line 68: | Line 82: | ||
RAILS_ENV=production bundle exec rails db:migrate | RAILS_ENV=production bundle exec rails db:migrate | ||
</syntaxhighlight> | </syntaxhighlight> | ||
== Discord == | == Discord == | ||