Hi all, Maybe we should revive this discussion now a week later? It's been a good active week with 3-4 issues resolved. Our CHANGES.md has the unreleased updates lined up:
* [METAMODEL-198] - Fixed support for JDBC TIMESTAMP precision to match the underlying database's precision. * [METAMODEL-200] - Added optional "APPROXIMATE" keyword to query syntax for aggregate functions. * [METAMODEL-144] - Automated binary packaging of the MetaModel project. * [METAMODEL-197] - ElasticSearch schema update/change after CREATE TABLE statements. * [METAMODEL-199] - Fixed a bug in query parser when parsing two consecutive WHERE items with parentheses around them. We even have two minor PRs pending which we could also add (MongoDB version update and a build/travis improvement). For me this is enough to justify a 4.4.1 release. What do you think? Best regards, Kasper 2015-10-20 8:36 GMT+02:00 Alberto Rodriguez <[email protected]>: > Personally, I'd wait until we include more changes, for me it does not make > much sense to release a new version including just one bugfix. > > Kind regards, > > Alberto > > 2015-10-19 23:13 GMT+02:00 Kasper Sørensen <[email protected] > >: > > > Actually it's not long since we released 4.4.0 and I think there is only > > one bugfix made since it (namely METAMODEL-198 which we merged today). > > > > But anyways I am always fine with making minor releases as long as we are > > happy with the state of the code. For me not important, but also no > issues > > with releasing 4.4.1. > > > > Best regards, > > Kasper > > > > 2015-10-19 22:41 GMT+02:00 Ankit Kumar <[email protected]>: > > > > > Hi All, > > > > > > Wanted to initiate a discussion for the next release for Metamodel > > v4.4.2. > > > There are some new additions to the library and also quite some bug > fixes > > > made. > > > > > > Should we plan a minor release any time soon? > > > > > > Regards > > > Ankit > > > > > >
