@mattab opened this Issue on August 29th 2018 Member

Checklists for a successful Matomo release

Work on the release in the beta cycle:

Steps towards Release Candidate 1:

  • [ ] Tag a new release for matomo-org/referrer-spam-blacklist and matomo-org/searchengine-and-social-list
  • [ ] Fetch our latest and greatest home-made libraries with composer update matomo-org/referrer-spam-blacklist matomo-org/searchengine-and-social-list matomo-org/matomo-php-tracker matomo-org/component-network,matomo-org/component-ini,matomo-org/component-decompress,matomo-org/component-cache
  • [ ] Fetch the latest composer libraries for all with composer update
  • [ ] Up to date submodules
  • [ ] Tag the RC candidate
  • [ ] Check that the build is green
  • [ ] Package & release the Release Candidate
  • [ ] Post sticky thread in forum about RC
  • [ ] Notify translators that they should check if any translation keys got updated.
  • [ ] inform RC release on social media

The final checks before the stable release:

  • [ ] Release candidate cycle (at least 1 week cycle)
  • [ ] Fix all remaining issues in the milestone
  • [ ] All open source plugins builds are green on master with latest RC
  • [ ] Plugins that needed a version bump are now released on the marketplace
  • [ ] Synchronise translations from transifex
  • [ ] Submodules are up to date

Prepare the Changelog entry:

  • [ ] Mark that the release has a major DB upgrade
  • [ ] Use our github changelog generator to generate the changelog using this config.js
  • [ ] Add to changelog any new issues or FAQ added since first RC
  • [ ] Add to changelog the security issues fixed, if any
  • [ ] Do not publish publicly the changelog yet. This also ensures security issues are not publicly visible until the stable release.
  • [ ] Change changelog published date to the release day

    Check the developer changelog is complete, by looking over each issue:

  • [ ] is this issue relevant to developers? let's mention it in the Developer changelog
  • [ ] is this issue's title descriptive and useful to people scanning our changelog?
  • [ ] are the right labels applied to the issue? (issues tagged with labels such as Bug, Enhancement, Major are grouped together in the changelog)
  • [ ] if this issue was sponsored, we note the sponsor organisation in the changelog.

Merge 3.x-dev branch into master:

:boom: Release :rocket:

  • [ ] Close milestone on Github
  • [ ] Release publicly the new stable version by running ./scripts/build-package.sh 3.x.y from here and waiting 5 minutes
  • [ ] In Github release we write
## [Matomo 3.3.0 Changelog](https://matomo.org/changelog/matomo-3-3-0/)

This Github download (below) is only meant for developers and it will require extra work to install it. 
 * Latest stable production release can be found at https://matomo.org/download/ ([learn more](https://matomo.org/docs/installation/)) (recommended)
 * Beta and Release Candidates releases can be found at https://builds.matomo.org/ ([learn more](http://matomo.org/faq/how-to-update/faq_159/))
  • [ ] Take screenshots of new features + draft a blog post showcasing what's new
  • [ ] Create this 'Release Matomo 3.*' issue in the next release milestone
@mattab commented on November 14th 2018 Member

we discussed an issue with the translations cc @sgiehl and @Findus23 where for example the Opt-out iframe was released with a partial German translation also showing english text. This was because translators were not notified early enough that there was new text in the recently merged code.

To prevent or limit this problem in the future, could we maybe send a message on Transifex to all translators, for example 1 week before the release (or when we cut the RC)? this way they will always have a few days to translate any new english strings. Thoughts?

@sgiehl commented on November 14th 2018 Member

For the frequently maintained languages it should be enough to simply have one or better two weeks between rc and release. But for sure you need to give me a ping before the final release is done, so I can push a last translation update.
And feel free to publish an announcement on transifex as soon as an RC get's published: https://www.transifex.com/matomo/matomo/announcements/

@Findus23 commented on November 14th 2018 Member

Speaking of translations: It would be amazing if the Matomo Tag Manager is now available screen would be translated as it's the first time most people will come across tag manager. And if they don't understand what it is, they might dismiss it immediately.

Powered by GitHub Issue Mirror