I think a cutoff date on the 28th would be fine but I also think it would be fine to do another 1.3 release later on with critical backported bug fixes only. It would remove unnecessary pressure to get 2.0 out of the door as soon as possible.
All the best, Matt On Tue, Feb 22, 2022 at 11:42 PM Sergio Ramazzina (SERASOFT) < [email protected]> wrote: > Hi Hans, > > as you know we are hardly working to fix the memory leak issues we are > getting from our long running processes running in production. We think > we are going very well. During th enext few ours I will open a few JIRA > issues to push some other PR to fix the lates bugs we found lastly. > > I ask you if we can postpone the cutoff date to mid of March (March 15th > is fine I think) to be able to catch and close the latest things. The > battle is not win yet but I think anyone will benefit from this hard > work to make our Hop even stronger. > > Let me know what you think. > > Best > > Sergio > > Il 22/02/2022 19:38, Hans Van Akelyen ha scritto: > > Hello Hoppers, > > > > The development on version 1.2.0 started on the 15th of January and we > have > > made some great progress, I would like to thank everyone that has been > > creating tickets and solving them. > > Currently we are at 65 tickets solved, including mostly bug fixes and > some > > nice new features. > > For those interested, a full list on what has happened on 1.2.0 can be > > found in Jira [1] > > > > I think we have come to a point where we can start thinking about the > next > > release, I would like to suggest the end of the month (28th February) as > > the final day where we will be merging pull requests and start working on > > the vote then. > > > > As it is really hard to maintain two separate branches and the EOL of > java > > 8 has come into sight (no worries it will still receive security fixes) I > > would like to suggest going for Hop 2.0 after this release. Hop 2.0 will > be > > our first full java 11 release and include some breaking API changes. > > > > Love to hear your thoughts! > > > > Cheers, > > Hans > > > > [1] > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12324323&version=12351230 > > > -- Neo4j Chief Solutions Architect *✉ *[email protected]
