Releasing 3.1-a1

[nickvergessen]

Release Highlights

New Features

• Extensions - Replacing MODs, Extensions are a new contribution type that require no file edits for installation. They can be easily installed via the ACP.
• AJAX - Several functions use AJAX to perform actions without a page reload.
• Notifications - Certain actions users perform while using your board will generate notifications to affected users. For instance, users can be notified when they are quoted in a post. There are multiple notification methods, including board notification and email notification. This feature can be expanded upon by extensions to add notification types (e.g. mentioning a user) and notifications methods (e.g. text message).
• Soft Delete - Posts and topics can now be "soft" deleted (i.e. removed from public view but retained in the database) to allow greater control over access of potentially unwanted posts and topics. Permissions dictate separately who can soft delete and who can hard delete posts.
• Gravatar - Avatars may now be fetched from the Gravatar service, in addition to the previously available options (upload, URL, and gallery).
• Attachment Improvements - Attachments can now be uploaded and downloaded in batches. Images that are too big can be resized before upload.
• OAuth Login - Login or register using Google, Bit.ly, or Facebook. Extensions can take advantage of this feature to add new authentication services.
• More Search Plugins - Besides MySQL Fulltext and phpBB native, PostgreSQL Fulltext and Sphinx are now supported.

Notable Changes / Bug Fixes

• Better Timezone handling - After selecting a timezone in the user control panel, daylight saving time adjusts automatically.
• Last topic in forum list - The title of the topic with the most recent post is now displayed as a link in the forum list along with the username and date.
• Improved Team Page - The team page is now better organized and can be customised via the administration control panel.
• Increased Maximum Subject Length - The maximum length of topic titles is now 120 characters.
• Improved Global Announcements - Global announcements are now linked to the forum they are posted in (and can be moved), allowing easier permission management.
• Improved MySQL Fulltext Search - A MySQL Fulltext Search Index now requires about 40% less table space.
• Resumable Attachment Downloads - Downloads of attachments can now be resumed after being interrupted or paused.
• Improved Page Titles - Browser page titles now begin with the forum/topic name, rather than the site name (which is now at the end).
• Improved Plural Support - Languages with non-trivial plural rules (e.g. Bosnian) are now properly supported by the language system.
• Text-based Buttons - Large buttons, such as Post Reply and New Topic, are now CSS and text, rather than images.
• Various prosilver Improvements - CSS3 rounded corners, removed duplicate colors, much more ...
• Improved Style Inheritance - Inheritance depth for template files is now unlimited (e.g. prosilver > awesomesilver > mysilver > yoursilver).

Notable Backend Changes

• Namespacing & Autoloading - New and refactored code is now namespaced and can be autoloaded.
• Migrations - Database update management. [[Migrations|[More Information]]]
• Dependency Injection - New and refactored code is now consistently following the Dependency Injection design pattern.
• Composer - Dependency manager.
• Routing and Controllers - Any views included by extensions (and, in future releases, all front-facing core pages, such as viewtopic and memberlist) can be given more "user-friendly" routes (e.g. something like /gallery/album/1 instead of something like gallery.php?view=album&id=1).
• Twig Template Engine - The template engine has been replaced with Twig while maintaining syntax compatibility.
• Modular Cron System - The cron system is now modular and extensions can supply cron jobs.

Todo List for 3.1-a1

1. Move all bug reports assigned to fix version "3.1-a1" to "3.1-a2" in Tracker. ✔
2. Create "3.1-a3" version on the tracker. ✔
3. Make sure phpBB/docs/AUTHORS is up to date. ✔
4. Make sure all reports in the security tracker are closed or invalid. ✔
5. Verify that the schema files match the version from develop/create_schema_files.php ✔
6. Branch of prep-release-3.1.0-a1 from develop ✔
7. Update version number in develop-ascreaus to "3.1.0-a1" 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 "alpha1" depending on all migration-dependency-graph leaves from 3.0 and 3.1 ✔
9. Go through Issues fixed in 3.1.0-a1 and correct any unreadable descriptions. ✔
10. Check the feature hightlights wiki page for completeness. ✔
11. Commit Changelog generated from Tracker ✔

    Code: Select all

    php build/build_changelog.php 3.1.0-a1

    Code: Select all

    phpBB/docs/CHANGELOG.html

12. Build packages ✔

    Code: Select all

    cd build
    phing

13. Test install of 3.1.0-a1 package ✔
14. Test update from 3.0.12 to 3.1.0-a1 ✔
15. Update list of events in the Wiki: https://wiki.phpbb.com/Event_List
16. Post language changes for translators ✔
17. Tag prep-release-3.1.0-a1 as release-3.1.0-a1 ✔

    Code: Select all

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

18. Update version number in develop-ascreaus to 3.1.0-a2-dev@naderman in these files:

    Code: Select all

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

19. Merge prep-release-3.1.0-a1 into develop ✔

    Code: Select all

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

20. Push changes ✔

    Code: Select all

    git push phpbb develop

21. Set release date for version 3.1.0-a1 on the tracker ✔
22. Upload packages ✔
23. Make sure packages have correct permissions for downloading ✔
24. Announce in QA team forum
25. Announce on area51 ✔
26. Update QA versioncheck
27. Announce on QA mailinglist

[Danielx64]

Now will upgrades from 3.0.12 be supported in the a1? Or that later? That one thing that I'm keen on testing.

[EXreaction]

We are not providing any sort of support for a1. Updating a 3.0 board to 3.1 should work, but it's certainly not recommended to do that for any reason other than testing.

[Meis2M]

is phpBB 3.0.12 is the end of 3.0.X series ?

[nickvergessen]

As we just started working on the first alpha of 3.1 I don't think so.

[MattF]

is phpBB 3.0.12 is the end of 3.0.X series ?

3.0.X ends when 3.1 is released (that means after all the alpha, and beta stage releases as well).

[nickvergessen]

is phpBB 3.0.12 is the end of 3.0.X series ?

3.0.X ends when 3.1 is released (that means after all the alpha, and beta stage releases as well).

We could also support 2 versions for sometime, but we will see that, when we reach that state.

[Danielx64]

We are not providing any sort of support for a1. Updating a 3.0 board to 3.1 should work, but it's certainly not recommended to do that for any reason other than testing.

Just saying, I didn't mean that I would go over to phpbb.com's support area and say that my board broke, it more like looking for bugs and errors.

[Danielx64]

is phpBB 3.0.12 is the end of 3.0.X series ?

3.0.X ends when 3.1 is released (that means after all the alpha, and beta stage releases as well).

We could also support 2 versions for sometime, but we will see that, when we reach that state.

It more like what happen when 3.0.x was out and 2.0.x was supported for some time.

[bantu]

is phpBB 3.0.12 is the end of 3.0.X series ?

is phpBB 3.0.12 is the end of 3.0.X series ?

3.0.X ends when 3.1 is released (that means after all the alpha, and beta stage releases as well).

From https://www.phpbb.com/community/viewtop ... &t=1958605

Following the release of phpBB 3.1 "Ascraeus", phpBB 3.0 "Olympus" will remain supported for a limited period of 6-9 months (further information on this will be released as it is decided upon) -- this version will remain compatible with PHP4.