Generate Releases and version more frequently

[mfansler]

I am interested in packaging ArchR as a Conda package, which could help alleviate installation issues. However, it appears master has had minor patching since the last Release. Also, dev has had many changes and end-users do appear to use this. It would be helpful to capture fixes and features in Releases. Note that one has the ability to mark Releases as beta, in case one wishes to signal uncertainty about their stability.

[immanuelazn]

Hi Mervin,

I've seen your recent work with respect to getting a conda package built for ArchR, and am really greatful for that work. I am currently doing some final checks with making sure that the brunt of the function reference, and vignettes work within my containerized environment.

Once that is done, I will update 1.0.2 to reflect the current state of master, and 1.0.3 to reflect the current state of dev as a pre-release.

Best,

Immanuel

[mfansler]

I see there is a release! 🎉

For reference, here's the corresponding Bioconda PR. Any suggestion on what R version I should be aiming at? Right now trying R 4.3, which is our latest available.

[immanuelazn]

Thanks for being on top of this and sorry for the delayed response! I was thinking to keeping 1.0.3 to be working with 4.1, and releasing a sub-version with some fixes to dependencies. One of them being the one you pointed out with ggplot legends.

On my end, the fixes are working on both 4.3 and 4.4. I'll ping this discussion board when they're merged in and I create a new release for that.

[immanuelazn]

Hi @mfansler , hope you're doing well. I have updated ArchR to reflect version 1.0.3, and have set the pre-release to point to master with as an official release instead. Thank you again for your support and suggestions.

[mfansler]

I'm a little confused what is going on here. There was a 1.0.3 release in November and that used the v1.0.3 tag. Was that tag changed to point elsewhere?

[immanuelazn]

I see, the 1.0.3 was a pre-release and it was pointing to release candidates. Originally it was connected to a v1.0.3, but I changed it to v1.0.3rc1 and v1.0.3rc2 while we were still adding in last minute changes. v1.0.3 is now a tag that corresponds to the master branch's current commit.