"Development snapshot" tarball is stale

Over a year, no activity, presume thread is dead. Re-open if not.

Re-opening. Yes, you are right, the 5.x development snapshot is dated 25th Feb 2008 whereas the official 5.x-1.3 release is dated 27th March 2008. This will be addressed as soon as we get the maintainership sorted out.

Voxpelli, now that you have maintainership, do you know do we go about resolving this?

I'm not very good at CVS - as I see it this might be caused by two things: Either the dev release has been switched of, if so it will be solved by me switching it on now, or it's caused by changes being pushed to the wrong branch. If it's the wrong branch then I don't exactly now how to solve it.

Also - if there are changes for 5.x that hasn't been released yet - then maybe we should do one final release of it? I'm then thinking of no longer actively supporting 5.x - only fixing any critical issue that might pop up.

I just noticed that the D5 development snapshot is now dated 11th July 2010. Downloaded both and compared all files, and the .module and .install files are identical to the 1.3 release. However, the dev snapshot does not contain the .info file but instead contains a .mysql file.

Any ideas why there should be a difference in the files that are included? Does it matter? and can we close this issue?

Also I noticed that the 6.x-1.x dev release now says 11th July, but nothing has been changed. I've compared all files with the previous release of 21st Feb and they are identical (except for the timestamp in .info of course)

Something must have triggered a new release without any changes being committed. I don't know if anything went wrong with CVS on that day, because the Pingback module http://drupal.org/node/187800/release also had a new dev release dated 11th July but no code was changed in any file.

I believe there has been an issue were almost all dev-builds on Drupal.org has been recreated with a newer date. So nothing has really changed for Multiping.

Since the dev-build for Drupal 5 is wrong - maybe we should remove it?

Yes, given that the .module and .install are identical to 1.3 I think we (you) can remove the D5 dev version then we can close this issue.

Done