We have released the last minor release for Piwik 2.X and from now on there will be only patch releases that contain only important bug and security fixes for 2.15.X.

This means it is time to merge 3.0 => master and we will handle 2.15.X updates in another branch.

I'm wondering what the normal process for this is? I presume we should release a blog post asap to announce this change as some might have installed master via Git on development, testing, QA or production servers. We recommended to not use Piwik via Git so we should be fine here but possibly still need to notify users.

• Some custom plugins will become incompatible most likely
• If someone uses PHP 5.3 Piwik and updates via Git won't work anymore
• We also need to mention that Piwik 3.0 API's are not stable yet and there will be changes over time

Before we release a blog post about merging 3.0 we need to:

• Make Developer Changelog nice (group similar changes etc)
• Ideally we have some migration guides that makes it easier to update plugins, this should safe a lot of time when updating plugins
• Decide whether we go with PHP5.4 or PHP 5.5 Drop support for PHP 5.4, require PHP 5.5 #8156
• Make a decision re MySQL support: Increase minimum required Mysql version to 5.x in Piwik 3: are there benefits? #9107

Before merging Piwik 3.0 into master we need to:

• Make all submodule plugins compatible with 3.0 (eg Make it compatible with 3.0  plugin-AnonymousPiwikUsageMeasurement#14)

How much time should we give after the blog post till we merge 3.0 => master. 2 weeks?

Meanwhile:
We have to issue all PR's for 3.0 and not master. If we need a fix for 2.X we should cherry-pick