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

Consider using different versions when new releases are made #94

Open
Sabryr opened this issue Nov 26, 2018 · 2 comments
Open

Consider using different versions when new releases are made #94

Sabryr opened this issue Nov 26, 2018 · 2 comments
Assignees

Comments

@Sabryr
Copy link

Sabryr commented Nov 26, 2018

I am assisting a user to use plink2 on our HPC cluster and your versioning course issues for us.

i.e. using the same version for different releases and distinguish them using a date in brackets.

Concerns this version http://s3.amazonaws.com/plink2-assets/plink2_linux_x86_64_20181028.zip)
When using February version
-bash-4.1$ plink2 --version
PLINK v2.00a2LM 64-bit Intel (15 Feb 2018)

When using October version
bash-4.1$ plink2 --version
PLINK v2.00a2LM 64-bit Intel (28 Oct 2018)

@chrchang
Copy link
Owner

I was planning to start using real version numbers at the beginning of beta testing. (About 85% of the way there; still need merge and multiallelic-dosage functions before the program skeleton is complete.)

@Sabryr
Copy link
Author

Sabryr commented Nov 26, 2018

Thank you for the update.

@chrchang chrchang self-assigned this Jan 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants