It appears to me that a 6.x-2.x version of chart is appropriate, in which an attempt should be made to include any patch-like stuff (or other contributions) that seems to be hanging around (mostly as attachments), in various (mostly still open) issues. And this starting from the current 6.x-1.x-dev version, with a date that is not before the release date of the most recent recommended 6.x-release.

Assuming that this suggestion is acceptable (and not conflicting with any other similar efforts that I'm not aware of yet), I propose to use this issue as the parent issue to track progress towards the release of a 6.x-2.x version of chart. Issues for which some type of patch seems to have been applied already to the 6.x-1.dev branch will be updated with this issue as their parent issue (issue status might be closed already, needs review, etc). To mark an issue for being considered for inclusion in this release, select this issue as the parent issue in such issue. Using such parent links seems to be the easiest way to get the data entry done also. Moreover, it'll automatically also make it clear what in the end the release blockers might be (ie any issues with a status different from fixed or closed).

As a (recent) co-maintainer, I hope to get some type of support/backing from chart users and/or other maintainers as it relates to making decisions about what to yes or no consider for inclusion in such release.

See Child Issues (lower right) for a list of current release blockers.

Comments

Pierre.Vriens’s picture

Pierre.Vriens commented
Issue summary: View changes
Pierre.Vriens’s picture

Pierre.Vriens commented

Comment #17 in issue #2368793: Chart 2.0 contains the following (from Brad, @eosrei):

I don't intend to spend any time on any 6.x code again. D6 is already deprecated and will be unsupported the day D8 is released; which will hopefully be before April.

Hope I'm allowed to say so, but I've a slightly different opinion regarding support for D6 in current chart:

  1. Checkout the weekly usage statistics of charts: over 20% (more then 5K sites ...) of the about 26K sites still using chart today are still in D6 ...
  2. The day that D8 is released will not be the day that D8 is mature enough to have D6 sites (or D7 sites) move to D8, either because of missing contrib modules that aren't ported to D8 yet, or simply because of things like budget constraints. Moreover I'm not convinced that the release of D8 will still be in 2015. Moreover, after D8 becomes available, there will still be some time that D6 will continue to be supported.
  3. Even if we'd go for some type of "merger" with the charts module, that wouldn't really be an attractive route (business case) for these D6 sites, since the current status of the charts module is "no more support for D6", as illustrated in various charts issues related to D6 that have status closed (won't fix), for which many of them include a comment like "The D6 version of the module is no longer being updated. If this problem exists in the 7.x-2.x branch of the module please reopen".
  4. Quite a few of "our" Drupal customers are still on D6. They'd like to go ahead with D7 and all its enhancements as compared to D6, but budget limitations typically make them stick with D6.

Therefor I think we've to come up with some type of upgrade for these D6 sites, at least to try to address most of the child issues of this issue. Therefor please consider giving me commit access also to the 6.x branch of the chart module, thereby taking the (no longer existing) maintenance of that branch over from Brad, who indicated that he doesn't intend to spend more time on D6? Of course this doesn't resolve the known April 2015 deadline, but a new (and last) stable D6 release would be a good starting point for some type of migration to whatever comes out of Chart 2.0.

13rac1’s picture

13rac1 commented

It's still weirding me out that you refer to me by my actual name on drupal.org. Haha

If boomatower gave you commit access to the project, you already have access to commit to the 6.x-1.x branch. You can probably commit these RTBC patches without much review.

Moreover, after D8 becomes available, there will still be some time that D6 will continue to be supported.

D6 will be supported for three months after D8's release:
Drupal 6 core and modules will transition to unsupported status three months after Drupal 8 is released.
src: Drupal 6 extended support announcement https://www.drupal.org/node/2288521
There's a whole discussion about it here: Drupal 6 end of life when Drupal 8 is released… or not? https://groups.drupal.org/node/291243

D8 is in Beta3 with only 100 criticals remaining. I really hope you are wrong about a D8 not being released in 2015! Haha! It's so close! :)

Thanks for your efforts!

Pierre.Vriens’s picture

Pierre.Vriens commented
Title: Chart 6.x-1.4 Release » Chart 6.x-2.x Release
Issue summary: View changes

Per #25 in #2368793: Chart 2.0 I'm updating the release ID here (with related changes in the issue summary). Changes to the links of related issues may follow later on, depending what gets added or remove to this release ID.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Status: Active » Closed (outdated)

I am closing this issue, as Drupal 6 is no longer supported.