On 21/01/2021 Pedro Lino wrote:
Please let me know if it works; if it does, I will then revert it and
republish only after 4.1.9 is out ...
It is fixed indeed (although I get 2 notifications for that extension, but one
problem at a time!). Thanks!
OK, thank you for checking. I've now reverted the fix and we'll go live
with a more complete version when people will have upgraded to 4.1.9.
if an extension author submits a new version does s/he have permission to do
that manual update or s/he has to request someone to do it?
Extensions authors cannot trigger the update. Site moderators can (and
probably should) do it once in a while as a routine task. The worst
period is for sure when you are close to a release and the few weeks
after a release, since before the release you might be downloading a
newer version than the one coming with the release (like: if a bundled
extension was updated yesterday, 4.1.9 would contain an older extension
version than the one people would download today).
But when we are not in proximity of a release, we can trigger the update
perhaps once a month; fact is, the process I could find is still
cumbersome and requires shell commands to be run, so until we streamline
it it won't be run very frequently. And I would be against fully
automating it as some anti-spam checks might be needed, even though spam
is a problem on the Templates site much more than the Extensions site.
Regards,
Andrea.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
