https://nf-co.re logo
Join Slack
Powered by
Okay, so the tools release is coming up Do we wan...
# rnaseq_dev
e
Okay, so the tools release is coming up Do we want to do: 1. Tools release/template update 2. rnaseq release 3. Arm experimentation or 1. rnaseq release 2. Tools release/template update 3. rnaseq release 4. Arm experimentation
2️⃣ 1
j
I think I displeased folks by holding off previously waiting for the arm resolution, think we need to go for release ASAP
m
second option for me
RELEASE now, to fix the current issue, and then release again
j
But I do want to bump the modules I can bump for arm compatibility now
e
What's the current issue?
@Jonathan Manning, let's just get a stable release before we break things with arm
party this 1
Idk if you've watched the PR https://github.com/nf-core/modules/pull/7747 but it's gonna be a whole thing
Or if you're scared, I can take it over to #C05V9FRJYMV winking cowboy
j
OK, I'd like to bump the modules for improved compatibility, separate from the CI shennanigans, because it should be trivial. But I can do that separately.
p
Hello all 🙂 A week has trickled by.. Any news?
shakefist 1
m
I'll be working on the TEMPLATE sync RN
and from there we're almost done I believe
🎉 1
j
e
This is a perfect example of why we need trunk-based development. The dependency updates are always going to be a moving target.
j
It's the darned sortmerna builds that are messing with me right now
m
@Edmund RFC?
👍🏻 1
e
I'll make that happen.
❤️ 1
m
Not sure, but it could be that we have a case in the pipeline, where the 
-C
flag of the 
process.shell
may cause issues beyond the 
.command.trace
file that should be fixed with Nextflow 25.04.3?
shakefist 1
Ok, maybe not…there are 15 modules using the same 
sed -i
notation. If it was related to the 
-C
flag, that would have caused more issues already.
p
Bloody chomp shakefist facepalm
The number of problems that this simple config change has caused 😩
m
yeah, I did remove this 
-C
in a previous PR
🚀 1
this one has been a mess from the start
nod 1
j
@Phil Ewels putting most of the complexity in https://github.com/nf-core/rnaseq/pull/1529 to one side, would you like me to rename the profile used to pull in aarch64 containers before I release? Noting https://github.com/nf-core/rnaseq/pull/1529#issuecomment-2885718163
p
I don't think so - this is v. likely to change across the board soon, but it's not 100% certain about the profile names that we'll end up with. I'd prefer to have a single renaming / change event.
Thanks for checking 🙏🏻
👍 1
j
OK, release is GO! Those who'd like it to happen quickly can maybe help me with the PRs 😉 . Maxime is off today. Version bumps: https://github.com/nf-core/rnaseq/pull/1563
✅ 1
dancing penguin 1
... and finally the dev -> master https://github.com/nf-core/rnaseq/pull/1564
m
Sorry, I am also off today and on my way to a remote camping spot by the sea without computer, so also not exactly the best setting for PR reviews.
j
haha, no worries- enjoy!
m
Yeah, Sweden is off today
j
release PR is ready to go, fixed conda issues. Do we need an outside review?
m
I am probably not an outsider anyway...I started a review, but then got other things to do...I can still try to do it today.
j
I think a non-Seqeran would probably be sufficient, it's really not much more than a patch release.
party this 1
m
Ok, I will see to squeeze it into the itinerary today somehow.
j
@mashehu has already given us a review (thank you!). I'll go through later and PR his suggestions and we'll be good to go.
m
Ok, fine with me. Can't say that I have found much if anything noteworthy until now.
thankyou 1
Open in Slack
PreviousNext
Powered by