Piwigo 2.2 planning
----------------------------
hi, could you refresh the information on Piwigo 2.2, only for the purpose of knowing what date could be dating this version.
Are working very hard on this project, I really admire and appreciate them.
OK, yesterday I made a review on the issues in the bugtracker. I have renamed the "2.2" version to "2.20RC1". Among all issues marked as "Target Version = 2.2.0RC1", I have postponed some to 2.2.0RC2 (some bugs), and others to 2.3 or 2.4 (some features).
Some issues target 2.2.0RC1 are still opened but could get closed right now:
* [Bugtracker] ticket 2105 (rvelices, can you confirm this issue can be closed?)
... or with a small coding session:
* [Bugtracker] ticket 1289
* [Bugtracker] ticket 2040
* [Bugtracker] ticket 2018
* [Bugtracker] ticket 2025
(I try to finish this in the next hours)
The "rename X to Y" features are finished at engine level but not all languages are ready:
* [Bugtracker] ticket 2102
* [Bugtracker] ticket 1616
So I will close those issues but we will have "feature 2102" or "feature 1616" in the commit log when we add a new langage even if the feature is closed.
I would like to release Piwigo 2.2.0RC1 in the next 24 hours, unless someone has a specific blocking point.
Note: some bugs postponed to 2.2.0RC2 will require database upgrades
Offline
slow tags - fixed/closed
no blocking point RC1 soon (still some minor CSS/tpl commits pending)
Offline
It's OK for me
Offline
I'm in the last testing steps before 2.2.0RC1. I should release it tonight.
Offline
I'm preparing the release notes for version 2.2 (this takes quite some time, with screenshots and so on...). I still have bug with PNG resizing and then I'm ready to release version 2.2.0. Any blocking point on your side?
Offline
no blocking point on my side. I'm reworking the internal quick search engine though. Not sure I can commit before 2.2. Anyway this dev does not impact in anyway the db model, plugins, themes or languages.
Offline