Hi Christian,
I think the API [1] is proven and in use since 2013 (I would guess >
2000 checks to exist out in the wild in code bases of various projects).
The Felix API was carefully adjusted with your feedback (e.g. the
removal of state DEBUG, FELIX-6016) to make the migration path really
easy for 99% of the checks that exist.
In the migration guide in Sling that I will write I don't think I can
ask people to change from stable version Sling HC API 1.0.2 to a Felix
API "preview version" 0.1.0. Also, maintaining Sling HCs and Felix HCs
in parallel for some time is the worst of all options IMHO.
So this really leaves us to push forward with Felix HC API 2.0.0 - if we
find valid reasons to make changes we'll just bump versions according
semantic versioning.
-Georg
[1] https://github.com/apache/sling-org-apache-sling-hc-api
On 2019-01-31 16:30, Christian Schneider wrote:
I think we should not yet release a stable version. Instead I propose
to
release a 0.1.0.
WDYT?
Christian
Am Mo., 28. Jan. 2019 um 09:44 Uhr schrieb Georg Henzler
<fe...@ghenzler.de
:
Hi all,
We solved 11 issues in this release:
https://issues.apache.org/jira/issues/?jql=issuekey%20in%20(FELIX-6024%2CFELIX-6025%2CFELIX-6017%2CFELIX-6018%2CFELIX-6016%2CFELIX-6012%2CFELIX-6011%2CFELIX-6010%2CFELIX-6005%2CFELIX-6004%2CFELIX-5952)
(@PMC: Could you please create the versions for this and next release
in
JIRA for the 5 modules?)
Staging repository:
https://repository.apache.org/content/repositories/orgapachefelix-1279/
You can use this UNIX script to download the release and verify the
signatures:
http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh
Usage:
sh check_staged_release.sh 1279 /tmp/felix-staging
Please vote to approve this release:
[ ] +1 Approve the release
[ ] -1 Veto the release (please provide specific comments)
This vote will be open for 72 hours.
-Georg
--
