Plan for Views 7.x-3.15 release

+1 to the initiative!!

Added a few proposals.

Sad a release was rolled without maintainers even commenting on child issues.

Sadly a release was fixed which fixed a critical regression. Maybe doing that is a bad idea ;)

Fair enough, I read the "release notes" and didn't see an indication of a critical must fix immediately regression, so I hope you can excuse my ignorance.

Are you referring to #2450447: Drupal QA is broken for Views 7.x-3.x?

We had a release in the meantime. Do you think we have to keep this issue open?

@dawehner:
Thanks for replying, you didn't really answer my question, but I shall endeavour to answer yours regardless.

Do you think we have to keep this issue open?

Well I'm not the module maintainer, so it's not really up to me, however I would note that it's quite common practice amongst popular contrib modules to have a plan for what bug fixes and new features will be incorporated into which release, this way everyone can stay apprised of what's going on.

So I wouldn't say this issue has to be kept open, only that it's of great use to those of us that like to track release progress, especially when a module has so many open issues as this one does.

@dawehner: can you commit the fixes to the current totally broken 3.14 and make a new working 3.15 release, please?

Well I'm not the module maintainer, so it's not really up to me, however I would note that it's quite common practice amongst popular contrib modules to have a plan for what bug fixes and new features will be incorporated into which release, this way everyone can stay apprised of what's going on.

Well, if anyone would plan anything sure :)

Sadly a release was fixed which fixed a critical regression. Maybe doing that is a bad idea ;)
Are you referring to #2450447: Drupal QA is broken for Views 7.x-3.x?

I don't remember anymore to be honest :(

Drupal 7.50 causes a new test fail in Views, which has been fixed in #2761829: Getting drupal_trigger_error_with_delayed_logging errors on Drupal 7.x dev (7.50) , so it would certainly be good to tag a new release so as to not have failing tests in modules with tests that depend on Views.

@stefan.r: True. There are a few other RTBC issues too, if someone's thinking of getting a new release out the door..

I would be happy to have time to look at them. In general I think we should try to be a little bit conservative, especially when we can't promise some form of responsiveness after the commit :)

@DamienMcKenna
Want to have another module? :)

I would be happy to have time to look at them.

Thanks @dawehner.
There are couple of regression #2750453: Delta value 1 not handled and #1090432: Allow additional field-to-field conditions with the default views_join handler introduced after 3.14 release which need immediate attention. I'm not at all pressuring you. It is just that 3.14 is a security release and all the D7 site will be vulnerable until those regressions will be fixed.

Is the plan more to rollback #1090432: Allow additional field-to-field conditions with the default views_join handler or go with #2750453: Delta value 1 not handled. It is not clear if it fixes all issues introduced.

Will appreciate if this #2750021: View Styles Plugin - row CSS class name is forced to lowercase issue is also included in 3.15 release.

Is there any scheduled date for next release?

Thanks

How come RTBC's haven't got included in 3.15 release?

If #1090432: Allow additional field-to-field conditions with the default views_join handler is not solved we stick all at v3.13... looks like there are wrong priorites for about 9 months as people cannot upgrade to latest security releases without destroying all their websites.