-
Notifications
You must be signed in to change notification settings - Fork 709
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
nextflow edge release documentation for running 3.0 #569
Comments
Agreed @boulderrinnlab ! This was a bit of a Catch 22 situation because this is the first proper DSL2 pipeline we have released and didn't realise we would have these issues until we had these issues 😅 I did put some notes in the CHANGELOG and have been quietly hoping for a stable Nextflow release so I can re-release and these problems will magically disappear! |
Awesome you guys are the best -- thanks for the explanation too ! |
Docs added here b4c71ed :) |
Thank you!!!
It runs like a champ and it feels good to be on the “edge” of a version :)
Thanks again for all you are doing — there are a bunch of students in Boulder CO using this to explore 460 DNA binding proteins — they are grateful too !
JR
[*~*]$ tail -f time
On Mar 17, 2021, at 11:04 AM, Harshil Patel ***@***.******@***.***>> wrote:
Docs added here b4c71ed<b4c71ed> :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#569 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AM5D4QUUAGJLSXFQONYTG6TTEDOLFANCNFSM4XS5RCJQ>.
|
This maybe minor for experts, but the general user will get confused if they run v3.0.
One can easily download the edge-release in the error message.
But it maybe worth updating the nf-core/rnaseq website to give instructions to update with the appropriate edge-release.
Y'all are the best at documentation and just wanted to mention this aspect is missing from the nf-core website install instructions for v3.0
The text was updated successfully, but these errors were encountered: