if 3.0.7 is the last of the 3.0?

osu9400

Joined: 2007-05-14
Posts: 11

Posted: Thu, 2013-04-25 18:42

does this mean 3.1 or 4.0 is next? Anyone have a feature list or timeline?

jnash

Joined: 2004-08-02
Posts: 814

Posted: Thu, 2013-04-25 18:55

3.1 is up on blocks now being worked on by the mechanics!

3.0.7 is the expected last of 3.0.x series.

No ETA's at the moment, but at least a couple of months. Also, I don't think there is a published feature list as of yet.

Things currently in the works as known:

* Upgrade to Kohana 3.3 framework
* Upgrade to JQuery 1.9

shadlaws

Joined: 2012-03-14
Posts: 183

Posted: Fri, 2013-04-26 12:33

Just to add to what jnash said...

Gallery 3.1 will be largely/entirely compatible with 3.0 databases and photos, so the migration process for user data will be relatively painless (a teensy but more than a typical 3.0.x -> 3.0.y upgrade, but not by much). Additionally, most/all of the external interface will be the same (album/photo addresses stay the same, REST API will work the same, RSS feeds look the same, etc.). This is why we're still calling it 3.x as opposed to 4.x.

However, the internal interface (i.e. module design) will be a big shift to get back on track with the new frameworks. In other words, we have our work cut out for us . But, it'll totally be worth it since, once done, we open up a lot more doors for cool modules and features!

Take care,
Shad

MikeLFD

Joined: 2013-03-22
Posts: 79

Posted: Fri, 2013-04-26 13:23

A minor suggestion if I may.
When publishing updates (security fixes, etc.) would it be possible to just push the files that were affected?

Not that it's a major headache but pushing out the complete version again does cause (or did in my case) one to
loose fixes that were applied (flowplayer changes,etc.)
Again it's not a major thing (myself, I always keep a seperate copy of any file I make changes to) Just a thought.

floridave

Joined: 2003-12-22
Posts: 27300

Posted: Fri, 2013-04-26 16:14

MikeLFD, We did that in G2 and it did cause some confusion for users. It would add additional work to the dev team and package releases. Here is just a short list that gets done behind the scenes: https://github.com/gallery/gallery3-packaging/blob/master/ReleaseChecklist
As well as adding more queries in the support forums. like "what is a patch" and "how do I make it work".....

I guess one could make a diff of each version as you apply the upgrades and post them in the news story for the benefit of others.
I use http://winmerge.org/ to track what I change/merge and it works in my work flow. Each admin has his/her own flow that a diff might not fit into.

Dave

_____________________________________________
Blog & G2 || floridave - Gallery Team

osu9400 Joined: 2007-05-14 Posts: 11	Posted: Thu, 2013-04-25 18:42
	does this mean 3.1 or 4.0 is next? Anyone have a feature list or timeline?
	XUser login Username: * Password: * Create new account Request new password
jnash Joined: 2004-08-02 Posts: 814	Posted: Thu, 2013-04-25 18:55
	3.1 is up on blocks now being worked on by the mechanics! 3.0.7 is the expected last of 3.0.x series. No ETA's at the moment, but at least a couple of months. Also, I don't think there is a published feature list as of yet. Things currently in the works as known: * Upgrade to Kohana 3.3 framework * Upgrade to JQuery 1.9

shadlaws Joined: 2012-03-14 Posts: 183	Posted: Fri, 2013-04-26 12:33
	Just to add to what jnash said... Gallery 3.1 will be largely/entirely compatible with 3.0 databases and photos, so the migration process for user data will be relatively painless (a teensy but more than a typical 3.0.x -> 3.0.y upgrade, but not by much). Additionally, most/all of the external interface will be the same (album/photo addresses stay the same, REST API will work the same, RSS feeds look the same, etc.). This is why we're still calling it 3.x as opposed to 4.x. However, the internal interface (i.e. module design) will be a big shift to get back on track with the new frameworks. In other words, we have our work cut out for us . But, it'll totally be worth it since, once done, we open up a lot more doors for cool modules and features! Take care, Shad

MikeLFD Joined: 2013-03-22 Posts: 79	Posted: Fri, 2013-04-26 13:23
	A minor suggestion if I may. When publishing updates (security fixes, etc.) would it be possible to just push the files that were affected? Not that it's a major headache but pushing out the complete version again does cause (or did in my case) one to loose fixes that were applied (flowplayer changes,etc.) Again it's not a major thing (myself, I always keep a seperate copy of any file I make changes to) Just a thought.

floridave Joined: 2003-12-22 Posts: 27300	Posted: Fri, 2013-04-26 16:14
	MikeLFD, We did that in G2 and it did cause some confusion for users. It would add additional work to the dev team and package releases. Here is just a short list that gets done behind the scenes: https://github.com/gallery/gallery3-packaging/blob/master/ReleaseChecklist As well as adding more queries in the support forums. like "what is a patch" and "how do I make it work"..... I guess one could make a diff of each version as you apply the upgrades and post them in the news story for the benefit of others. I use http://winmerge.org/ to track what I change/merge and it works in my work flow. Each admin has his/her own flow that a diff might not fit into. Dave _____________________________________________ Blog & G2 \|\| floridave - Gallery Team

if 3.0.7 is the last of the 3.0?

XUser login