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 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 > > > -- Niclas Hedhman, Software Developer http://polygene.apache.org - New Energy for Java
