Best practices for informing a maintainer of a new version of a package in Manjaro's repositories

[RoestVrijStaal]

Hi

I’m not sure if this topic is placed in the right category, but I’m wondering what’s the best way to inform package maintainers for new versions.

I know there is an e-mail provided, so I’m supposed to e-mail that person. But imagine the (over)flow of e-mails when a package get an update. It’s quite a time waste for me to send a mail to the maintainer when someone else already did that.

The way how the AUR addressed this, is quite elegant. Registered users just have to send a form, preferably with urls to the changelog and the new version release page.

Isn’t it an idea to do something the same? I’m thinking of opening one topic to address new releases of packages with are in the Manjaro repositories. To be clear: not a topic per package for now. Would be considerable when it will be a mess to put it in one topic.

[xabbu]

If it is really a package build by Manjaro Develeopers post in thist hread

Update requests for packages built by Manjaro developers

This thread is here to request updates for packages that are in the official repositories of Manjaro and that are built+signed by the Manjaro team. It is not meant to request updates for packages that are imported from Arch Linux repositories as it is. For such requests, please see this thread instead: Update requests for packages imported from Arch Linux. Here’s an example of a package that is build and signed by someone in the Manjaro team. [linux54] Commands that can be used to verify who …

But most packages are not build by Manjaro Develeopers. These packages are directly imported form Arch.

https://www.archlinux.org/packages/
search and use “Flag Package Out-of-Date”

Also check this post

Update requests for packages imported from Arch Linux

This thread is here to request updates for packages that are in the official repositories of Manjaro and that are imported directly from Arch Linux. These packages are not signed by anyone in the Manjaro Team, but rather signed by a maintainer of Arch Linux. Usually, updates for these packages come regularly on the Unstable branch and gradually go on the Testing, Stable-Staging and Stable branch. Sometime, there may be a good and legitimate reason why an update for a package would need to be pu…

[RoestVrijStaal]

Thanks, it seems I misinterpreted the “This section is for developers only.”-description of the Development-category.