-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Is the "Request new package" [1] now officially supported? Will there be some announcement? And will it work faster/automatically or is there still fallback to some manual action?

And I have one additional RFE. Since there is referred bugzilla ticket, I believe that you should be able to get the "package name" and "summary" from that ticket summary. This would save me from copy-pasting.


Vít


[1] https://admin.fedoraproject.org/pkgdb/request/package/



Dne 23.3.2015 v 18:57 Pierre-Yves Chibon napsal(a):
> On Thu, Mar 19, 2015 at 02:55:15PM +0100, Pierre-Yves Chibon wrote:
>> Hi all,
>>
>> I have just released and pushed to staging a new pkgdb2 release: 1.24
>> Here is the changelog for this version:
>>
>> * Thu Mar 19 2015 Pierre-Yves Chibon <pingou@pingoured.fr> - 1.24-1
>> - Fix orphaning package having a group as PoC
>> - Fix excluding provenpackager from some packages specified in the
>>   configuration
>> - Monkey patch flask.jsonify to handle JSONP responses on GET requests (Ralph
>>   Bean)
>> - Anitya integration
>> - Allow package admins to retire a package
>>
>>
>> Here below is the changelog for the versions that made it to stg but not prod
>> (giving more info about the changes that are specific to stg).
>>
>> * Fri Feb 20 2015 Pierre-Yves Chibon <pingou@pingoured.fr> - 1.23.995-1
>> - Update to 1.23.995 (pre-release of 1.24)
>> - Fix the link to `My Requests` on the API documentation page
>>
>> * Fri Feb 20 2015 Pierre-Yves Chibon <pingou@pingoured.fr> - 1.23.994-1
>> - Update to 1.23.994 (pre-release of 1.24)
>> - Do not use insecure connection to pkgdb in set_monitoring_status (Till Maas)
>> - Add documentation for the API endpoint to set the monitoring status of a
>>   package
>> - Replace the monitoring toggle button by one that might be clearer
>> - Fix actually setting the monitoring flag of new package to True (and adjust
>>   the tests for this)
>>
>> * Thu Feb 19 2015 Pierre-Yves Chibon <pingou@pingoured.fr> - 1.23.993-1
>> - Update to 1.23.993 (pre-release of 1.24)
>> - Drop the package name from the URL to edit a request (fix few bugs in the
>>   process)
>> - If requested is a package admin, request is set to Awaiting Review
>> - Use secure=True against prod pkgdb in set_monitoring_status.py (Ralph Bean)
>>
>> * Wed Feb 18 2015 Pierre-Yves Chibon <pingou@pingoured.fr> - 1.23.992-1
>> - Update to 1.23.992 (pre-release for 1.24)
>> - Add a `My Request` tab in the main menu
>> - Adjust copyright year in the master template
>> - Monitor package set as True by default (Ralph Bean)
>> - Drop the branch from field when requesting branch for a package
>> - Add the possibility to Edit one's request directly via the `My Requests` page
>> - Increase the width of the field in the form to request a new package
>>
>> * Tue Feb 17 2015 Pierre-Yves Chibon <pingou@pingoured.fr> - 1.23.991-1
>> - Update to 1.23.991 (pre-release for 1.24)
>> - Fix documentation to reflect the correct variable name
>> - Add a link to the request made by someone on the user's page (where all the
>>   packages of that person are listed)
>> - Simplify the form to request a package to be added to pkgdb
>> - Ensure we check that a group is valid before giving it some ACLs
>> - Make it easier to change one's avatar by simply clicking on it (Ralph Bean)
>> - Add a placeholder for the Review URL field when requesting a package to be
>>   added to pkgdb
>> - When giving watch* ACLs to a FAS user, check that this user exists
>> - Per FESCo decision, Fedora branch requests will have by default a 7 days
>>   period during which packager with approveacls will be allowed to grant/deny
>>   the request, this period does not apply if the requester has approveacls on
>>   the package
>>
>> * Mon Jan 26 2015 Pierre-Yves Chibon <pingou@pingoured.fr> - 1.23.99-1
>> - Update to 1.23.99 (pre-release for 1.24)
>> - New processes to request a new package or a new branch of a package directly
>>   in pkgdb instead of relying on bugzilla
>
>
> 1.24 is now running in prod.
> I have had to adjust some permissions at the DB level and hopefully I got them
> all, but please do report if you run into an error 500.
>
> Thanks,
> Pierre
>
>
> _______________________________________________
> infrastructure mailing list
> infrastructure@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/infrastructure


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJVERAsAAoJEAzgnueZF7h89hsP/RX3yxQblWr22Zmen0w5DXC3
tBpW60946QdDzUq2pLbRqq9rM3iqQiFsjbX4QzxXT8JXlwQO8kqjGNHwQlzuXLUW
lX9B2J8RYnOPP9krDX3Y4MRZmhV4jL4lIZjXgAwCyrxH0avJZk2tykpIcgzgeXY+
HRuZ//r49FLXQ04ihMZfe5aN15Fqwp8caaZ0Q1QKS9Rqb9u0jRZPaWq74c/NSxvg
N68bxaab2wxtGlZkt6CfakQkHybLyZ54uVK/CG2ulnuM0x59eTmHdCh/Hrlnscje
rMinRSCdD1j+vn3dTZZmjIwcRla6F8H6KDa9vpuAEy/56zDTE4vYJuoJsusn2Dc8
GIlLC5YLXYSirBUmO9qh8IjywepvSaHN1JbiFj7Hb/vLDcBGHHcEOqPrQddEJE2x
TkEcvtIIxl2OV+8Q2cIerdmcddKHFpeO+zX7lmfVUqjWFvjgn2/m73nOwXlhytFK
T5rnAPHyONzjkecl61jdFh+1rBodbn+xQqkdCKT4nGhmhI9DvCAVcLBliVpd49Nm
QLFP47FZewJV+eUYwSpyO1LP45W3iMUY9RTazgRR+6OiJTJIgiZOnIR4Sj7/heax
TZm66TGcRe9rzNk/uZ32uqBE8jXF9q1Bu39Qsz8YaipKbc19GEcynPiNIkHDjB16
6dGsoXWxS3D5PFeGUlvz
=RqWk
-----END PGP SIGNATURE-----