Good morning! I think it's safe to say that most of us tag modules for DRUPAL-4-6 and earlier versions only when they are ready for release, rather than being under early development (though there's probably some fuzziness to that line). My question is, should that policy also hold for DRUPAL-4-7 tagging, given that Drupal itself is still in beta, or are we encouraged to tag modules that are in late beta for 4.7 now to encourage more testing? Thanks for any comments. Scott -- ------------------------------------------------------------------------------- Syscrusher (Scott Courtney) Drupal page: http://drupal.org/user/9184 syscrusher at 4th dot com Home page: http://4th.com/
On 2/3/06, Syscrusher <syscrusher@4th.com> wrote:
I think it's safe to say that most of us tag modules for DRUPAL-4-6 and earlier versions only when they are ready for release, rather than being under early development (though there's probably some fuzziness to that line).
My question is, should that policy also hold for DRUPAL-4-7 tagging, given that Drupal itself is still in beta, or are we encouraged to tag modules that are in late beta for 4.7 now to encourage more testing?
I think that if you're feature- and schema-complete at this point, you're ready to tag. Personally, I'm holding off on tagging freelinking until I'm confident I've got the .install file working well, as that module has changed considerably from 4.6 to what will be 4.7. The big thing that you want to avoid, imo, is introducing new features and/or schema updates after a tag. I believe that, once tagged, only bug fixes should go in. If you're there, and confident enough in the upgrade routine, go for it, says I. -- e www.eafarris.com
The big thing that you want to avoid, imo, is introducing new features and/or schema updates after a tag. I believe that, once tagged, only bug fixes should go in. If you're there, and confident enough in the upgrade routine, go for it, says I.
-- e www.eafarris.com
That raises a question for me, though -- what happens if I want to release a major new version of my module in three months, after 4.7 has shipped? Should I start using one set of tags for the drupal version and another for the module 'milestone' version? --Jeff
On 2/3/06, Jeff Eaton <jeff@viapositiva.net> wrote:
That raises a question for me, though -- what happens if I want to release a major new version of my module in three months, after 4.7 has shipped? Should I start using one set of tags for the drupal version and another for the module 'milestone' version?
I think the problem that you'd run in to there is lots of extra support. You would have to then: 1) keep three branches open. The 'original' release that coincides with the Drupal release, the 'new' release that still will work on the latest Drupal release, and HEAD. or 2) drop the original release, and field bug reports for it by saying 'just get the new version, and run the update script. You'll probably have to do some digging when fielding new bug reports, since you'll want to know which version of your module is actually getting the report.
From my chair, no thanks. You'll have early adopters/testers that will try your HEAD versions anyway, until HEAD can't run with the last stable Drupal release.
If the cvs+project module handles custom tags and not just the 'official' ones, I suppose most of my objections would be moot, but even then you have the extra problem of users filing reports against the right version of your module, which *might* be the same version of Drupal. You could handle that by putting a version number or the Id tag in your settings or somewhere. It's just my opinion that new features are for HEAD, and only HEAD. I've been wrong before (in fact, it's my defining characteristic.) :) -- e www.eafarris.com
Truth, I just won't do it. I'm rather release a new module and retire the old one come version shift time. I develop modules for my use, and return them to the Drupal community because, well, I just do. But I don't do feature request for free because 1- it will never end 2- I'd have to find out which version a person is using to And yes, schema and feature complete is the earliest I'll ever tag a project. I may refactor the code after bug fix requests settle down On 2/3/06, Jeff Eaton <jeff@viapositiva.net> wrote:
That raises a question for me, though -- what happens if I want to release a major new version of my module in three months, after 4.7 has shipped? Should I start using one set of tags for the drupal version and another for the module 'milestone' version?
participants (4)
-
Earl Dunovant -
eric Farris -
Jeff Eaton -
Syscrusher