[drupal-devel] Re: CVS question: Multiple branch tags on a module
I wrote:
However, the 4.5 branch still doesn't appear as the "latest release" when I go to the project page:
http://drupal.org/project/interwiki
If people click on the "download latest release," they still get an old version of the module rather than the current version. What can I do to fix this?
And Jim Riggs replied:
It looks like you just committed changes over an hour ago. There is a script that runs on the server that packages the tar.gz files every 6 hours (I think). Wait a few hours and check it again. It will get updated.
OK, I waited and Jim was right. The tar.gz file now reflects my commit. The only thing now is that the project page still lists December 31, 2004 as the "latest release" date. This is a minor detail, of course. My main concern was making a current version available for download, and that's now accomplied. However, is there any way to get the latest release date changed on the project page? --Sheldon Rampton
It looks like you just committed changes over an hour ago. There is a script that runs on the server that packages the tar.gz files every 6 hours (I think). Wait a few hours and check it again. It will get updated.
OK, I waited and Jim was right. The tar.gz file now reflects my commit. The only thing now is that the project page still lists December 31, 2004 as the "latest release" date. This is a minor detail, of course. My main concern was making a current version available for download, and that's now accomplied. However, is there any way to get the latest release date changed on the project page?
As I mentioned in one of my earlier e-mails, that date is populated by the project module when a version is first encountered. It does not change. So, that is the date that the project module first encountered the 4.5 version of your module. The only way to change it would be to modify the DB directly. Also as I said before, this may not be the best system, but that is how it currently works.
On Thursday 14 April 2005 08:27, Jim Riggs wrote:
As I mentioned in one of my earlier e-mails, that date is populated by the project module when a version is first encountered. It does not change. So, that is the date that the project module first encountered the 4.5 version of your module. The only way to change it would be to modify the DB directly. Also as I said before, this may not be the best system, but that is how it currently works.
Thanks for explaining this. I had wondered about that behavior; it's confusing to see the date not change on drupal.org. Scott -- ------------------------------------------------------------------------------- Scott Courtney Drupal user name: "syscrusher" http://drupal.org/user/9184 scott@4th.com Drupal projects: http://drupal.org/project/user/9184 Sandbox: http://cvs.drupal.org/viewcvs/drupal/contributions/sandbox/syscrusher
participants (3)
-
Jim Riggs -
Sheldon Rampton -
Syscrusher