Hi all,
well we created a first version of the API but lacked the feedback and
discussion if this was the way to go. So I knew that some major refactoring of
the API was to come.
I am a strong advocate of SemVer versioning sceme ... didn't want to bump the
major version up too far ;-)
So currently we are in the process of discussing exactly these expected major
API changes. Hopefully resulting in a far more stable API after that.
Additionally there were some issues with the build, that would have made a
release difficult, but I fixed the last of these problems last week.
As we are getting more and more requests for PLC4X consulting, I too will
definitely opt for a release pretty soon.
So I would propose, that we do the following steps:
- Finish the API discussion and decide on the changes
- Implement the changes
- In parallel I will try to help an upstream library (ethernet/ip driver) get
released in a new version (we currently depend on a SNAPSHOT version)
- Then we'll try to do our first release
As a timeframe I would like us to have a release before the ApacheCon NA in
Montreal (That's less than 30 days).
Chris
Am 26.08.18, 11:30 schrieb "Julian Feinauer" <j.feina...@pragmaticminds.de>:
Hi Justin,
I like your suggestion and also wanted to suggest a first release soon as
we start to experiment with plc4j a lot in one project and I don’t like to
reference snapshots with the lot of changes going on (or are planned).
What do the others think of this?
Julian
Am 26.08.18, 02:22 schrieb "Justin Mclean" <jus...@classsoftware.com>:
Hi,
While looking through the incubator reports it’s come to my attention
that this podling hasn’t made a release yet and has been in the incubator for
250+ days. "Release early and release often” should be the guideline to
follow. What is holding up this project making it first release? Remember a
first release doesn’t have to be perfect and each release just needs to be
better than the last.
Thanks,
Justin
