Closed (fixed)
Project:
Auto Assign Role
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
13 Apr 2011 at 14:15 UTC
Updated:
6 Nov 2015 at 19:34 UTC
Jump to comment: Most recent
Seems it functions, at least for what I used. Do a bit of double checking and release?
Comments
Comment #1
rogical commented+1
Comment #2
Shadlington commentedSubbing
Comment #3
damienmckennaMost of the issues for the 7.x-1.x branch need to be resolved before this can be marked 7.x-1.0, there are lots of simple issues so that almost anyone could lend a hand to speed up the development.
Comment #4
damienmckennaI've just released 7.x-1.0-beta1, give it a little while to be built.
Comment #5
mgiffordThanks @DamienMcKenna. It's been almost a year now though. We need to see a 1.0 release.
More importantly though, what can be done to help address this call to Seeking co-maintainer(s)?
It's amazing how invisible it is on the project page. There should be something to really encourage users (on the project page and the issue queues) to take the next step and volunteer to help.
Comment #6
damienmckennaI haven't had time to work on this, and I don't have any projects that need it anymore. I've added an extra note at the top of the project page explaining the need for fresh blood to help push the module forwards.
Comment #7
mgiffordThanks @DamienMcKenna - this is a pretty normal flow for Drupal modules I think. Particularly for a heavy contributor like yourself.
I do think there should be an easier way to put in these kinds of requests automatically:
Note there is a missing 'k' that I added in the string.
Maybe messages like this #2193871: Create an Action Block for Short Messages for Users & Visitors
If a module is seeking co-maintainer, that should be widely advertised in the issue queue for that project. It's easy to miss where it is right now.
Comment #8
mike.davis commentedHi, I'm helping to maintain this module now so hopefully we will be able to get some movement towards a stable release for 1.0 out soon.
I have been reviewing the main outstanding issues and there are several patches ready for review so if people can review them we can at least see if we can get another beta release out soon as a good step towards getting a first release candidate.
Comment #9
mike.davis commentedOK, one last issue left before we can think about moving to a 7.x-1.0 release - #971434: User creates account from the web and is assigned roles by path.
Can anyone offer any suggestions on the query I have with it?
Comment #10
mike.davis commentedI haven't heard anything further on #971434: User creates account from the web and is assigned roles by path, so it may be worth moving it to a future release branch if I don't hear anything within the next month or so, as this is currently blocking moving this release forward.
With one bug left to sort out I think we could be close to getting a rc1 release.
Comment #11
mike.davis commentedThere hasn't been any more bug reported for the 7.x-1.x release for several months now and this last user story (#971434: User creates account from the web and is assigned roles by path) hasn't had any response so I have bumped it to 7.x-2.x.
We have a 7.x-1.0-rc1 release now, but with nothing much left in the issue queue currently I am happy to say that we have a stable 7.x-1.x release - just about made it before 8.x-1.0 is released! :)
The next release will be an official 7.x-1.0 release, but with nothing to current commit it doesn't seem worth while just creating a release for the sake of it, so I will close this task.