Hi all,

before starting a release vote again and starting discussing the version number there, let's try to find an agreement before :)

So now that we have had a test release 0.1.1 I think everybody would be ok to move to versions >=1.0.0 I suppose. For developers implementing against the health check API and annotations I think it is important to quickly be able to tell apart newer from older without digging in documentation (which often just does not happen, then developers do the wrong thing). So for me it would be important to use a version number higher than the following two Sling maven artifacts:

org.apache.sling:org.apache.sling.hc.annotations:1.0.6
org.apache.sling:org.apache.sling.hc.api:1.0.2

So for
org.apache.felix:org.apache.felix.healthcheck.annotation
org.apache.felix:org.apache.felix.healthcheck.api
I would suggest to use at least 1.0.8 and 1.0.4 respectively.

For the modules core, generalchecks and webconsoleplugin it is just a version number and it does not really matter. Also for the OSGi package export version of the two API packages it could be anything really.

So we have the following options:

1) everything 1.0.0 is not a good option (because then it's not clear enough that Felix API/annotations are newer than Sling)
2) everything 1.1.0 (would work for me)
3) everything 1.5.0 (would work for me)
4) everything 2.0.0 (what I proposed initially, still my favorite)
5) mixed approach of using 1.0.8 and 1.0.4 for annotations/api, 1.0.0 for everything else (where it does not matter)

WDYT?

-Georg


Reply via email to