Create a roadmap for reactivesearch

[metagrover]

To keeps things transparent, we should create a development and support roadmap for Reactivesearch v2 and v3.

• It should define the content of releases.
• It can include release targets, migration guides and support details.
• We can also plan out the components that are going to be added in the future releases for a current version.

Open to suggestions on this.

Related: https://github.com/nodejs/Release

[ghost]

I think that utilising the projects board on Github is a nice way to handle a roadmap. I have seen other repositories using a different board per release. This allows users to see which features are coming up in the next release and allow contributors to priorities certain issues.

[brod-dotdev]

ola @george-dotdev 👋

@metagrover Also interested in a roadmap and updated documentation for library development purposes - for the past hour or so I've been trying to figure out what appbaseio package I should be working with to add a click handler for markers in reactivemaps, I assumed @appbaseio/reactivemaps but stumbled on a few issues with the source code not aligning with whats available on NPM, afterwards I noticed the npm package links to here instead.

At this point I'm confused as to whether the marker click handler functionality already exists, in which package that functionality exists and where the source code for that package is.

[metagrover]

Hi @brod-dotdev, we maintain reactivemaps in this monorepo along with reactivesearch for react, vue and react-native. You can find the maps package implementation here - https://github.com/appbaseio/reactivesearch/tree/next/packages/maps

And, you can find Reactivemaps docs here.

---

I assumed @appbaseio/reactivemaps but stumbled on a few issues with the source code not aligning with whats available on NPM

We used to maintain reactivemaps version 1.x here, but it only contains the reactivemaps website and old versions at the moment.

[gaving]

👍 For this.

Really keen to bump Reactivesearch in our project to 3 to take advantage of this kind of thing but it's a little unclear on the status on v3 and how much breakage it'll introduce.

[siddharthlatest]

@gaving The migration guide covers the breaking changes involved for v3 migration: https://opensource.appbase.io/reactive-manual/advanced/migrationguide.html

[gaving]

@siddharthlatest Ah missed that, thanks!

I don't suppose you a rough timeline of when v3 goes stable? Also, is Reactivesearch 3 compatible with Elasticsearch 6.x?

Apologies for asking dumb questions, can't see it detailed anywhere.

I see this issue adding ES7 support but assume that means RS is compatible with both ES 6 and 7.

[siddharthlatest]

It’s going to be soonish - we’re waiting on closing out the reported bugs and some WIP PRs.

On Mon, Jul 22, 2019 at 5:57 PM Gavin Gilmour notifications@github.com wrote:

@siddharthlatest https://github.com/siddharthlatest Ah missed that, thanks!

I don't suppose you a rough timeline of when v3 goes stable?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/appbaseio/reactivesearch/issues/491?email_source=notifications&email_token=AAEZ2GRAX7O5EOBEIF2RLSTQAWRT7A5CNFSM4FREQGUKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2PYG7Q#issuecomment-513770366, or mute the thread https://github.com/notifications/unsubscribe-auth/AAEZ2GWJUZ277D6EQKJS6XDQAWRT7ANCNFSM4FREQGUA .