Well, it's a small module that will probably not evolve much. A 7.x-1.x-dev release is not really useful. If the bug persists in a couple of days, i'll simply commit some small adjustment and add a 7.x-1.x-beta2 tag.
Rodolfo -- Gaspaio On Sunday, October 2, 2011 at 6:03 AM, Randy Fay wrote: > Why don't you create a 7.x-1.x release and see if it changes anything. I > didn't think that was a prerequisite, but it could be. Right now, drupal.org > (http://drupal.org) doesn't know about your 7.x work. > > -Randy > > On Sat, Oct 1, 2011 at 2:58 AM, Gaspaio <[email protected] > (mailto:[email protected])> wrote: > > Hi again, > > Actually, the tag is 7.x-1.0-beta1. The commit in question can be seen here > > : http://drupalcode.org/project/token_custom.git/commit/e4308d2 > > Any ideas ? > > > > Rodolfo > > > > -- > > Gaspaio > > > > On Saturday, October 1, 2011 at 10:54 AM, Gaspaio wrote: > > > > > Hi everybody, > > > > > > I have a strange problem ; i just tagged a commit with a release tag > > > (7.x-.1.x-beta1) in a project i'm co-maintaining and the tag doesn't show > > > up in the "create new release" select list. What can i do ? > > > The tag seems correct … > > > > > > I initially had made a mistake and wrote the tag as 7.x-1.x-Beta1, which > > > is not correct. I then deleted the tag from the git repo and re-tagged > > > using the correct syntax. But it still doesn't show. > > > > > > Any ideas ? > > > > > > Thanks. > > > > > > Rodolfo > > > > > > -- > > > Gaspaio > > > > > > > > > -- > Randy Fay > Drupal Module and Site Development > [email protected] (mailto:[email protected]) > +1 970.462.7450 >
