search

IHEC / ihec-assay-standards

This repo is for code and documentation associated with the ihec-assay-standards working group
Apache License 2.0
5 stars 5 forks source link

Reorganized folders following IHEC Annual Meeting 2017 proposal. #3

Closed dbujold closed 6 years ago

sitag commented 7 years ago

Can we do a release before we merge in this request?

tsierocinski commented 7 years ago

Can my email address be removed from this mailing list please?

Thank you.

Thomas

On Oct 17, 2017 5:09 PM, "sitag" notifications@github.com wrote:

Can we do a release before we merge in this request?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/IHEC/ihec-assay-standards/pull/3#issuecomment-337416948, or mute the thread https://github.com/notifications/unsubscribe-auth/AQyePa8C5Ob2YyEXFVm7qHKysx3l__APks5stUGrgaJpZM4P8gi3 .

dbujold commented 7 years ago

Hi Thomas, if you're talking about GitHub notifications, you have to remove yourself as a watcher in the ASWG GitHub.

Sincerely,

David

On 10/17/2017 08:33 PM, tsierocinski wrote:

Can my email address be removed from this mailing list please?

Thank you.

Thomas

On Oct 17, 2017 5:09 PM, "sitag" notifications@github.com wrote:

Can we do a release before we merge in this request?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/IHEC/ihec-assay-standards/pull/3#issuecomment-337416948, or mute the thread https://github.com/notifications/unsubscribe-auth/AQyePa8C5Ob2YyEXFVm7qHKysx3l__APks5stUGrgaJpZM4P8gi3 .

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/IHEC/ihec-assay-standards/pull/3#issuecomment-337421943, or mute the thread https://github.com/notifications/unsubscribe-auth/AJO545GjvR2QjxD1Ov1yb0RaHA5TIgSyks5stUdygaJpZM4P8gi3.

dbujold commented 7 years ago

Sure can, although isn't it better to do the cleanup beforehand? Or should we tag the current version 0.1, and then merge the PR in master, in preparation for version 1?

Thanks,

David

On 10/17/2017 08:09 PM, sitag wrote:

Can we do a release before we merge in this request?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/IHEC/ihec-assay-standards/pull/3#issuecomment-337416948, or mute the thread https://github.com/notifications/unsubscribe-auth/AJO540auCVLbc0dBMMF6BjDdcejEvgwnks5stUGrgaJpZM4P8gi3.

sitag commented 6 years ago

Since things will move around quite a bit, in case someone needs it, it would be good to have a snapshot of how things are before this happens for easy reference (as vs digging through commits). Releasing in this state is not ideal - but maybe there's another way to tag the state prior to the merge?

dbujold commented 6 years ago

Hi Sita, what would you think of creating Git tags for new versions that would correspond to annual IHEC meetings? So the current version, pre-merge, would be tag "2017-10-12". That would allow us to see what was done before reshuffling things around. And then the next tag could be at next year's meeting, or before that if we decide that we've reached a big enough milestone.

Thank you,

David

On 11/03/2017 04:19 PM, sitag wrote:

Since things will move around quite a bit, in case someone needs it, it would be good to have a snapshot of how things are before this happens for easy reference (as vs digging through commits). Releasing in this state is not idea - but maybe there's another way to tag the state prior to the merge?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/IHEC/ihec-assay-standards/pull/3#issuecomment-341815535, or mute the thread https://github.com/notifications/unsubscribe-auth/AJO54wyPJ3rkMwaOkPWsCOHxEd9SzwPYks5sy3VZgaJpZM4P8gi3.

sitag commented 6 years ago

Thanks, David. That sounds like a good plan.