Posted by hsvmda on November 4, 2012 at 2:32pm
5 followers
Jump to:
| Project: | GMap Module |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
I just looked at the status report this morning for my site, and I saw this error message:
GMap Module 6.x-1.1 ---- Not supported!
Project not supported: This project is no longer supported, and is no longer available for download. Disabling everything included by this project is strongly recommended!
Includes: GMap, GMap Location, GMap Macro Builder
Is this true? If so, are there any substitutes for these modules?
Comments
#1
maintenance fixes only
no feature additions
#2
status
#3
@podarok, I also think that the status of 6.x-1.x-dev as not supported is NOT in keeping with maintenance fixes only and no feature additions. There are many drupal projects that are in the same situation and still can be used.
Furthermore, the status sends the wrong message telling people they should remove the module and the comments suggest the 6.x-1.1 release is okay but the 6.x-1.x-dev release is not. This ignores the work that has gone into 28 commits, some of which are critical to specific features and 2,288 sites are using it.
Please review this and restore the status of the 6.x-1.x-dev branch so it does not have such an alarming status.
Thanks.
#4
Please restore a supported download for this module.
There are 20K sites reporting usage of Gmap 6.x - removing the supported release for 6.x will trigger security warnings for all of them, which does not sound like what you intended from your comment in #1.
#5
Looks like you've now restored the downloads of 6.x-1.1 and 6.x-1.x-dev - thanks for doing so.
#6
Thanks for your quick reply on this. My site is now reporting everything is up-to-date. I had to run update.php and re-run the cron task in order to clear the "Not supported!" status.
#7
keep in mind that support for the 6.x version limited only with bug fixes from issue queue
all new features will be created against 7.x and upcoming 8.x releases and only after that possibly can be implemented for 6.x
#8
That's fine. Just don't make me go looking again for some module-devouring security advisory I missed ;)
Thanks for your work on maintaining. It does sound from @izmeez's #3 that a 6.x-1.2 release might be useful to those still on 6.x?
#9
6.x release supported with only user posted patches or backported patches for 7.x
latest fixes always lying in 6.x-1.x-dev - this branch used for consolidation all RTBC patches and feature request but the way is - provide patch for 7.x and after RTBC backport it to 6.x
#10
We understand that fixes go into 7.x first, yes. I (and possibly izmeez) were simply suggesting a 6.x-1.2 release, which I see you've kicked off with a 6.x-1.2-alpha1. Thanks for that.
I created #1832936: Release co-ordination for Gmap 6.x-1.2 and collated the fixes which are available in 6.x-1.2 - hope this helps with the release notes. 6.x-1.2-alpha1 is not yet visible on the module homepage.
Thanks again!
#11
#10 added #1832936: Release co-ordination for Gmap 6.x-1.2 to project page
#12
@podarok, thank you.
#13
Automatically closed -- issue fixed for 2 weeks with no activity.