Changes between Version 28 and Version 29 of MilestoneReleasesHowTo


Ignore:
Timestamp:
Dec 14, 2012, 6:29:10 AM (6 years ago)
Author:
planetcruiser
Comment:

added cache breaking hints

Legend:

Unmodified
Added
Removed
Modified
  • MilestoneReleasesHowTo

    v28 v29  
    66   * If grave new issues are raised in the ticket comments, make sure new tickets have been created and that those tickets mention the current ticket in the "Related tickets" part
    77   * Look through commits and ensure that newly added and changed code follows the ProgrammingGuideline. If not, contact the committer or fix it yourself. But this should not delay the release, so this is mainly intended as a notice for future commits
     8 1. Make sure to break caches
     9   * A common source of errors are outdated versions of !JavaScript and CSS files in users' caches after a release. We address this by adding "?1" or increments of it to resource file includes. Find out which resource files have been modified since the last major release by typing this:
     10{{{
     11git checkout master
     12git pull
     13git checkout develop
     14git pull
     15git diff --name-only --diff-filter=M master | egrep "\.(js|css)"
     16}}}
     17   * Do a full text search for the filenames you get above and make sure they got a "?1" (or higher) at the end, for example {{{searchmembers.js?1}}} in {{{main.js}}}.
    818 1. Write changelog
    919   * Create new wiki page for changelog, naming convention is "Changelog_x.x", see [wiki:Changelog_0.7] for example and use [wiki:Changelog_x.x] as a template.