Hi, sorry for being out, now I'm getting back and need to update myself with current changes. From what I've seen ( #654206: Upgrade to 1.7 fails to complete on some installations, and corrupts data and others) looks like upgrade path has already been fixed. Due to this, kiamlaluno, you can slow down the process of new release creation because we bumped from the eternal 1.3 to 1.8 in two weeks.

So here is a proposal: Unless it is a SA (mandatory) or a bug breaking an upgrade path, lets group current issues and make a new release with several fixes.

This is a list of bugs currently active for 1.x (as long as support requests should go to 3.x):
#656828: Users with "administer nodes" can see/edit all meta tag fields even if they have no specific permissions for each meta tag.
#600452: Upgrade path for views and panels
#641722: Use node teaser option not sticking <-- this one is tagged for 3.x, but if it is a bug, should probably appear in 1.x.
#645042: Settings "Other Pages" are not applied <-- probably should be tagged as bug instead of support request.

All this issues fixed could be the point to release 1.9, because having too much active releases may difficult seriously future upgrade paths. (take a look to the bottom of the nodewords usage stats and you'll figure out why..)

Oh, and kiamLaLuno, thanks for all the good work with this. I've to admit, you fix issues faster than I could even read them!

Comments

ilo’s picture

ilo commented
Title: slow down release process » Roadmap to release 1.9

Lets make a better title.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented

I would also add #651898: {nodewords_custom}.path is copied in {nodewords}.id, which is actually a bug present in branch 6.x-1 too.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented

About #641722: Use node teaser option not sticking, I think the report was thought to be for 6.x-1; anyway, the problem is not present on both the branches.
About #645042: Settings "Other Pages" are not applied, I think the problem was reported on a different issue, and it has been already fixed.

ilo’s picture

ilo commented

So there is only one blocker now, good work Kiam!!

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented

About the left issue, I am not sure there is a way to resolve it, considering that the eventual code to resolve it should look for any path associated with each displays of a view. I am not good with Views, but I don't recall there is a way to do it.

ilo’s picture

ilo commented

Perhaps it is a good idea to put a final comment on the OT issue about this one, so people can focus on what would expect to appear in this new release, I don't know if this is possible as long as it is closed for comments.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented

I did close the comments on that issue report as it got a way too out of topic.
I will check if it is possible to get the path associated to a view display from the view ID; if that it is possible, then something can be done.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Status: Active » Fixed

Version 6.x-1.9 has been already released. This task can be marked as fixed.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.