Announcement

  •  » Engine
  •  » Piwigo 2.2 planning

#16 2011-01-17 06:08:44

Julian
Guest

Re: Piwigo 2.2 planning

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.

 

#17 2011-01-19 11:11:59

plg
Piwigo Team
Nantes, France, Europe
2002-04-05
13180

Re: Piwigo 2.2 planning

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, fixed] Browsing tags is slow if tags contains many photos (rvelices, can you confirm this issue can be closed?)

... or with a small coding session:

* [Bugtracker, ticket 1289, fixed] Add a clean fonction for tags
* [Bugtracker, ticket 2040, fixed] automatic rotation of the photo based on EXIF Orientation
* [Bugtracker, ticket 2018, fixed] setting user status to administrator should set the privacy level to admin as well
* [Bugtracker, ticket 2025, fixed] [history] by default connected users visits should be stored in history

(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, fixed] rename "image"/"item" into "photo"
* [Bugtracker, ticket 1616, fixed] rename "category" into "album"

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


Latest blog post (November 9th 2018) Why Flickr could not remain free for ever

Offline

 

#18 2011-01-19 13:36:40

rvelices
Piwigo Team
2005-12-29
1960

Re: Piwigo 2.2 planning

slow tags - fixed/closed
no blocking point RC1 soon (still some minor CSS/tpl commits pending)

Offline

 

#19 2011-01-20 01:03:38

ddtddt
Piwigo Team
Quetigny - France
2007-07-27
6745

Re: Piwigo 2.2 planning

It's OK for me


You love Piwigo so don't hesitate to participate, learn more on the "Contribute to Piwigo" page. If you don't have much time for contribution, you can also help the project with a donation.

Offline

 

#20 2011-01-20 16:21:29

plg
Piwigo Team
Nantes, France, Europe
2002-04-05
13180

Re: Piwigo 2.2 planning

I'm in the last testing steps before 2.2.0RC1. I should release it tonight.


Latest blog post (November 9th 2018) Why Flickr could not remain free for ever

Offline

 

#21 2011-03-30 00:31:18

plg
Piwigo Team
Nantes, France, Europe
2002-04-05
13180

Re: Piwigo 2.2 planning

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?


Latest blog post (November 9th 2018) Why Flickr could not remain free for ever

Offline

 

#22 2011-03-30 09:49:05

rvelices
Piwigo Team
2005-12-29
1960

Re: Piwigo 2.2 planning

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

 
  •  » Engine
  •  » Piwigo 2.2 planning

Board footer

Powered by FluxBB

github twitter facebook google+ newsletter Donate Piwigo.org © 2002-2019 · Contact