Issue status update for http://drupal.org/node/20439 Project: Drupal Version: cvs Component: other Category: feature requests Priority: normal Assigned to: Chris Johnson Reported by: Chris Johnson Updated by: mathias Status: patch This make a lot sense. +1 Let's also output the release tag name somewhere in the Drupal admin section. Maybe on admin/settings? mathias Previous comments: ------------------------------------------------------------------------ April 13, 2005 - 10:31 : Chris Johnson Attachment: http://drupal.org/files/issues/releasename_core.patch (32.8 KB) There's no easy way for a site administrator to tell which version of Drupal software his site is running. This is particularly a problem when an administrator manages multiple sites at multiple hosts. The problem becomes even more exacerbated when the same admin only has limited time to update the software on sites, resulting in confusion as to just what version is running where. While there are a lot of technical solutions to this problem, some of which I'd like to implement, this patch is the simplest and least invasive. It simply adds the CVS release tag name to each file which can take such a tag. An admin can thus look in any file and see which release it is. This patch is for the core files. A similar one will be added to a separate issue for contrib files.

Issue status update for http://drupal.org/node/20439 Project: Drupal Version: cvs Component: other Category: feature requests Priority: normal Assigned to: Chris Johnson Reported by: Chris Johnson Updated by: kbahey Status: patch +1 for this patch. It does not solve everything, but is sorely needed. Dries, I think this should go in 4.6 before its release too. As for the visibility to the admin, I suggest that each module would have a version attached to it. This version can be the Build Tag/Name, and a date where the tar ball was packaged. Under admin -> modules, each module has this info listed next to it. Adding the date avoids the problem of retagging in contrib, updates to an existing branch, ...etc. which were discussed in an earlier thread. If we extend this to the scheme files, it would be easier to track changes needed to the database from one release to the next too. kbahey Previous comments: ------------------------------------------------------------------------ April 13, 2005 - 11:31 : Chris Johnson Attachment: http://drupal.org/files/issues/releasename_core.patch (32.8 KB) There's no easy way for a site administrator to tell which version of Drupal software his site is running. This is particularly a problem when an administrator manages multiple sites at multiple hosts. The problem becomes even more exacerbated when the same admin only has limited time to update the software on sites, resulting in confusion as to just what version is running where. While there are a lot of technical solutions to this problem, some of which I'd like to implement, this patch is the simplest and least invasive. It simply adds the CVS release tag name to each file which can take such a tag. An admin can thus look in any file and see which release it is. This patch is for the core files. A similar one will be added to a separate issue for contrib files. ------------------------------------------------------------------------ April 13, 2005 - 11:40 : mathias This make a lot sense. +1 Let's also output the release tag name somewhere in the Drupal admin section. Maybe on admin/settings? ------------------------------------------------------------------------ April 13, 2005 - 13:03 : Chris Johnson Yes, I'd like to add some panel to admin that would show the admin which version of the software he was running, as well as which version of the database (update number) he was running. There might be a few other bits that could be added to such a display that would make life so much easier for the harried admin trying to manage many sites and projects. I'm willing to code it. Just need to get a little buy-in and agreement on features from those who decide what goes in core.

Issue status update for http://drupal.org/node/20439 Project: Drupal Version: cvs Component: other Category: feature requests Priority: normal Assigned to: Chris Johnson Reported by: Chris Johnson Updated by: Uwe Hermann Status: patch +1 Uwe Hermann Previous comments: ------------------------------------------------------------------------ April 13, 2005 - 18:31 : Chris Johnson Attachment: http://drupal.org/files/issues/releasename_core.patch (32.8 KB) There's no easy way for a site administrator to tell which version of Drupal software his site is running. This is particularly a problem when an administrator manages multiple sites at multiple hosts. The problem becomes even more exacerbated when the same admin only has limited time to update the software on sites, resulting in confusion as to just what version is running where. While there are a lot of technical solutions to this problem, some of which I'd like to implement, this patch is the simplest and least invasive. It simply adds the CVS release tag name to each file which can take such a tag. An admin can thus look in any file and see which release it is. This patch is for the core files. A similar one will be added to a separate issue for contrib files. ------------------------------------------------------------------------ April 13, 2005 - 18:40 : mathias This make a lot sense. +1 Let's also output the release tag name somewhere in the Drupal admin section. Maybe on admin/settings? ------------------------------------------------------------------------ April 13, 2005 - 20:03 : Chris Johnson Yes, I'd like to add some panel to admin that would show the admin which version of the software he was running, as well as which version of the database (update number) he was running. There might be a few other bits that could be added to such a display that would make life so much easier for the harried admin trying to manage many sites and projects. I'm willing to code it. Just need to get a little buy-in and agreement on features from those who decide what goes in core. ------------------------------------------------------------------------ April 13, 2005 - 20:11 : kbahey +1 for this patch. It does not solve everything, but is sorely needed. Dries, I think this should go in 4.6 before its release too. As for the visibility to the admin, I suggest that each module would have a version attached to it. This version can be the Build Tag/Name, and a date where the tar ball was packaged. Under admin -> modules, each module has this info listed next to it. Adding the date avoids the problem of retagging in contrib, updates to an existing branch, ...etc. which were discussed in an earlier thread. If we extend this to the scheme files, it would be easier to track changes needed to the database from one release to the next too. ------------------------------------------------------------------------ April 13, 2005 - 20:56 : chx biiiig +1

Issue status update for http://drupal.org/node/20439 Post a follow up: http://drupal.org/project/comments/add/20439 Project: Drupal Version: cvs Component: other Category: feature requests -Priority: normal +Priority: critical Assigned to: Uwe Hermann Reported by: Chris Johnson Updated by: Cvbge Status: patch (ready to be committed) +1 on idea. Critical because many people ask on -support how to check what release they are running... Cvbge Previous comments: ------------------------------------------------------------------------ Wed, 13 Apr 2005 16:31:37 +0000 : Chris Johnson Attachment: http://drupal.org/files/issues/releasename_core.patch (32.8 KB) There's no easy way for a site administrator to tell which version of Drupal software his site is running. This is particularly a problem when an administrator manages multiple sites at multiple hosts. The problem becomes even more exacerbated when the same admin only has limited time to update the software on sites, resulting in confusion as to just what version is running where. While there are a lot of technical solutions to this problem, some of which I'd like to implement, this patch is the simplest and least invasive. It simply adds the CVS release tag name to each file which can take such a tag. An admin can thus look in any file and see which release it is. This patch is for the core files. A similar one will be added to a separate issue for contrib files. ------------------------------------------------------------------------ Wed, 13 Apr 2005 16:40:52 +0000 : mathias This make a lot sense. +1 Let's also output the release tag name somewhere in the Drupal admin section. Maybe on admin/settings? ------------------------------------------------------------------------ Wed, 13 Apr 2005 18:03:40 +0000 : Chris Johnson Yes, I'd like to add some panel to admin that would show the admin which version of the software he was running, as well as which version of the database (update number) he was running. There might be a few other bits that could be added to such a display that would make life so much easier for the harried admin trying to manage many sites and projects. I'm willing to code it. Just need to get a little buy-in and agreement on features from those who decide what goes in core. ------------------------------------------------------------------------ Wed, 13 Apr 2005 18:11:10 +0000 : kbahey +1 for this patch. It does not solve everything, but is sorely needed. Dries, I think this should go in 4.6 before its release too. As for the visibility to the admin, I suggest that each module would have a version attached to it. This version can be the Build Tag/Name, and a date where the tar ball was packaged. Under admin -> modules, each module has this info listed next to it. Adding the date avoids the problem of retagging in contrib, updates to an existing branch, ...etc. which were discussed in an earlier thread. If we extend this to the scheme files, it would be easier to track changes needed to the database from one release to the next too. ------------------------------------------------------------------------ Wed, 13 Apr 2005 18:56:10 +0000 : chx biiiig +1 ------------------------------------------------------------------------ Wed, 13 Apr 2005 19:27:59 +0000 : Uwe Hermann +1 ------------------------------------------------------------------------ Sat, 27 Aug 2005 23:50:06 +0000 : Uwe Hermann Attachment: http://drupal.org/files/issues/cvs_name.patch (34.76 KB) Lets revive this. I still think it's a good idea. Patch attached.