3.1 Status

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.2/Rhea followed by 3.3.
Forum rules
Please do not post support questions regarding installing, updating, or upgrading phpBB 3.1. If you need support for phpBB 3.1 please visit the 3.1.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.
Oleg
Posts: 1150
Joined: Tue Feb 23, 2010 2:38 am
Contact:

3.1 Status

Post by Oleg » Tue Jan 11, 2011 10:13 am

Hi everyone,

I went through the blog post and topics in 3.1 RFC forum to compile an updated progress report on 3.1 Ascraeus.

Below, "merged" means the feature is in develop branch and effectively finished. "Patch in progress" means there is a complete or incomplete patch either in the ticket or in the RFC topic. Complete patches are complete according to patch submitters. These patches need to be reviewed, and if no issues are raised can be merged as is. Incomplete patches are those where either the submitter stated that additional work is needed or "complete" patches that were reviewed and comments or objections raised. "RFC only" means either there is no code attached to either the ticket or the RFC topic, or there is code which is potentially relevant but not in a form of patch for the particular RFC; in other words, essentially work on these RFCs has not started.

Merged: Patch in progress:
  • Avatar improvements, Gravatar RFC Ticket
    Status: v1 rejected - waiting for v2 from ckwalsh with better factoring
  • SQLite 3.0+ Support RFC Ticket
    Status: patch attached to RFC topic, needs to be turned into a proper git branch; some discussion going on in RFC topic pertaining to the patch
  • Updated BBcode engine RFC Ticket
    Status: partial implementation - discussion is in RFC topic - implementation needs to be finished
  • Switch to PHP timezone handling RFC Ticket
    Status: partial patch in RFC topic - needs to be finished
  • General Hook Architecture RFC Ticket
    Status: incomplete patch exists - stalled? - I am working on an alternative implementation
  • Improve User Pruning feature RFC Ticket
    Status: unreviewed patch on github - linked to ticket
  • Cleaning up the ACP UI RFC Ticket
    Status: unmerged patch in tracker - needs to be reviewed and merged
  • HipHop for PHP compatibility RFC Ticket
    Status: patch submitted - some comments in the RFC topic
RFC only:
Rejected:
As you can see, there are several features which have been implemented and need to be reviewed. While patch merging is done by phpBB developers anyone can review submitted patches and provide comments. Of course, for RFCs that do not have a complete implementation everyone is welcome to contribute code as well.
Last edited by Oleg on Sun Nov 20, 2011 8:07 am, edited 9 times in total.
Reason: Extensions merged

User avatar
Meis2M
Registered User
Posts: 411
Joined: Fri Apr 23, 2010 10:18 am
Contact:

Re: 3.1 Status

Post by Meis2M » Wed Jan 12, 2011 5:35 am

thank u
i think this feature not change again.

User avatar
Meow
Registered User
Posts: 12
Joined: Thu Mar 23, 2006 2:24 pm
Location: Taipei, Taiwan

Re: 3.1 Status

Post by Meow » Tue Jan 18, 2011 5:32 am

Does it mean that subsilver2 will not be removed in 3.1?

User avatar
naderman
Product Manager
Product Manager
Posts: 1727
Joined: Sun Jan 11, 2004 2:11 am
Location: Karlsruhe, Germany
Contact:

Re: 3.1 Status

Post by naderman » Tue Jan 18, 2011 7:25 am

Yes, that has been decided quite some time ago now.

User avatar
rxu
Registered User
Posts: 124
Joined: Tue Apr 04, 2006 4:28 pm
Contact:

Re: 3.1 Status

Post by rxu » Tue Jan 18, 2011 1:35 pm

Hmm. IIRC we've decided to remove it from the 3.1 package but still provide update and support (as a separate package).
Image

User avatar
bantu
3.0 Release Manager
3.0 Release Manager
Posts: 557
Joined: Thu Sep 07, 2006 11:22 am
Location: Karlsruhe, Germany
Contact:

Re: 3.1 Status

Post by bantu » Tue Jan 18, 2011 10:20 pm

I've added "Support for X-Accel-Redirect and X-Sendfile headers for attachment downloads" to the "Merged" list.

User avatar
MichaelC
Development Team
Development Team
Posts: 889
Joined: Thu Jan 28, 2010 6:29 pm

Re: 3.1 Status

Post by MichaelC » Wed Jan 19, 2011 6:56 pm

rxu wrote:Hmm. IIRC we've decided to remove it from the 3.1 package but still provide update and support (as a separate package).
As the original point was rejected but then this was built upon to be a change to the build script rather than complete removal but still as part of the same RFC, shouldn't the RFC be marked as merged (or what status it currently is) rather than rejected?
Formerly known as Unknown Bliss
psoTFX wrote: I went with Olympus because as I said to the teams ... "It's been one hell of a hill to climb"
No unsolicited PMs please except for quotes.

Oleg
Posts: 1150
Joined: Tue Feb 23, 2010 2:38 am
Contact:

Re: 3.1 Status

Post by Oleg » Wed Jan 19, 2011 10:23 pm

How about instead reviewing some of the patches that need to be reviewed?

User avatar
keith10456
Registered User
Posts: 523
Joined: Sat Apr 22, 2006 10:29 pm
Contact:

Re: 3.1 Status

Post by keith10456 » Wed Mar 30, 2011 12:58 am

Very useful... Thank you!

User avatar
sooskriszta
Registered User
Posts: 85
Joined: Wed Dec 29, 2010 7:23 pm

Re: 3.1 Status

Post by sooskriszta » Thu Jun 23, 2011 8:43 pm

Any updates?
OC2PS
Testfestés, Arcfestés, Csillámfestés

Alapanyagok, Képzések, Ismertetők
Hennafestés
GMAT coaching and MBA Admissions Consulting
formerly known as sooskriszta

Locked