Navigation Menu

Skip to content
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

Release 2.16.3 #10526

Closed
28 of 37 tasks
mattab opened this issue Sep 19, 2016 · 1 comment
Closed
28 of 37 tasks

Release 2.16.3 #10526

mattab opened this issue Sep 19, 2016 · 1 comment
Assignees
Milestone

Comments

@mattab
Copy link
Member

mattab commented Sep 19, 2016

Checklist for a successful 2.16.3 release:

  • Beta release cycle has started with the first beta release!
  • Forum support: regularly check all posts in Support & Bugs forum
  • Forum General questions: look for bugs & regressions in General questions forum
  • Backlog grooming: check issues without milestone if any one should be fixed in this release (72 issues to groom on sept 20th)
  • Check this list of issues across all Piwik repositories, where the milestone is set to Current sprint
  • Make CI builds of our official plugins piwik/plugin-* all green
  • Tag a new release for piwik/referrer-spam-blacklist and piwik/searchengine-and-social-list
  • Fetch our latest and greatest home-made libraries with composer update piwik/referrer-spam-blacklist piwik/searchengine-and-social-list piwik/piwik-php-tracker piwik/component-network,piwik/component-ini,piwik/component-decompress,piwik/component-cache
  • Fetch the latest composer libraries for all with composer update
  • Up to date submodules
  • Tag the RC candidate eg. 3.0.0-rc1
  • Check that the build is green
  • Package & release the Release Candidate
  • Post sticky thread in forum about RC,
  • inform RC release on social media
  • Release candidate cycle (at least 1 week cycle)
  • Fix all remaining 2.16.3 issues
  • 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
  • Up to date submodules
  • Prepare the Changelog entry for the new release:
    • 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
  • For each issue in the changelog:
    • 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.
  • Close milestone on Github
  • Release publicly the new stable version!
  • In Github release write
This release is meant for developers only and requires extra work to install it. 
 * Latest stable production release can be found at https://piwik.org/download/ ([learn more](https://piwik.org/docs/installation/))
 * Beta and Release Candidates releases can be found at https://builds.piwik.org/ ([learn more](http://piwik.org/faq/how-to-update/faq_159/))
  • Take screenshots of new features + draft a blog post showcasing what's new

(follows up 2.16.2 release)

@mattab mattab added this to the 2.16.3 milestone Sep 19, 2016
@mattab mattab self-assigned this Sep 19, 2016
mattab added a commit that referenced this issue Sep 28, 2016
mattab added a commit that referenced this issue Sep 29, 2016
* Fix depraction test: use assertDeprecatedMethodIsRemovedInPiwik3

* Fix Scheduled Reports sent one hour late in daylight saving timezones (#10443)

* convert hour to send report to/from UTC, to ensure it isn't affected by daylight savings

* adds update script to change existing scheduled reports to use utc time

* code improvement

* adds missing param

* Added new event Archiving.makeNewArchiverObject to  allow customising plugin archiving  (#10366)

* added hook to alllow plugin archiving prevention

* cr code style notes

* reworked PR to fit CR suggestions

* added PHPDoc for hook

* Event description more consistent

* UI tests: minor changes

* Comment out Visitor Log UI tests refs #10536

* Adds test checking if all screenshots are stored in lfs

* removed screenshots not stored in lfs

* readds screenshots to lfs

* 2.16.3-b4

* Issue translation updates against 2.x-dev

* language update

* Fix bug in widget list remove where the JSON object becomes array

* 2.16.3-rc1

* console command custom-piwik-js:update should work when directory is writable and file does not exist yet (#10576)

* followup #10449

* Fix test
(cherry picked from commit fac3d63)

* Prevent chmod(): No such file or directory

* Automatically update all marketplace plugins when updating Piwik (#10527)

* update plugins and piwik at the same time

* make sure plugins are updated with piwik

* use only one try/catch

* reload plugin information once it has been installed

* make sure to clear caches after an update

* fix ui tests

* make sure to use correct php version without any extras

* Additional informations passed in the hook "isExcludedVisit" (issue #10415) (#10564)

* Additional informations passed in the hook "isExcludedVisit" (issue #10415)

* Added better description to the new parameters

* Update VisitExcluded.php

* Remove two parameters not needed as better to use the Request object

* Update VisitExcluded.php

* remove extra two parameters in VisitExcluded constructor to prevent confusion (#10593)

* Update our libs to latest #10526

* Update composer libraries to latest #10526

* Update log analytics to latest

* When updating the config file failed (or when any other file is not writable...), the Updater (for core or plugins) will now automatically throw an error and cancel the update (#10423)

* When updating the config file failed (or when any other file is not writable...), the Updater (for core or plugins) will now automatically throw an error and cancel the update

* add integration test to check the correct exception is thrown when config not writabel

* New integration test for updater

* Make test better

* When opening the visitor profile, do not apply the segment (#10533)

* When opening the visitor profile, do not apply the segment

* added ui test for profile but does work for me

* next try to make ui test work

* add expected screenshot

* added missing doc
@mattab
Copy link
Member Author

mattab commented Oct 2, 2016

Well done everyone.

Piwik 2.16.3 changelog: https://piwik.org/changelog/piwik-2-16-3/

87 tickets have been closed by more than 24 contributors!

@mattab mattab closed this as completed Oct 2, 2016
@mattab mattab mentioned this issue Jan 9, 2017
37 tasks
sgiehl pushed a commit to matomo-org/plugin-CustomVariables that referenced this issue Jun 18, 2020
* Fix depraction test: use assertDeprecatedMethodIsRemovedInPiwik3

* Fix Scheduled Reports sent one hour late in daylight saving timezones (#10443)

* convert hour to send report to/from UTC, to ensure it isn't affected by daylight savings

* adds update script to change existing scheduled reports to use utc time

* code improvement

* adds missing param

* Added new event Archiving.makeNewArchiverObject to  allow customising plugin archiving  (#10366)

* added hook to alllow plugin archiving prevention

* cr code style notes

* reworked PR to fit CR suggestions

* added PHPDoc for hook

* Event description more consistent

* UI tests: minor changes

* Comment out Visitor Log UI tests refs #10536

* Adds test checking if all screenshots are stored in lfs

* removed screenshots not stored in lfs

* readds screenshots to lfs

* 2.16.3-b4

* Issue translation updates against 2.x-dev

* language update

* Fix bug in widget list remove where the JSON object becomes array

* 2.16.3-rc1

* console command custom-piwik-js:update should work when directory is writable and file does not exist yet (#10576)

* followup #10449

* Fix test
(cherry picked from commit fac3d63)

* Prevent chmod(): No such file or directory

* Automatically update all marketplace plugins when updating Piwik (#10527)

* update plugins and piwik at the same time

* make sure plugins are updated with piwik

* use only one try/catch

* reload plugin information once it has been installed

* make sure to clear caches after an update

* fix ui tests

* make sure to use correct php version without any extras

* Additional informations passed in the hook "isExcludedVisit" (issue #10415) (#10564)

* Additional informations passed in the hook "isExcludedVisit" (issue #10415)

* Added better description to the new parameters

* Update VisitExcluded.php

* Remove two parameters not needed as better to use the Request object

* Update VisitExcluded.php

* remove extra two parameters in VisitExcluded constructor to prevent confusion (#10593)

* Update our libs to latest matomo-org/matomo#10526

* Update composer libraries to latest matomo-org/matomo#10526

* Update log analytics to latest

* When updating the config file failed (or when any other file is not writable...), the Updater (for core or plugins) will now automatically throw an error and cancel the update (#10423)

* When updating the config file failed (or when any other file is not writable...), the Updater (for core or plugins) will now automatically throw an error and cancel the update

* add integration test to check the correct exception is thrown when config not writabel

* New integration test for updater

* Make test better

* When opening the visitor profile, do not apply the segment (#10533)

* When opening the visitor profile, do not apply the segment

* added ui test for profile but does work for me

* next try to make ui test work

* add expected screenshot

* added missing doc
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant