You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hop.apache.org by Hans Van Akelyen <ha...@gmail.com> on 2021/03/22 10:54:07 UTC
[DISCUSS] The road after 0.70
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
Re: [DISCUSS] The road after 0.70
Posted by Matt Casters <ma...@neo4j.com.INVALID>.
Excuse me for the confusion. I didn't create that list. These cases were
already in JIRA.
Please add more cases for those things you think are critical to have for a
1.0 release.
Thanks a lot!
Matt
On Tue, Mar 23, 2021 at 9:57 AM Sergio Ramazzina (SERASOFT) <
sergio.ramazzina@serasoft.it> wrote:
> Hi all,
>
> I personally agree with Hans. The list you prepared Matt is for sure a
> set of needed documentation items but we must think to beginners. We
> need to prevent as much as possible their questions and them all the
> info they need to start working on the platform without any problem.
>
> Cheers
> Sergio
>
> Il 23/03/2021 09:43, Hans Van Akelyen ha scritto:
> > I do agree that "complete" was maybe too strong of a word, thanks for
> > creating those work items.
> > But we do have to close the gap a bit for beginners. When we have more
> > users questions will start flowing in and we can adapt the docs based on
> > that.
> >
> > Cheers,
> > Hans
> >
> > On Tue, 23 Mar 2021 at 09:35, Matt Casters <matt.casters@neo4j.com
> .invalid>
> > wrote:
> >
> >> 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) <
> >> sergio.ramazzina@serasoft.it> 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
> >>>>
>
--
Neo4j Chief Solutions Architect
*✉ *matt.casters@neo4j.com
☎ +32486972937
Re: [DISCUSS] The road after 0.70
Posted by "Sergio Ramazzina (SERASOFT)" <se...@serasoft.it>.
Hi all,
I personally agree with Hans. The list you prepared Matt is for sure a
set of needed documentation items but we must think to beginners. We
need to prevent as much as possible their questions and them all the
info they need to start working on the platform without any problem.
Cheers
Sergio
Il 23/03/2021 09:43, Hans Van Akelyen ha scritto:
> I do agree that "complete" was maybe too strong of a word, thanks for
> creating those work items.
> But we do have to close the gap a bit for beginners. When we have more
> users questions will start flowing in and we can adapt the docs based on
> that.
>
> Cheers,
> Hans
>
> On Tue, 23 Mar 2021 at 09:35, Matt Casters <ma...@neo4j.com.invalid>
> wrote:
>
>> 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) <
>> sergio.ramazzina@serasoft.it> 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
>>>>
Re: [DISCUSS] The road after 0.70
Posted by Hans Van Akelyen <ha...@gmail.com>.
I do agree that "complete" was maybe too strong of a word, thanks for
creating those work items.
But we do have to close the gap a bit for beginners. When we have more
users questions will start flowing in and we can adapt the docs based on
that.
Cheers,
Hans
On Tue, 23 Mar 2021 at 09:35, Matt Casters <ma...@neo4j.com.invalid>
wrote:
> 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) <
> sergio.ramazzina@serasoft.it> 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
> > >
> >
>
Re: [DISCUSS] The road after 0.70
Posted by Matt Casters <ma...@neo4j.com.INVALID>.
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) <
sergio.ramazzina@serasoft.it> 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
> >
>
Re: [DISCUSS] The road after 0.70
Posted by "Sergio Ramazzina (SERASOFT)" <se...@serasoft.it>.
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
>