Identify what would be necessary for a views-6.x-2.27 release to follow the current views-6.x-2.26 for use with Drupal 6 LTS core that is php 7.2 compatible.

The issue that is similar but relates to views-6.x-3.x is #2507839: Plan for Views v6.x-3.10 release. It too is outdated.

Please add this issue as the parent (or "related") for any issues that should be included in the next release, please help to review existing patches and fix others that need work. Please keep in mind that issues for 6.x-2.x may also affect 6.x-3.x so please reference them there too. Thank you.

Comments

DamienMcKenna’s picture

Issue summary: View changes
dawehner’s picture

To be clear for 2.x I would like to avoid any kind of changes, if possible, everything else is just too old software.

DamienMcKenna’s picture

@dawehner: That's cool, there are enough bugs in 2.x to make a bugfix release completely worthwhile.

dawehner’s picture

Yeah no question ... on the other hand I realized that you burn a non trivial amount of money, if people update some module for a release, just time wise.

DamienMcKenna’s picture

Issue tags: +PHP 5.4
roball’s picture

After committing 3abf14a0e609b975441b29072af0e2891ea918e4, is it worth to release Views 6.x-2.19?

izmeez’s picture

Title: Plan for Views v6.x-2.19 release » Plan for Views v6.x-2.27 release
Version: 6.x-3.x-dev » 6.x-2.x-dev
Issue summary: View changes
Issue tags: +D6LTS

I have just completed a review of a number of patches in the issue queue and would like to update the candidates for the next views-6.x-2.x release. I hope this helps the maintainers.

DamienMcKenna’s picture

Status: Active » Closed (won't fix)

The Drupal 6 branch is no longer supported, please check with the D6LTS project if you need further support.