Releasing 3.1.0-a3

[nickvergessen]

Sorry it took so long, Christmas and some other events delayed A3, but here we go:

Todo List for 3.1.0-a3

1. Make sure phpBB/docs/AUTHORS is up to date. ✔
2. Make sure all reports in the security tracker are closed or invalid. ✔
3. Go through Issues fixed in 3.1.0-a3 and correct any unreadable descriptions. ✔
4. Check the feature hightlights wiki page for completeness.
5. Verify that the schema files match the version from develop/create_schema_files.php ✔
6. Branch of prep-release-3.1.0-a3 from develop ✔
7. Update version number in prep-release-3.1.0-a3 to "3.1.0-a3" in these files: ✔

   Code: Select all

   build/build.xml
   phpBB/includes/constants.php
   phpBB/install/convertors/convert_phpbb20.php
   phpBB/install/schemas/schema_data.sql
   phpBB/styles/prosilver/style.cfg
   phpBB/styles/subsilver2/style.cfg

8. Create Migration "alpha3" depending on all migrations added after alpha2 and alpha2 itself ✔

   Code: Select all

   php develop/migration_tips.php

9. Commit Changelog generated from Tracker ✔

   Code: Select all

   php build/build_changelog.php 3.1.0-a3

   Code: Select all

   phpBB/docs/CHANGELOG.html

10. Build packages ✔

    Code: Select all

    cd build
    phing

11. Test install of 3.1.0-a3 package ✔
12. Test update from 3.0.12 to 3.1.0-a3 ✔
13. Test conversion from 2.0.x to 3.1.0-a3 ✔
14. Update list of events in the Wiki: https://wiki.phpbb.com/Event_List
15. Tag prep-release-3.1.0-a3 as release-3.1.0-a3 ✔

    Code: Select all

    git tag -a release-3.1.0-a3 -m "Tagging the 3.1.0-a3 release."

16. Update version number in develop to 3.1.0-a4-dev in these files: ✔

    Code: Select all

    build/build.xml
    phpBB/includes/constants.php
    phpBB/install/schemas/schema_data.sql

17. Merge prep-release-3.1.0-a3 into develop ✔

    Code: Select all

    git checkout develop
    git merge --no-ff prep-release-3.1.0-a3

18. Push changes ✔

    Code: Select all

    git push phpbb develop

19. Upload packages ✔
20. Make sure packages have correct permissions for downloading ✔
21. Set release date for version 3.1.0-a3 on the tracker ✔
22. Move all bug reports assigned to fix version "3.1.0-a3" to "3.1.0-a4" in Tracker ✔
23. Update area51 downloads page ✔
24. Post language changes for translators ✔
25. Announce in QA team forum ✔
26. Announce on area51 ✔
27. Update QA versioncheck - Not done for Alpha
28. Announce on QA mailinglist

[JAiAk]

When?

[Un1matr1x]

When?

When ever point in the list above has a ✔ - what mean that this point is done

[Darkness_demoN]

Please make it Important. That new users will find it faster

[Barrnet]

Any notice of beta?

[Mess]

A the time of this reply Steps 24-28 are still missing from the Alpha release.
Why would they skip those and start a new release, a beta?

[leschek]

Mess: Look on the same steps at Releasing 3.1.0-a2.

[EXreaction]

A Beta will be released when all the blocker bugs for all Alpha releases and blocker bugs for the first Beta release are completed.

[John P]

In the nightly build page I find files for 3.1.0-a4, is that correct?

[nickvergessen]

its 3.1.0-a4-dev, we just do that so that there are not multiple packages for 3.1.0-a3