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.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.
Post Reply
User avatar
EXreaction
Registered User
Posts: 1555
Joined: Sat Sep 10, 2005 2:15 am

3.1 status?

Post by EXreaction »

With all the talk of different features that we had wanted to add for 3.1, I am curious as to what the actual status of those features is.

Who is working on what?

What do we want to get into 3.1 yet?

What do we want to get into 3.1 yet that nobody has yet to begin working on?

The feature lock date is not too far away, only 6 weeks.

User avatar
Highway of Life
Registered User
Posts: 1399
Joined: Tue Feb 08, 2005 10:18 pm
Location: I'd love to change the World, but they won't give me the Source Code
Contact:

Re: 3.1 status?

Post by Highway of Life »

Perhaps it would help (if it’s not being done already) if tickets were created for each potential feature for 3.1, that way it’s easier to see at a glance what is there and what is not. :)
Image

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

Re: 3.1 status?

Post by Oleg »

Looking at tickets may provide too much information. May I suggest a wiki page? With, say, the following sections:

1. Accepted features/changes

(List of changes that are committed to the 3.1 branch)

2. Pending features/changes

(List of changes on which work has been completed, but which have not been committed to the branch.)

3. Features/changes in progress

(List of changes currently being implemented.)

4. Features/changes under discussion

(List of changes that do not have any code written for them or that have unresolved issues that must be worked out before implementation can be finished.)

1 and 2 above would have tickets in the tracker, 3 and 4 will not. If 3 and 4 prove to be too hard to separate they of course can be merged.

Furthermore, maybe:

5. Postponed features/changes

(Changes that are desired but cannot be implemented in the given version for some reason.)

6. Rejected features/changes

(Changes that were discussed and rejected.)

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

Re: 3.1 status?

Post by naderman »

Actually the tracker seems like the perfect place for this. There are states for all the different lists you would like to have, and it should be a lot less work than maintaining yet another list somewhere ;-) Everything in progress now should have a ticket anyway, but I agree we should add more of the ideas asap to get a proper overview on the tracker.

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

Re: 3.1 status?

Post by keith10456 »

I'm not a developer but one would think a Ticket system would be best. It's easier (for the community and developers) to quickly see "what's what" on the various features, bugs, etc.

Post Reply