[RFC] Use composer.json for styles and track phpBB version

Note: We are moving the topics of this forum and it will be deleted at some point

Publish your own request for comments/change or patches for the next version of phpBB. Discuss the contributions and proposals of others. Upcoming releases are 3.2/Rhea and 3.3.
User avatar
naderman
Product Manager
Product Manager
Posts: 1727
Joined: Sun Jan 11, 2004 2:11 am
Location: Karlsruhe, Germany
Contact:

Re: [RFC] Separate style and phpBB versions in style.cfg

Post by naderman » Wed Apr 04, 2012 7:47 pm

Oleg wrote:My understanding of the current situation is:

1. Any style or modification can break at the next minor version.
2. Support team only supports the latest version.

Until these policies are changed specifying a single compatible version seems at least sensible to me.
I guess that makes sense.

User avatar
Marc
Development Team Leader
Development Team Leader
Posts: 128
Joined: Thu Sep 09, 2010 11:36 am
Location: Munich, Germany

Re: [RFC] Separate style and phpBB versions in style.cfg

Post by Marc » Sun Apr 08, 2012 9:05 pm

I like the idea, both JSON & the seperation of the style versions, although it shouldn't be a hard limit. Warning the user that the style is outdated should be enough.

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

Re: [RFC] Separate style and phpBB versions in style.cfg

Post by naderman » Thu Apr 19, 2012 12:37 am

I'll merge the change now anyway to resolve problems with the updater. I still think we should go the same route as with extensions, and make this the same composer.json format.

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

Re: [RFC] Separate style and phpBB versions in style.cfg

Post by naderman » Thu Apr 19, 2012 12:52 am

I created a ticket for composer.json format for styles: http://tracker.phpbb.com/browse/PHPBB3-10824

Post Reply