[development] When should a module be tagged DRUPAL-4-7?

eric Farris eafarris at gmail.com
Fri Feb 3 16:29:58 UTC 2006

On 2/3/06, Syscrusher <syscrusher at 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

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.


More information about the development mailing list