It appears to me that an official release of a 7.x-2.0 version of charts 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 some (mostly still open) issues. And this starting from the current 7.x-2.0-rc1 version, with a date that is not before the release date of that version.
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 7.x-2.0 version of charts. Issues for with some type of patch seems to have been applied already to the 7.x-2.0-rc1 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 charts users and/or other maintainers as it relates to making decisions about what to yes or no consider for inclusion in such release.
After such 7.x-2.0 release becomes available, I think that such (stable) release should become the starting point of a 7.x-3.x version of charts. It appears to me that it makes sense to also create a similar issue Charts 7.x-3.x Release, so that we can use that for issues classified as "not for 7.x-2.0, but let's consider it in the context of 7.x-3.x later on". As usual: feedback and thoughts about this proposal will be appreciated!
See Child Issues (lower right) for a list of current release blockers.
PS: transforming the rc1 version in an official release, might help convincing our friends (+25K sites ...) over at the chart module to swap to charts (right now one could argue "I only want to use official releases" ...)
Comments
Comment #1
Pierre.Vriens commentedComment #2
dqd@Pierre.Vriens #1: Patches from issues, which are fixing major bugs from installable versions at the project page should not be hold back to next release versions, if they don't implement an API change. There are a year old RTBC patches in the issue queue, which should be committed, IMHO.
Comment #3
bluegeek9 commentedThank you for your contributions to this issue. As Drupal 7 has reached its End of Life and is no longer supported, we are closing this issue. We encourage you to upgrade to a supported version of Drupal.