Page 1 of 1

OOo version numbering conventions

Posted: Wed Jul 21, 2010 8:14 pm
by mark_orion
I am curious if there is a difference between even and odd minor numbers in the OOo version numbering - like the Linux kernel versions. Are even releases like 3.2 more focusing on features while odd releases 3.1 3.3 focus on stability?

Re: OOo version numbering conventions

Posted: Wed Jul 21, 2010 9:07 pm
by acknak
Yes. The plan (as I understand it, anyway) is to release a new version four times a year, with alternating versions getting primarily bug fixes or primarily new features. Minor releases (3.2.1) are made for high-priority bug fixes.

As far as I can tell, this is not a hard and fast rule: there are bug fixes in every release; sometimes there are changes made in a nominally "bugfix" release. It's mostly a matter of which area the developers are focused on: it's hard to do both bugs and features all the time.

Re: OOo version numbering conventions

Posted: Wed Jul 21, 2010 10:10 pm
by RGB
mark_orion wrote:I am curious if there is a difference between even and odd minor numbers in the OOo version numbering - like the Linux kernel versions. Are even releases like 3.2 more focusing on features while odd releases 3.1 3.3 focus on stability?
Since 2.6, Linux kernel do not use that convention anymore ;) (wine project use it, but nobody uses the "stable" version...)
As acknak pointed out the "theory" is <big refactoring>.<new features>.<bugfix>, but those big categories are a bit blurred... like on any big software project, I think.