Thanks both for the explanation!
Sounds good to me.
Raúl
El sáb, 10 feb 2024, 22:46, Jacob Wujciak-Jens
escribió:
> Thanks Nic.
>
> For a versioned history I planned to also have the versioned
> 'apache-arrow-x.y.z-cran' tags or maybe 'apache-arrow-x.y.z-r' would be
> less ambiguous as Nic
Thanks Nic.
For a versioned history I planned to also have the versioned
'apache-arrow-x.y.z-cran' tags or maybe 'apache-arrow-x.y.z-r' would be
less ambiguous as Nic mentioned.
The r-universe tag is unversioned so we can update it without any changes
on the r-universe side.
On Sat, Feb 10, 2024
Thanks Raul for asking. For the moment, to get it set up, it was simplest
to just have the tag, which we can then move to a different commit upon
another release. Jacob has started pushing the CRAN maintenance branches
to the main repo (from 14.0.2 onwards) with "-cran" as the suffix, so the
Hi,
Thanks for doing this! Only one question, would there be any downside on
the R side on having the tag with a version associated so we have a
historic on the repo?
Something on the lines of "r-universe-release-15.0.0".
Maybe not relevant at the moment but if in the future we decide to have
Thanks for this Nic.
And just to clarify: the latest here is the latest _release_ of Apache
Arrow with this new set up. Prior to this the build available on R-universe
were effectively dev builds (commits to main), but with this new tag,
R-universe will only have (or at least default to having)
Hi folks,
The Arrow R package is distributed via a few different methods, one of
which is R-universe[1].
In order for r-universe to track the latest version of the R package, we
have started using the tag "r-universe-release" to indicate the commit
which represents the latest version of the R
