Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Publish/socialize a roadmap #591

Closed
laserson opened this issue Feb 25, 2015 · 6 comments
Closed

Publish/socialize a roadmap #591

laserson opened this issue Feb 25, 2015 · 6 comments

Comments

@laserson
Copy link
Contributor

No description provided.

@massie
Copy link
Member

massie commented Feb 26, 2015

Created a 0.17.0 milestone for us to use for this. We can socialize and tracker progress using the milestone features of github.

https://github.com/bigdatagenomics/adam/milestones

@ryan-williams
Copy link
Member

How set in stone are the issues in the 0.17.0 milestone?

#599 at least seems like it'd take a while to fix in ADAM, since it will need a Spark release after the necessary changes make it in to Spark.

Any interest in doing an 0.16.1 release, or punting some of those issues beyond 0.17.0 so that we can get it out the door sooner? 0.16.0 was > 3mos ago…

@fnothaft
Copy link
Member

@ryan-williams we're hoping to cut a 0.17.0 "soon" --> hopefully this week. I've just added 0.18.0 and 1.0.0 milestones and retagged issues as necessary.

@heuermh
Copy link
Member

heuermh commented Nov 2, 2015

@massie It was discussed in a recent phone call that we should post upcoming release intentions to the developer mailing list.

I created 0.18.2 and 0.19.0 milestones, and understand that 0.18.2 will be for fixing issue #872 and that 0.19.0 will be for performance improvements, but I don't have any further details. Might you be able to write the release intentions post?

I will send the 0.18.1 release announcement once bigdatagenomics/bigdatagenomics.github.io#9 has been merged and the blog updated (or with a little hand holding, I should be able to do that myself).

@fnothaft
Copy link
Member

See #1048, #1088, #1089. Shall we close this in favor of those?

@heuermh
Copy link
Member

heuermh commented Jul 20, 2016

+1

@heuermh heuermh closed this as completed Sep 8, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants