Releasing 3.1.0-b1

[nickvergessen]

The list is getting shorter: http://tracker.phpbb.com/issues/?filter=11191
So be prepared for the next alpha or the first beta soon.

Todo List for 3.1.0-b1

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-b1 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-b1 from develop ✔
7. Update version number in prep-release-3.1.0-b1 to "3.1.0-b1" 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 "beta1" depending on all migrations added after alpha3 and alpha3 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-b1

   Code: Select all

   phpBB/docs/CHANGELOG.html

10. Update list of events in the Wiki: https://wiki.phpbb.com/Event_List ✔
11. Build packages ✔

    Code: Select all

    cd build
    phing

12. Test install of 3.1.0-b1 package ✔
13. Test update from 3.0.12 to 3.1.0-b1 ✔
14. Test conversion from 2.0.x to 3.1.0-b1
15. Tag prep-release-3.1.0-b1 as release-3.1.0-b1 ✔

    Code: Select all

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

16. Update version number in develop to 3.1.0-b2-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-b1 into develop ✔

    Code: Select all

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

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-a4 and 3.1.0-b1 on the tracker ✔
22. Move all bug reports assigned to fix version "3.1.0-a4/b1" to "3.1.0-b2" 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
28. Announce on QA mailinglist

[Kamahl19]

What will decide if it is alpha or beta? Is there any particular issue which needs to be finished before beta?

[Mess]

omgomgomg! Looks like we are getting close to a beta!

[nickvergessen]

@Kamahl19: it depends on whether we get all things fixed from the list above

[aleha]

Link in 3. is broken because of an extra h.
I see a b1,b2 and an RC1 in tracker. It would safe to assume that there would be more that one RC, correct?

[Mess]

Link in 3. is broken because of an extra h.
I see a b1,b2 and an RC1 in tracker. It would safe to assume that there would be more that one RC, correct?

Yes, that would be safe to assume.

Also, 1 blocker left at the time of writing this.

[nickvergessen]

Aaaaaaaand we're done.

We will release the new version tomorrow and will try to have a look at the outstanding PRs until then.

[Mess]

We need a big thumbs up smiley.

[Nfboy]

Sounds like the developers are on the right track, well done

[MaFeSa]

Sounds like the developers are on the right track, well done

+1

Thanks