Re: [Hawkular-dev] Inventory to break its REST API
Hello,
It is not so much of a vote but an example of what Hawkular Metrics has been doing. The
project has been released on 0.x.y version under RHQ Metrics name and will continue to get
released under the same version scheme under the Hawkular organization. But Metrics is a
little bit atypical because we had official releases along the way and will keep
releasing. If you plan on getting community releases then it might be a good idea to use
0.x.y until the API is stable and the project matures.
Thank you,
Stefan
----- Original Message -----
From: "Lukas Krejci" <lkrejci(a)redhat.com>
To: hawkular-dev(a)lists.jboss.org
Sent: Thursday, March 12, 2015 8:38:30 AM
Subject: [Hawkular-dev] Inventory to break its REST API
Hi,
the time has come to merge the "future" branch of inventory to its master so
that we don't prolong the schizophrenic situation of the component.
Because that merge will break the REST API, we need to sort out the recent
discussion about how to handle the breaking changes in the builds.
There were 2 proposals:
[ ] adopt 0.x.y versioning or some such so that we can actually increase a
version with breaking changes *, or
[ ] release timed snapshots and depend on them rather then simple -SNAPSHOT.
Please vote or propose other solutions so that we can move forward and not
piss off whole nations..
Cheers,
Lukas
* semver allows 0.x to do breaking changes without increasing the major
version, because leading zero means "before the first stable release"
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev