We should release at least one stable 2.x release (there has never been one) before completely abandoning 7.x-2.x development.

Problem/Motivation

Since 2014 (2.x beta 11) there hasn't been any release based on OpenLayers 2. In the meantime OL has moved on to v3 and the development on this module's 2.x branch seems to have halted. Many users are stuck on OL 2 and 7.x for the foreseeable future. And usage statistics show that 2.x still greatly outnumbers 3.x usage. So lets not leave this user base behind and release 7.x-2.0 and leave it at that. We can than entice users to make the switch to 8.x-3.x or 7.x-3.x and focus on helping them upgrade rather than stemming the flow of 2.x issues still trickling in. There are currently about 400 open 7.x issues 60 of which are 3.x. That means there are over 300 open issues on the various 7.x-2.x releases.

Proposed resolution

Key goals:

  1. Release a final stable 7.x-2.0.
  2. Mark that as a supported release and document it as stable but no further development.
  3. Clean up the issue queue regarding all 2.x issues.
  4. Create a clear vantage point for users to upgrade or migrate to OL 3.

Remaining tasks

  • Create an issue tag for the stable 2.0 release 7.x-2.0 blocker
  • Tag all essential 2.x issues regarding major bugs and security problems
  • Remove all support / feature requests in the 2.x line or move them to 3.x
  • Make a summary list here of all essential issues.
  • Provide documentation on how to migrate / upgrade to 8.x without breaking your current installation

Comments

basvredeling created an issue. See original summary.

basvredeling’s picture

basvredeling
Primary language Dutch
Location Amsterdam
CreditAttribution: basvredeling at Code Culture commented
Issue summary: View changes
Pol’s picture

Pol
the/that
Location Brussels
CreditAttribution: Pol commented

Hi @Bas,

I let you take care of this good initiative. It's good to see people care about it!

basvredeling’s picture

basvredeling
Primary language Dutch
Location Amsterdam
CreditAttribution: basvredeling at Code Culture commented
Assigned: Unassigned » basvredeling
Issue summary: View changes

Assigned to myself.
Added issue queue summary.

basvredeling’s picture

basvredeling
Primary language Dutch
Location Amsterdam
CreditAttribution: basvredeling at Code Culture commented
Issue summary: View changes

Added tag 7.x-2.0 blocker as suggested tag.

basvredeling’s picture

basvredeling
Primary language Dutch
Location Amsterdam
CreditAttribution: basvredeling at Code Culture commented
Issue summary: View changes

typo

basvredeling’s picture

basvredeling
Primary language Dutch
Location Amsterdam
CreditAttribution: basvredeling at Code Culture commented
Issue summary: View changes

Issues tagged with 7.x-2.0 blocker will be part of the 2.0 release if at all possible.
I will select these issues from all 7.x-2.x branches (including -betaX branches) based on:

  • Priority (is it critical or major?)
  • Age and relevance (has anyone responded in recent months / years?)
  • Wether a patch has been provided (is it tested or ready for testing?)
  • Topic (is it security related? will it make 2.x more stable?)

I will move all feature requests to 7.x-3.x or 8.x-3.x for reevaluation.
I will close all support requests that have been answered and where discussion has subsided.

ressa’s picture

ressa CreditAttribution: ressa at Ardea commented

Great initiative @basvredeling. Perhaps someone with coding skills could review the 7.x-2.0 blocker patches?