Why does this module have such frequent official releases?
| Project: | Tracker 2 |
| Version: | 5.x-1.13 |
| Component: | Miscellaneous |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
I am posting this as a result of a discussion on the development list (http://lists.drupal.org/pipermail/development/2008-May/029947.html and thereafter), because I noticed that this module seems to be creating new official releases very frequently, sometimes after every CVS commit.
This is not meant to be accusatory or to single this module out (I am posting similar messages at other modules too)! Rather, it's part of an informal "survey" to gather some information to help figure out why module maintainers are doing this and whether there are any structural issues related to Drupal's release management system involved in the decision to do so.
So my basic question is this: Are you aware that the recommended practice is to only release new official versions (as opposed to auto-generated development snapshots) somewhat infrequently, usually after a number of bugfixes in the issue queue have been accumulated (with the exception being security issues and extremely critical bug fixes)? And is there a particular reason that you seem to have followed a different policy for this module?
Thanks very much for your time!
#1
The initial stream of releases was before anyone was using the module for non-testing purposes. It was simply a convenient way to post new packages for testing. Development snapshots were too slow. Because most complaints about frequent releases relate to annoying Update module notifications -- and this issue wasn't a concern with no one having the module installed -- I didn't think it would be a problem.
The other reason for frequent releases was the maddening pace at which this module was developed. It went from a few thoughts to running on Drupal.org in only a week or two.
New releases are now relatively infrequent.
#2
Cool, thanks. Yeah, it sounds like this module was definitely a unique situation! The idea that dev snapshots are too slow is not something I would have thought of, but I guess that's true; if you need people to test new code more than twice a day, then you might need something faster (if they don't have CVS). Interesting. So far, this particular issue hasn't come up with any of the other module maintainers I've surveyed, but it's worth keeping in mind... Thanks again!
#3
Automatically closed -- issue fixed for two weeks with no activity.