I have a module App::Assixt
, to which I've recently made a relatively large change. I've of course tested it on my local system, but would like to give it some field testing before calling it a "stable release".
Is there a way to "tag" this release as an "alpha", or "release-candidate", so this release will only be installed by people who have opted to use unstable/testing releases?
zef will treat versions the same as Raku:
If a
Foo:ver<1.0.PREVIEW>
is installed it can be used asFoo:ver<1.0.PREVIEW>
orFoo:ver<1.0>
. This means any systems that haveFoo:ver<1.0.PREVIEW>
installed would need to uninstall it to upgrade / installFoo:ver<1.0>
in the future ( unless using--force-install
), but also that authors can write code for the final version without declaring the extra.PREVIEW
everywhere.This is not very useful in regards to publishing -- zef will grab the newest version by default despite the user not having opted in to whatever versioning scheme is in use. Since the user wants to opt-in for this, there are two options.
1) Create e.g. unstable, testing, stable` indexes and convince people to use them
This could be done by copying the zef config to
%*ENV<XDG_CONFIG_HOME>/zef/config.json
and incorporate the following:Which allows:
2) Give out a link to the resource without publishing it