Any chance we could get a 6.x-dev release? I put off trying this for a good couple of months because of the lack of an official release. I finally did a CVS checkout a few weeks ago, expecting to find it fairly broken, and haven't had a problem with it - at least on one small hobby site and only using it with Drupal OpenID clients so far. I don't see any harm in getting a few more eyeballs on it, at least with the usual "not for production use" caveats.
Comments
Comment #1
Cwolly commentedAgreed. I've been using it for several months with very little issue.
Comment #2
Chris Johnson commentedYup. We could really use a dev release, James. We will give it a lot of testing, as our biggest customer uses it quite extensively in D4.7, and we are migrating to D6 this fall.
Comment #3
Jax@drupal.org commentedDid someone tried to contact walkah directly? Usually it takes a couple of weeks before he responds. Maybe someone should volunteer as a co-maintainer?
Comment #4
christefano commentedI nominate you, Jax! It's possible that someone in the thread at http://groups.drupal.org/node/9742 contacted walkah but I think it's safe to say that nobody did. To that end, I just contacted him about this thread via his website.
Comment #5
IngusNeilands commentedAny progress with OpenID_Provider 6.x-dev release?
Comment #6
christefano commented@IngusNeilands: I'm not aware of any new progress... I don't think nagging usually helps but you might want to try contacting walkah anyway.
Comment #7
Chris Johnson commentedI actually chatted with James (walkah) in IM about it and he said he would do it. Also pinged him via Twitter a bit later. I suspect he is just busy with life, like most people. The squeaky wheel gets the grease. Don't give up yet.
Comment #8
christefano commentedThanks for the update, Chris Johnson!
Comment #9
walkah commentedThanks for the patience, the pings and the interest everyone... DRUPAL-6--1 branched, release node created... tarballs should be generated within 12 hours!
Keep the bug reports coming. :)
Comment #10
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.