> Will 3.2 contain the bugfixes that are in 3.0.2 as well?
If the bugfix affects both 3.2 and 3.0.2, yes. Otherwise it will only go in
the affected version.
> Is 3.x.y just 3.0.x plus new stuff? Where most of the time y is 0, unless
there's a really serious issue that needs fixing?
You can't really compare 3.0.y with 3.x(.y) because they're two different
versioning schemes. To make it a bit clearer:
Old model:
* x.y.z, where:
* x.y represents the "major" version (eg: 2.1, 2.2)
* z represents the "minor" version (eg: 2.1.1, 2.2.2)
New model:
* a.b(.c), where:
* a represents the "major" version (3, 4, 5)
* b represents the "minor" version (3.1, 3.2, 4.1, etc), where:
* if b is even, it' a tick release, meaning it can contain both
bugfixes and new features.
* if b is odd, it's a tock release, meaning it can only contain
bugfixes.
* c is a "subminor" optional version, which will only happen in emergency
situations, for example, if a critical/blocker bug is discovered before the
next release is out. So we probably won't have a 3.1.1, unless a critical
bug is discovered in 3.1 and needs urgent fix before 3.2.
The 3.0.x series is an interim stabilization release using the old
versioning scheme, and will only receive bug fixes that affects it.
2015-12-09 18:21 GMT-08:00 Maciek Sakrejda <mac...@heroku.com>:
> I'm still confused, even after reading the blog post twice (and reading
> the linked Intel post). I understand what you are doing conceptually, but
> I'm having a hard time mapping that to actual planned release numbers.
>
> > The 3.0.2 will only contain bugfixes, while 3.2 will introduce new
> features.
>
>
>
