I'd like to add my vote for a 2.4.1 release. We don't want to raise the
expectation that there will be substantial new functionality (which would
warrant a 2.5.0 version).
However, if the 2.4.1 release goes well I would certainly suggest that we aim
for a 2.5.0 release in the second half of 20
When it comes to version numbers, I'm more concerned about following
semantic versioning than whether or not it's a major release. Bugfixes
warrant micro version updates, while new features warrant minor version
updates (and backward incompatible API changes are for the major version).
On 14 Decem
On 2016-12-14, Matt Sicker wrote:
> When it comes to version numbers, I'm more concerned about following
> semantic versioning than whether or not it's a major release. Bugfixes
> warrant micro version updates, while new features warrant minor version
> updates (and backward incompatible API chang
On 2016-12-13, Gintautas Grigelionis wrote:
> Thanks for clarification. There are lots of duplications around there, and
> the overall process would surely benefit from some restructuring. I took
> the liberty of extracting the commits particular to style subdirectory
> (there are three of them, i
