Releasing 3.1.0-RC5

[nickvergessen]

Todo List for 3.1.0-RC5

1. Make sure phpBB/docs/AUTHORS is up to date ✔
2. Make sure Contributors have their ranks ✔
3. Make sure all reports in the security tracker are closed or invalid ✔
4. Go through Issues fixed in 3.1.0-RC5 and correct any unreadable descriptions ✔
5. Check the feature hightlights wiki page for completeness ✔
6. Branch of prep-release-3.1.0-RC5 from develop-ascraeus ✔

   Code: Select all

   git checkout develop-ascraeus
   git checkout -b prep-release-3.1.0-RC5

7. Update version number in prep-release-3.1.0-RC5 to "3.1.0-RC5" 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 "RC5" depending on all migrations added after RC4 and RC4 itself ✔

   Code: Select all

   php phpBB/bin/phpbbcli.php dev:migration-tips

9. Create the schema file with develop/create_schema_files.php ✔

   Code: Select all

   localhost/develop/create_schema_files.php

10. Commit Changelog generated from Tracker ✔

    Code: Select all

    php build/build_changelog.php 3.1.0-RC5

    Code: Select all

    phpBB/docs/CHANGELOG.html

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

    Code: Select all

    php phpBB/develop/export_events_for_wiki.php all

12. Build packages ✔

    Code: Select all

    cd build
    ../phpBB/vendor/bin/phing

13. Test install of 3.1.0-RC5 package ✔
14. Test update from 3.1.0-RC4 to 3.1.0-RC5 ✔
15. Test update from 3.0.12 to 3.1.0-RC5 ✔
16. Test conversion from 2.0.x to 3.1.0-RC5
17. Tag prep-release-3.1.0-RC5 as release-3.1.0-RC5 ✔

    Code: Select all

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

18. Update version number in prep-release-3.1.0-RC5 to 3.1.0-RC6-dev in these files: ✔

    Code: Select all

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

19. Merge prep-release-3.1.0-RC5 into develop-ascraeus and develop-ascraeus into develop ✔

    Code: Select all

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

20. Push changes ✔

    Code: Select all

    git push phpbb release-3.1.0-RC5
    git push phpbb prep-release-3.1.0-RC5
    git push phpbb develop-ascraeus develop

21. Upload packages ✔
22. Make sure packages have correct permissions for downloading ✔
23. Set release date for version 3.1.0-RC5 on the PHPBB3 and SECURITY trackers ✔
24. Move all bug reports assigned to fix version "3.1.0-RC5" to "3.1.0-RC6" in the PHPBB3 and SECURITY trackers ✔
25. Update area51 downloads page ✔
    src/Phpbb/Area51Bundle/Controller/DefaultController.php
26. Post language changes for translators ✔

    Code: Select all

    git diff release-3.1.0-RC4 release-3.1.0-RC5 phpBB/language/ > language_changes_3.1.0-RC4_to_3.1.0-RC5.diff

27. Post style changes for style authors ✔

    Code: Select all

    git diff release-3.1.0-RC4 release-3.1.0-RC5 phpBB/styles/prosilver/ > prosilver_changes_3.1.0-RC4_to_3.1.0-RC5.diff
    git diff release-3.1.0-RC4 release-3.1.0-RC5 phpBB/styles/subsilver2/ > subsilver2_changes_3.1.0-RC4_to_3.1.0-RC5.diff

28. Announce in QA team forum
29. Post announcement ✔
30. Update versioncheck ✔
31. Announce on QA mailinglist

[nickvergessen]

how many more RC versions will be?

As many as needed

[Crizzo]

all for so many secret =)

Would you be happier, if he told you "10!"?

[Geolim4]

More like around 15~~18

[Mess]

I really appriciate the short release cycles.
Keep up the good work!

[Kiweed]

I really appriciate the short release cycles.
Keep up the good work!

Yup ditto from me ...... thanks all for ya awesomeness work

I don't care if theres 50 RC's as long as when it comes out its a kickass bulletin board and rather buggless

11/10 so far from me anyways

[Alien_Time]

I don't care if theres 50 RC's as long as when it comes out its a kickass bulletin board and rather buggless

50 RCs = 100 years! If its gonna take 50 RCs no one would care even if its bugfull since we will be long gone..

[nickvergessen]

Currently a new RC comes ~3-4 weeks,
so 50 RCs would be like 3-4 years not 100.
But surely this is not what we are aiming for.

[code reader]

maybe the original question (how many more RCs) is not a very good one - it basically asks you to predict the future, which is not necessarily an easy thing to do.

OTOH, the answer ("as many as required"/"it's ready when it's ready") is also not a very good one - it does not point to any definition of "ready" or "required", and is completely vague.

stating some reasonable criterion might by desirable: surely we don't expect to get to "0 bugs" - this is both unrealistic and unnecessary.
can you guys try to state or outline (even roughly) what is the bar an RC has to reach in order to be considered "GA worthy"?

peace.

[nickvergessen]

Well a minimum is that all Blockers are resolved:
https://tracker.phpbb.com/issues/?filter=12593