Pico 1.0 development & release process

[PhrozenByte]

The phpDocumentor folder of the gh-pages branch (introduced with Pico 1.0 resp. #260) should be automatically generated when both a release is published (create a distinct phpDocumentor folder for any minor release - see http://semver.org/) and someone commits to the master branch.

By the way, our ToDo list for the final 1.0.0 release:

• [x] Add "Build & Release process" to CONTRIBUTING.md, added in bef1502
• [x] Automatically generate phpDoc, added in bef1502
• [x] Website: Add "What's new" to upgrade.md, added in #276
• [x] Add a README.md for the gh-pages branch, added in https://github.com/picocms/Pico/commit/66bcb181cc82d760573a00d2bf472e4c7fb900c9
  • Don't forget to link to http://themes.iki-bir.com/webpaint/multipage/full/
• [x] Remove the Pico 0.X Plugins section from website with the final release of Pico 1.0.0
• [x] Update Pico Wiki
• [x] Wait for more feedback :smile:

Deferred:

• New default theme using Bootstrap 3 or (provided it has been released already) Bootstrap 4
• Website: Overhaul _development/ collection resp. development.md
• Website: Improve _cookbook/ collection resp. cookbook.html
  • Decide where to put links to it (inline user docs? website user docs? website dev docs?) and actually create the links

[PhrozenByte]

Done :gift_heart: :smiley:

I would like to thank all of you guys who made this possible, either by code and documentation contributions, general support, reporting issues, giving ideas or by participating in discussions, helping us to find the best solution. Pico and the community we built together are awesome, thank you!

Merry Christmas :santa: and a Happy New Year 2016 :fireworks: