Releasing 3.1.0-b2

[nickvergessen]

Todo List for 3.1.0-b2

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

   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-b2 package ✔
13. Test update from 3.0.12 to 3.1.0-b2 ✔
14. Test conversion from 2.0.x to 3.1.0-b2
15. Tag prep-release-3.1.0-b2 as release-3.1.0-b2 ✔

    Code: Select all

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

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

    Code: Select all

    git checkout develop-ascraeus
    git merge --no-ff prep-release-3.1.0-b2
    git checkout develop
    git merge --no-ff develop-ascraeus

18. Push changes ✔

    Code: Select all

    git push phpbb develop-ascraeus develop

19. Upload packages ✔
20. Make sure packages have correct permissions for downloading ✔
21. Set release date for version 3.1.0-b2 on the tracker ✔
22. Move all bug reports assigned to fix version "3.1.0-b2" to "3.1.0-b3" 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

[aleha]

Will you accept event requests in RC1?

[nickvergessen]

We will most likely accept event requests in every release

[Meis2M]

After beta 3, RC 1 will be release? And after RC 3 , final version will be release?

[NeilUK]

After beta 3, RC 1 will be release? And after RC 3 , final version will be release?

I doubt they would want to put a schedule together like that, there will be no set numbers for Betas, they will go to RC when ready whether there have been 3 betas or more. Then again there will be as many RC's as they need.

Ready when it's ready as always

[imkingdavid]

3 is not a magic number. We happened to have 3 alphas because that is how many we needed in this case. We will use as many beta and RC versions as needed to make the software stable.

[Alien_Time]

Beta 2 already! Wow... Great to see excellent progress. By the looks of it, we could have a final release by Xmas this year if it goes at this pace. Fingers crossed and v excited to view the progress.

[nickvergessen]

I plan to release B2 this weekend

[Kamahl19]

Great work, this way we will have 3.1 sooner then I expected (2015 ) . A little bit offtopic question, but do you plan to redesign buttons and input fields for prosilver before final release? The design of new "imageset" buttons is pretty good, it would be great to use it on all buttons/fields

[PayBas]

Being the selfish person that I am... I would like to see more pull requests merged before b2.