On 06/09/14 16:28, Thomas Mulhall wrote:
What I mean is for the extension to add there own release date so that when they release an updated version like for example 1.0 updated to 1.0.1 or 1.1 and the user goes to the extension and page and sees there is an updated version with an updated release date because some times versions will only be bumped if it is major or if it is worth bumping it. so it would be useful for the users to know when it was last updated. because some hosting companys doint allow you to use ssh to download from git so you have to do it manually.
That's not really feasible. As it is, extensions developers often forget to bump the version number (I think I've only actually remembered once), and that's if there even is one. Should we need to update an entire date, that seems particularly unlikely to reliably happen since dates are even more complicated than version numbers. (Although some like Interwiki actually include the date in the version number, or at least did at one point.)
A automatic date referring to when the last change was merged to the branch the tarball was made from, however, would indeed be useful for the tarballs (and likely relatively reliable), because that will tell you how old it is and give an idea if something should probably be updated. Because otherwise it can be very hard to tell.
You don't really have that problem with git because you generally just update everything in one go there, or even automatically.
-I