TNGIntegrate module not publishing releases [#121961]

I published two releases for the TNGIntegrate module on the night of Feb. 21/22 and as of this morning they are still not appearing as published releases, i.e. they are showing up pink in my view and not at all in anonymous users' view.

I imagine the packaging scripts have run since my release of these scripts. Are they encountering some kind of error that is keeping the scripts from being packaged and published?

Comments

Comment #1

merlinofchaos commented 23 February 2007 at 17:15

I'm not sure why or how, but somehow those releases have been set 'unpublished'. It may be that dev releases aren't set published until their tarball is created.

I've gone ahead and set them published, which should get their tarballs picked up in the next packaging run, which I think will be in 45 minutes.

Leaving this open to check on it; it's entirely possible something else is wrong so I'm not ready to set this closed until I'm sure the tarballs get picked up.

Comment #2

AjK commented 23 February 2007 at 17:31

Erm, I think you'll find that it's the tarball creation/release that switches the node from unpublished to published. Having them published before the "run" means there's no download file so you'll have broken links.

I'll go take a look now.

Comment #3

AjK commented 23 February 2007 at 17:43

ok, I've reversed that and unpublished them. The correct way to create a release to to first CVS TAG what it is you are releasing. Once the tags are in place in CVS you can then create an "official" release. It takes up to 5mins for the release to be made, after which the release node is published.

If you want "dev" releases based on the HEAD of your branches just leave "Display snapshot releases on project page" enabled and that should happen automatically.

So you first need to tag (eg cvs tag DRUPAL-5--1-0) and then create a release on that. For the 4.7 create a tag on the 4.7 branch (cvs tag DRUPAL-4-7--1-0) and then create a release node off that. The packaging script runs every 5mins.

Let us know how you get on (you'll notice I added myself as a co-maintainer in case you need some help, otherwise just remove me, I won't touch your code with talking with you first).

Comment #4

arturoramos commented 23 February 2007 at 18:29

I would like for the dev releases to be published automatically and as such I created two branches: "DRUPAL-4-6" and "DRUPAL-5"

I don't really want to create any official releases at this point, as the module is still in a beta stage so I have not created any tags, e.g. "DRUPAL-4-6--1-0." I have left the "Display snapshot releases on project page" option enabled which makes me think that there should be something published. I can do so if absolutely necessary but I have not done so for my other module "mailman_manager" for which I have three branches with the dev snapshots published.

Should I have first created a "HEAD" branch or tag?

Whatever you can do to get the current releases published is fine by me. I can go back and update the CVS repository later.

Comment #5

dww

we/he/they

commented 7 March 2007 at 19:44

Status:

Active

» Fixed

the releases are published (with tarballs), so this is clearly not a problem any more. probably you were just impatient, and didn't read either the documentation or the message when you created the release nodes that said the packaging script for dev snapshots only happens infrequently.

that said, it'd sure be nice if people closed their own issues when they're resolved... it's a waste of my time to read through infrastructure and webmaster issues for stuff related to project.module, investigate, only to find the issue is already fixed. :( please be more considerate of this case in the future. thanks.