I agree with Justin and Juliana and would suggest; Spend some time to get
the release process automated and smooth, then start a 0.x release train,
with no compatibility guarantees.
On Sun, Aug 26, 2018 at 5:29 PM, Julian Feinauer <
j.feina...@pragmaticminds.de> wrote:
> Hi Justin,
>
>
>
> I
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
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,
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?
