[development] releases, recommended/supported changing automatically on release creation...

Khalid Baheyeldin kb at 2bits.com
Tue Mar 11 01:43:12 UTC 2008

On Mon, Mar 10, 2008 at 9:38 PM, Earl Miles <merlin at logrus.com> wrote:

> In fact, in my own personal world, the API is
> pretty much what controls the major release #, but I realize that *most*
> projects don't have that as an issue.

+1 on this.

I do the same, branch and up the X number when things will break. Otherwise
if you are adding features or fixing bugs without breaking things, then
on the same X number.

Did this for a couple of modules of mine already.
Khalid M. Baheyeldin
2bits.com, Inc.
Drupal optimization, development, customization and consulting.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/development/attachments/20080310/8874943c/attachment.htm 

More information about the development mailing list