"value":"\n <p>Something I've seen, both with contributed Drupal modules and other open-source projects, over the past few years is they spend a lot of time in the 0.x versions or releasing alpha and beta versions rather than releasing a 1.0 or stable version.<\/p>\n\n<p>I presume it's a concern around backward compatibility and maintaining that once a stable version is released.<\/p>\n\n<p>But, if you want people to use your module or upgrade it to the latest version, that's much easier to do once there's a stable version.<\/p>\n\n<p>Some organisations prohibit using alpha or unstable versions of projects so, if there isn't a stable version, they wouldn't be able to use it.<\/p>\n\n<p>Personally, if I'm using one of my open-source modules, plugins or libraries in production, there should be a stable 1.0 version tagged.<\/p>\n\n<p>Once it's in production, I'm already making an implied commitment that it's going to be stable and I won't break everything in the next release, so why not make that explicit and tag a stable release?<\/p>\n\n<p>Version numbers are free and nothing is stopping you from deprecating code and releasing a new major version with breaking changes in the future, so go ahead and tag that stable version.<\/p>\n\n ",
"format":"full_html",
"processed":"\n <p>Something I've seen, both with contributed Drupal modules and other open-source projects, over the past few years is they spend a lot of time in the 0.x versions or releasing alpha and beta versions rather than releasing a 1.0 or stable version.<\/p>\n\n<p>I presume it's a concern around backward compatibility and maintaining that once a stable version is released.<\/p>\n\n<p>But, if you want people to use your module or upgrade it to the latest version, that's much easier to do once there's a stable version.<\/p>\n\n<p>Some organisations prohibit using alpha or unstable versions of projects so, if there isn't a stable version, they wouldn't be able to use it.<\/p>\n\n<p>Personally, if I'm using one of my open-source modules, plugins or libraries in production, there should be a stable 1.0 version tagged.<\/p>\n\n<p>Once it's in production, I'm already making an implied commitment that it's going to be stable and I won't break everything in the next release, so why not make that explicit and tag a stable release?<\/p>\n\n<p>Version numbers are free and nothing is stopping you from deprecating code and releasing a new major version with breaking changes in the future, so go ahead and tag that stable version.<\/p>\n\n ",