[aur-general] Pushing rc version of package to aur

[Kevin Morris]

If 1.0.0-rc.3 is why they're flagging it out of date, perhaps you could
reply to them and explain why it's not out of date; an rc is a release
candidate, but not necessarily a true release. After rc makes its way to
a true release, that's when upstream is telling everybody that there's a
new release to update to.

imho, if folks want release candidates, a VCS package could always be
crafted. I would personally avoid releasing non-vcs rc packages.

At the end of the day; it's really up to the maintainer.

Regards,
Kevin

On Fri, Jul 30, 2021 at 06:55:45PM +0200, Jan Kohnert via aur-general wrote:
> Hi,
> 
> I maintain the gnudatalanguage package on the aur. The current release is 0.9.9 
> (from 2019); however, there is 1.0.0-rc.3 available on their webpage.
> 
> I recall having read somewhere in the docs that pushing rc version is generally 
> discouraged on the aur, but got a out-of-date flagging today.
> 
> So the question is simply: Whould it be ok to push 1.0.0-rc.3 to the aur? And if so; 
> how to specify the version tag correctly?
> 
> Thanks in advance!
> 
> -- 
> MfG Jan

-- 
Kevin Morris
Software Developer

Identities:
 - kevr @ Libera
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://lists.archlinux.org/pipermail/aur-general/attachments/20210730/3f715f47/attachment.sig>