Question
Please discuss some (maybe just tentative) roadmap where haystack will go in the future, and how fast you intend to move.
Additional context
Such kind of transparency would help gather more community support and make the project more successful. And as a German team I believe you guys must already have the answers well planned. :smiley:
@tholor, @Timoeller @tanaysoni
Hi @dany-nonstop,
Good point. We do have an internal roadmap and quite clear directions for haystack in our minds. As the project and the whole field are still quite young the roadmap changes frequently (e.g. as new methods get released). We also don't believe in "waterfall" planning of long term releases, but rather work in an agile environment. However, we totally believe that transparency on "long term directions" is very important to share with the community.
We will evaluate a few different formats of how we can share this effectively and give an update.
If you have any great examples in mind from other open-source projects: happy to hear :)
Can you shed some light on when the next release is planned?
I'm noticing more and more useful functionality in master which aren't in 0.3.0.
We currently aim for next week or the week afterwards :)
Hey @maxupp,
We switched to some tooling that allows us now to share our roadmap and sprint planning 100 % openly and in real-time with the community :)
Check-out the docs to see how you can access it:
https://haystack.deepset.ai/en/docs/roadmapmd
Looking forward to getting your feedback on this!
That's great news. I'm just now switching over to 0.4.0. Will you be updating the Docker images as well?
Yep, deepset/haystack-cpu is now updated. The gpu version has some hick up, but should be fixed soon (#436 )
@maxupp both docker images (GPU and CPU) are now updated
Most helpful comment
Hi @dany-nonstop,
Good point. We do have an internal roadmap and quite clear directions for haystack in our minds. As the project and the whole field are still quite young the roadmap changes frequently (e.g. as new methods get released). We also don't believe in "waterfall" planning of long term releases, but rather work in an agile environment. However, we totally believe that transparency on "long term directions" is very important to share with the community.
We will evaluate a few different formats of how we can share this effectively and give an update.
If you have any great examples in mind from other open-source projects: happy to hear :)