Releasing 3.1.3

General discussion of development ideas and the approaches taken in the 3.x branch of phpBB. The next feature release of phpBB 3 will be 3.3/Proteus.
Forum rules
Please do not post support questions regarding installing, updating, or upgrading phpBB 3.2.x. If you need support for phpBB 3.2.x please visit the 3.2.x Support Forum on phpbb.com.

If you have questions regarding writing extensions please post in Extension Writers Discussion to receive proper guidance from our staff and community.
User avatar
nickvergessen
Former Team Member
Posts: 733
Joined: Sun Oct 07, 2007 11:54 am
Location: Stuttgart, Germany
Contact:

Releasing 3.1.3

Post by nickvergessen » Sat Dec 06, 2014 12:22 pm

Todo List for 3.1.3
Estimated release date: Jan 24, 2015
Freeze date: Jan 02, 2015 - Afterwards only critical blockers
  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.3 and correct any unreadable descriptions
  5. Check the feature hightlights wiki page for completeness
  6. Branch of prep-release-3.1.3 from develop-ascraeus

    Code: Select all

    git checkout develop-ascraeus
    git checkout -b prep-release-3.1.3
  7. Release candidate 1:
    Estimated release date: Jan 19, 2015
    • Update version number in prep-release-3.1.3 to 3.1.3.RC1 in these files:

      Code: Select all

      build/build.xml
      phpBB/includes/constants.php
      phpBB/install/schemas/schema_data.sql
    • Update version number in prep-release-3.1.3 to "3.1.3" in these files:

      Code: Select all

      phpBB/install/convertors/convert_phpbb20.php
      phpBB/styles/prosilver/style.cfg
      phpBB/styles/subsilver2/style.cfg
    • Create Migration "v313rc1" depending on all migrations added after v312 and v312 itself

      Code: Select all

      php phpBB/bin/phpbbcli.php dev:migration-tips
    • Commit Changelog generated from Tracker

      Code: Select all

      php build/build_changelog.php 3.1.3-RC1

      Code: Select all

      phpBB/docs/CHANGELOG.html
    • 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
    • Build packages

      Code: Select all

      cd build
      ../phpBB/vendor/bin/phing
    • Test install of 3.1.3-RC1 package
    • Test update from 3.1.2 to 3.1.3-RC1
    • Test update from 3.0.12 to 3.1.3-RC1
    • Test conversion from 2.0.x to 3.1.3-RC1
    • Tag prep-release-3.1.3 as release-3.1.3-RC1

      Code: Select all

      git tag -a release-3.1.3-RC1 -m "Tagging the 3.1.3-RC1 release."
    • Upload packages
    • Make sure packages have correct permissions for downloading
    • Update area51 downloads page
      src/Phpbb/Area51Bundle/Controller/DefaultController.php
    • Set release date for version 3.1.3-RC1 on the PHPBB3 and SECURITY trackers
    • Move all bug reports assigned to fix version "3.1.3-RC1" to "3.1.4-RC1" in the PHPBB3 and SECURITY trackers
    • Post language changes for translators
      https://gist.github.com/nickvergessen/8 ... 58fb1e1043

      Code: Select all

      git diff release-3.1.2 release-3.1.3-RC1 phpBB/language/ > language_changes_3.1.2_to_3.1.3-RC1.diff
    • Post style changes for style authors
      https://gist.github.com/nickvergessen/1 ... c8667dd3d4

      Code: Select all

      git diff release-3.1.2 release-3.1.3-RC1 phpBB/styles/prosilver/ > prosilver_changes_3.1.2to_3.1.3-RC1.diff
      git diff release-3.1.2 release-3.1.3-RC1 phpBB/styles/subsilver2/ > subsilver2_changes_3.1.2_to_3.1.3-RC1.diff
    • Post announcement on Area51 and Teams forum
    • Update versioncheck unstable version
    • Merge prep-release-3.1.3 into develop-ascraeus and develop-ascraeus into develop

      Code: Select all

      git checkout develop-ascraeus
      git merge --no-ff prep-release-3.1.3
      git checkout develop
      git merge --no-ff develop-ascraeus
    • Update version number in develop-ascraeus to 3.1.4-dev in these files:

      Code: Select all

      build/build.xml
      phpBB/includes/constants.php
      phpBB/install/schemas/schema_data.sql
    • Merge develop-ascraeus into develop

      Code: Select all

      git checkout develop
      git merge --no-ff develop-ascraeus
    • Push changes

      Code: Select all

      git push phpbb release-3.1.3
      git push phpbb prep-release-3.1.3
      git push phpbb develop-ascraeus develop
  8. Release candidate 2:
    Estimated release date: Jan 31, 2015
    • Update version number in prep-release-3.1.3 to "3.1.3-RC2" in these files:

      Code: Select all

      build/build.xml
      phpBB/includes/constants.php
      phpBB/install/schemas/schema_data.sql
    • Create Migration "v313rc2" depending on all migrations added after v313rc1 and v313rc1 itself

      Code: Select all

      php phpBB/bin/phpbbcli.php dev:migration-tips
    • Commit Changelog generated from Tracker

      Code: Select all

      php build/build_changelog.php 3.1.3-RC2

      Code: Select all

      phpBB/docs/CHANGELOG.html
    • 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
    • Build packages

      Code: Select all

      cd build
      ../phpBB/vendor/bin/phing
    • Test install of 3.1.3-RC2 package
    • Test update from 3.1.2 to 3.1.3-RC2
    • Test update from 3.0.12 to 3.1.3-RC2
    • Test conversion from 2.0.x to 3.1.3-RC2
    • Tag prep-release-3.1.3 as release-3.1.3-RC2

      Code: Select all

      git tag -a release-3.1.3-RC2 -m "Tagging the 3.1.3-RC2 release."
    • Upload packages
    • Make sure packages have correct permissions for downloading
    • Update area51 downloads page
      src/Phpbb/Area51Bundle/Controller/DefaultController.php
    • Set release date for version 3.1.3-RC2 on the PHPBB3 and SECURITY trackers
    • Post language changes for translators
      No changes, see above
    • Post style changes for style authors
      No changes, see above
    • Post announcement on Area51 and Teams forum
    • Update versioncheck unstable version
    • Merge prep-release-3.1.3 into develop-ascraeus and develop-ascraeus into develop

      Code: Select all

      git checkout develop-ascraeus
      git merge --no-ff prep-release-3.1.3
      git checkout develop
      git merge --no-ff develop-ascraeus
    • Push changes

      Code: Select all

      git push phpbb release-3.1.3
      git push phpbb prep-release-3.1.3
      git push phpbb develop-ascraeus develop
  9. Final Packaging:
    Estimated release date: Feb 01, 2015
    • Update version number in prep-release-3.1.3 to "3.1.3" in these files:

      Code: Select all

      build/build.xml
      phpBB/includes/constants.php
      phpBB/install/schemas/schema_data.sql
    • Create Migration "v313" depending on all migrations added after v313rc2 and v313rc2 itself

      Code: Select all

      php phpBB/bin/phpbbcli.php dev:migration-tips
    • Build packages

      Code: Select all

      cd build
      ../phpBB/vendor/bin/phing
    • Test install of 3.1.3 package
    • Test update from 3.1.2 to 3.1.3
    • Test update from 3.0.12 to 3.1.3
    • Test conversion from 2.0.x to 3.1.3
    • Tag prep-release-3.1.3 as release-3.1.3

      Code: Select all

      git tag -a release-3.1.3 -m "Tagging the 3.1.3 release."
    • Upload packages
    • Make sure packages have correct permissions for downloading
    • Disable area51 downloads page
      src/Phpbb/Area51Bundle/Controller/DefaultController.php
      https://github.com/phpbb/area51/commit/ ... 6b5ca6a82a
    • Set release date for version 3.1.3 on the PHPBB3 and SECURITY trackers
    • Post language changes for translators
      No changes, see above
    • Post style changes for style authors
      No changes, see above
    • Merge prep-release-3.1.3 into develop-ascraeus and develop-ascraeus into develop

      Code: Select all

      git checkout develop-ascraeus
      git merge --no-ff prep-release-3.1.3
      git checkout develop
      git merge --no-ff develop-ascraeus
    • Push changes

      Code: Select all

      git push phpbb release-3.1.3
      git push phpbb prep-release-3.1.3
      git push phpbb develop-ascraeus develop
  10. Update website downloads page
  11. Prepare an announcement in BBCode and E-Mail form

    Code: Select all

    git shortlog -sn release-3.1.2...release-3.1.3

    Code: Select all

    git diff --stat release-3.1.2...release-3.1.3
  12. Post announcement on phpBB.com
  13. Update versioncheck stable and unstable version
Member of the Development-TeamNo Support via PM

User avatar
Mess
Registered User
Posts: 199
Joined: Wed Jun 13, 2012 10:14 am

Re: Releasing 3.1.3

Post by Mess » Mon Dec 08, 2014 11:52 am

nickvergessen wrote:Todo List for 3.1.3
Estimated release date: Jan 10, 2015
Freeze date: Jan 02, 2015 - Afterwards only critical blockers
:o
Awesome to see an estimated release date this time around.
I for one really appreciate the new way of releasing updates.

User avatar
P_I
Registered User
Posts: 71
Joined: Fri Oct 31, 2014 4:56 am

Re: Releasing 3.1.3

Post by P_I » Mon Dec 08, 2014 4:43 pm

Count me along those who appreciate having this information available so that I can make plans for upgrading the forums that I manage.

MaFeSa
Registered User
Posts: 69
Joined: Sun Aug 26, 2012 1:44 pm

Re: Releasing 3.1.3

Post by MaFeSa » Mon Dec 08, 2014 5:48 pm

You are right the release date is a very useful thing!
Thanks

User avatar
nickvergessen
Former Team Member
Posts: 733
Joined: Sun Oct 07, 2007 11:54 am
Location: Stuttgart, Germany
Contact:

Re: Releasing 3.1.3

Post by nickvergessen » Mon Dec 08, 2014 9:22 pm

Just to make sure you get this right.
It's an estimated date not a release date. We plan to release on that date,
but if a critical bug comes up or real-life happens it might get moved 1-x week(s) in any direction.
Member of the Development-TeamNo Support via PM

User avatar
P_I
Registered User
Posts: 71
Joined: Fri Oct 31, 2014 4:56 am

Re: Releasing 3.1.3

Post by P_I » Tue Dec 09, 2014 12:36 am

Completely understand that "It's ready when it's ready" and these are estimates for planning purposes.

User avatar
Mess
Registered User
Posts: 199
Joined: Wed Jun 13, 2012 10:14 am

Re: Releasing 3.1.3

Post by Mess » Tue Dec 09, 2014 9:02 am

Understood and noted. And estimated date is very nice to have. :)

developer11
I've been banned
Posts: 17
Joined: Tue Dec 09, 2014 10:25 am

Re: Releasing 3.1.3

Post by developer11 » Wed Dec 10, 2014 9:44 am

I just disagree - with that much requests for improvement devs should postpone release date and implement suggestions one by one.

Nicofuma
3.2 Release Manager
3.2 Release Manager
Posts: 299
Joined: Sun Apr 13, 2014 1:40 am
Location: Paris

Re: Releasing 3.1.3

Post by Nicofuma » Wed Dec 10, 2014 11:10 am

developer11 wrote:I just disagree - with that much requests for improvement devs should postpone release date and implement suggestions one by one.
Well if you want to suggest a change in the release process create a new topic please. But I will explain to you our current process:
  • We release a feature version every year
  • We release a bug fix/minor version every month
  • We release a security version every time it is required
We don't want to postpone the release date, waiting for a new feature, anymore. A new feature shouldn't be a blocker, a blocker is a very important bug nothing else and the only thing that can postpone the release date is a blocker.

That's the release process: release what is ready and not what you wanted to see, if the feature needs more time give it more time... move it to the next release. And because a new feature (or a major UI improvement) needs a lot of tests it belongs to a feature release and not a bug fix/minor release.
Member of the phpBB Development-Team
No Support via PM

developer11
I've been banned
Posts: 17
Joined: Tue Dec 09, 2014 10:25 am

Re: Releasing 3.1.3

Post by developer11 » Wed Dec 10, 2014 12:50 pm

Nicofuma wrote: We don't want to postpone the release date, waiting for a new feature, anymore. A new feature shouldn't be a blocker, a blocker is a very important bug nothing else and the only thing that can postpone the release date is a blocker.

That's the release process: release what is ready and not what you wanted to see, if the feature needs more time give it more time... move it to the next release. And because a new feature (or a major UI improvement) needs a lot of tests it belongs to a feature release and not a bug fix/minor release.
I dont get it - you say that you do not want to wait anymore, but you have not implemented/rejected what has been suggested long ago..... and some features (or plans to implement them) go from one release to next one..... its better to say that sth will not be implemented than doing this......

Thats from me, cheers

Post Reply