Completion of documentation will prove to be an elusive target I'm afraid. To tie the task down a bit I collected a number of 'documentation' JIRA cases under HOP-2643 <https://issues.apache.org/jira/browse/HOP-2643> I would suggest we do this like any other feature: decide what to do up-front (like it under HOP-2643) and push everything else out to beyond 1.0 unless it's a really obvious omission in the docs.
Cheers, Matt On Mon, Mar 22, 2021 at 1:09 PM Sergio Ramazzina (SERASOFT) < [email protected]> wrote: > Hi all, > > I personally agree with Hans proposal on what to do before moving to 1.0. > > I personally think that necessarily the completion of user documentation > is a must if we want to attrach a wide number of users. > > Cheers > > Sergio > > Il 22/03/2021 11:54, Hans Van Akelyen ha scritto: > > Hi All, > > > > It was mentioned in a couple of previous emails and also on our chat but > we > > haven't had a formal discussion about it yet, so here it is. > > > > As we are nearing our 0.70 release and have made great progress over the > > past few months, > > we have left the path of great API changes and are moving towards > > implementing new features and fixing bugs. > > > > We have reached a point where we can start talking about moving our > version > > number in the direction of a 1.0 release. > > > > Here is an non-exhaustive list of what I think we still need to do before > > we can move to 1.0 > > - Add more Integration tests > > - Complete our user oriented documentation > > - Give Hop Web a thorough test and some fixes > > - Fix all bugs that show up from the integration tests and user feedback > > > > My proposal is to move our version number to 0.99 after our 0.70 release > > and focus on these areas. We can release 0.99 as a 1.0 preview version, > > resolve issues that still show up and then move to 1.0 > > > > I would love to hear your thoughts on what we should still focus on > before > > "going 1.0". > > > > Cheers, > > Hans > > >
