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

Release ADAM version 0.21.0 #1088

Closed
fnothaft opened this Issue Jul 20, 2016 · 12 comments

Comments

Projects
3 participants
@fnothaft
Member

fnothaft commented Jul 20, 2016

Timeline: November 15, 2016
Release goal: Documentation and code changes to support ADAM paper.

0.21.0 Milestone
0.21.0 Project

@heuermh

This comment has been minimized.

Show comment
Hide comment
@heuermh

heuermh Jul 21, 2016

Member

Possible new features:
Sequence, slice, and read schema
GA4GH protobuf schema
Phenotype schema, e.g. Phenopackets
Graph assembly schema
Pipe API for external bioinformatics applications
Snap, Freebayes, and SnpEff support via Pipe API

Member

heuermh commented Jul 21, 2016

Possible new features:
Sequence, slice, and read schema
GA4GH protobuf schema
Phenotype schema, e.g. Phenopackets
Graph assembly schema
Pipe API for external bioinformatics applications
Snap, Freebayes, and SnpEff support via Pipe API

@heuermh

This comment has been minimized.

Show comment
Hide comment
@heuermh

heuermh Oct 14, 2016

Member

Would it be ok to truncate the checkboxes from the issue description above and instead use the milestone for tagging issues and the project for triaging them?

Member

heuermh commented Oct 14, 2016

Would it be ok to truncate the checkboxes from the issue description above and instead use the milestone for tagging issues and the project for triaging them?

@fnothaft

This comment has been minimized.

Show comment
Hide comment
@fnothaft

fnothaft Oct 14, 2016

Member

Would it be ok to truncate the checkboxes from the issue description above and instead use the milestone for tagging issues and the project for triaging them?

I assume s/project/issue/g in the above comment ("...and the issue for triaging...")? If so, yes, that sounds good to me; that's how we were tracking issues for releases prior to 0.20.0.

Member

fnothaft commented Oct 14, 2016

Would it be ok to truncate the checkboxes from the issue description above and instead use the milestone for tagging issues and the project for triaging them?

I assume s/project/issue/g in the above comment ("...and the issue for triaging...")? If so, yes, that sounds good to me; that's how we were tracking issues for releases prior to 0.20.0.

@heuermh

This comment has been minimized.

Show comment
Hide comment
@heuermh

heuermh Oct 14, 2016

Member

I haven't had that much coffee yet, so I think I said the right thing. :)

Doing the checkboxes in these issues was kind of redundant with tagging via Milestone tags, although grouping individual issues into themes might have been somewhat useful.

By project I mean this https://github.com/bigdatagenomics/adam/projects/3. By triage I mean 1) tag issues with Milestones and 2) use the project trello-like cards for the what's done/what's not view and any other intermediate categorization (in progress, needs review, etc.), if that might be useful.

Member

heuermh commented Oct 14, 2016

I haven't had that much coffee yet, so I think I said the right thing. :)

Doing the checkboxes in these issues was kind of redundant with tagging via Milestone tags, although grouping individual issues into themes might have been somewhat useful.

By project I mean this https://github.com/bigdatagenomics/adam/projects/3. By triage I mean 1) tag issues with Milestones and 2) use the project trello-like cards for the what's done/what's not view and any other intermediate categorization (in progress, needs review, etc.), if that might be useful.

@fnothaft

This comment has been minimized.

Show comment
Hide comment
@fnothaft

fnothaft Oct 14, 2016

Member

Oh, cool! Misunderstanding was on my side; I'd forgotten about the new projects feature. That SGTM!

Member

fnothaft commented Oct 14, 2016

Oh, cool! Misunderstanding was on my side; I'd forgotten about the new projects feature. That SGTM!

@lbergelson

This comment has been minimized.

Show comment
Hide comment
@lbergelson

lbergelson Nov 30, 2016

Contributor

What's the status of this? Is there still going to be a release soon or will it be delayed for a while?

Contributor

lbergelson commented Nov 30, 2016

What's the status of this? Is there still going to be a release soon or will it be delayed for a while?

@fnothaft

This comment has been minimized.

Show comment
Hide comment
@fnothaft

fnothaft Nov 30, 2016

Member

Hi @lbergelson! Sorry for the delay here. We had a couple of issues pull out by a week with the Thanksgiving holiday. @heuermh and I were sitting together today and working on the release; I think we'll close within the week.

Member

fnothaft commented Nov 30, 2016

Hi @lbergelson! Sorry for the delay here. We had a couple of issues pull out by a week with the Thanksgiving holiday. @heuermh and I were sitting together today and working on the release; I think we'll close within the week.

@lbergelson

This comment has been minimized.

Show comment
Hide comment
@lbergelson

lbergelson Nov 30, 2016

Contributor

No problem! Thanks for the update. Holidays always slow everything down, even when you've already tried to account for it.

Contributor

lbergelson commented Nov 30, 2016

No problem! Thanks for the update. Holidays always slow everything down, even when you've already tried to account for it.

@heuermh

This comment has been minimized.

Show comment
Hide comment
@heuermh

heuermh Jan 6, 2017

Member

All the 0.21.0 milestone issues and pull requests have been closed and merged, so I'll work on cutting the release this afternoon. The only remaining task is to update the release notes, which for better or worse must still be edited and committed manually during release process (see #936).

Member

heuermh commented Jan 6, 2017

All the 0.21.0 milestone issues and pull requests have been closed and merged, so I'll work on cutting the release this afternoon. The only remaining task is to update the release notes, which for better or worse must still be edited and committed manually during release process (see #936).

@fnothaft

This comment has been minimized.

Show comment
Hide comment
@fnothaft

fnothaft Jan 6, 2017

Member

Thank you, @heuermh!

Member

fnothaft commented Jan 6, 2017

Thank you, @heuermh!

@heuermh

This comment has been minimized.

Show comment
Hide comment
@heuermh

heuermh Jan 6, 2017

Member

Fixed by commit 6491724. Rsync to Maven Central will take a few hours.

Member

heuermh commented Jan 6, 2017

Fixed by commit 6491724. Rsync to Maven Central will take a few hours.

@heuermh heuermh closed this Jan 6, 2017

@heuermh

This comment has been minimized.

Show comment
Hide comment
@heuermh

heuermh Jan 9, 2017

Member

Blog announcement pull request at bigdatagenomics/bigdatagenomics.github.io#13. After that is merged and the site updated, I'll post an announcement to adam-developers@ and via Twitter.

Member

heuermh commented Jan 9, 2017

Blog announcement pull request at bigdatagenomics/bigdatagenomics.github.io#13. After that is merged and the site updated, I'll post an announcement to adam-developers@ and via Twitter.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment