Re: CherryPy and the new versioning scheme

Thank you Joel for the heads up on this.

- Sylvain

2016-02-09 7:16 GMT+01:00 Joel Rivera <[email protected]>:

> Hello all!
>
> Probably some of you had already noticed the quick increments on the
> version numbers of CherryPy. It is specially notorious given the
> history of the project.
>
> The last version of CherryPy on the PyPI is at 5.0.1 [1]. As you can see
> on the
> changelog [1] we went from 3.8.2 -> 4.0 -> 5.0 -> 5.0.1 in a relative
> short amount of time.
>
> This took by surprise a lot of people (me included) and I would like to
> clarify
> a little bit more about the reason behind this change.
>
> If you take a close look to the changelog [2] you will see that it only
> includes
> version from 3.3.0 and up and the first record states:
>
>   "CherryPy adopts semver".
>
> For those who are not familiar with semver [3] in a nutshell follows this
> conventions (from [3]):
>
>   Given a version number MAJOR.MINOR.PATCH, increment the:
>
>   MAJOR version when you make incompatible API changes,
>   MINOR version when you add functionality in a backwards-compatible
>   manner, and PATCH version when you make backwards-compatible bug fixes.
>   Additional labels for pre-release and build metadata are available as
>   extensions to the MAJOR.MINOR.PATCH format.
>
> In the history of CherryPy every mayor version would probably mean a
> complete
> rewrite, but as you can see this is not the case anymore.
>
> This versioning scheme might suit it well to the project, given that
> the current developers that are involved tends to move forward the project
> by short "bursts" of dev time and PR merging, having this clear convention
> helps us to do a release on the spot and avoid losing the momentum which
> will probably end up queuing the changes for a release months later.
>
> I hope you all embrace this new versioning scheme and contribute to have
> faster releases given the new conventions.
>
> Cheers!
>
> [1] https://pypi.python.org/pypi/CherryPy
> [2]
> https://bitbucket.org/cherrypy/cherrypy/raw/766259a3f540186e9f5c327d0bb75b7e7fe5d24d/CHANGES.txt
> [3] http://semver.org/
> --
> Rivera²
>
> --
> You received this message because you are subscribed to the Google Groups
> "cherrypy-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to cherrypy-users+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/[email protected]
> To post to this group, send email to cherrypy-users-/JYPxA39Uh5TLH3MbocFF+G/[email protected]
> Visit this group at https://groups.google.com/group/cherrypy-users.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
- Sylvain
http://www.defuze.org
http://twitter.com/lawouach

-- 
You received this message because you are subscribed to the Google Groups "cherrypy-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cherrypy-users+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/[email protected]
To post to this group, send email to cherrypy-users-/JYPxA39Uh5TLH3MbocFF+G/[email protected]
Visit this group at https://groups.google.com/group/cherrypy-users.
For more options, visit https://groups.google.com/d/optout.