Bug 1266336
Summary: | Review Request: Mass review exception : php-zendframework | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Remi Collet <fedora> |
Component: | Package Review | Assignee: | Nobody's working on this, feel free to take it <nobody> |
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | j, package-review, panemade, siwinski |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-10-01 02:01:02 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Remi Collet
2015-09-25 05:09:00 UTC
New Package SCM Request ======================= Package Name: ** see above list ** Short Description: Zend Framework Upstream URL: http://framework.zend.com/ Owners: remi siwinski Branches: f23 InitialCC: Packages list: php-zendframework php-zendframework-zend-authentication php-zendframework-zend-barcode php-zendframework-zend-cache php-zendframework-zend-captcha php-zendframework-zend-code php-zendframework-zend-config php-zendframework-zend-console php-zendframework-zend-crypt php-zendframework-zend-db php-zendframework-zend-debug php-zendframework-zend-di php-zendframework-zend-dom php-zendframework-zend-escaper php-zendframework-zend-eventmanager php-zendframework-zend-feed php-zendframework-zend-file php-zendframework-zend-filter php-zendframework-zend-form php-zendframework-zend-http php-zendframework-zend-i18n php-zendframework-zend-i18n-resources php-zendframework-zend-inputfilter php-zendframework-zend-json php-zendframework-zend-ldap php-zendframework-zend-loader php-zendframework-zend-log php-zendframework-zend-mail php-zendframework-zend-math php-zendframework-zend-memory php-zendframework-zend-mime php-zendframework-zend-modulemanager php-zendframework-zend-mvc php-zendframework-zend-navigation php-zendframework-zend-paginator php-zendframework-zend-permissions-acl php-zendframework-zend-permissions-rbac php-zendframework-zend-progressbar php-zendframework-zend-serializer php-zendframework-zend-server php-zendframework-zend-servicemanager php-zendframework-zend-session php-zendframework-zend-soap php-zendframework-zend-stdlib php-zendframework-zend-tag php-zendframework-zend-test php-zendframework-zend-text php-zendframework-zend-uri php-zendframework-zend-validator php-zendframework-zend-version php-zendframework-zend-view php-zendframework-zendxml php-zendframework-zend-xmlrpc WARNING: Ticket is not assigned to anyone. WARNING: fedora-review flag not set WARNING: Requested package name ** see above list ** doesn't match bug summary Mass I just wonder is there any guidelines on how to request SCM here for such mass review requests? Can it be added on https://fedoraproject.org/wiki/Package_SCM_admin_requests page? Not sure if git-process-requests script is capable of handling such requests. Why for such requests a common Sort Description is used? or are we relying here on pkgdb_updater script to correct the package description here? (In reply to Parag AN(पराग) from comment #3) > Not sure if git-process-requests script is capable of handling such requests. I just give the list of packages, as asked by tibbs. > Why for such requests a common Sort Description is used? or are we relying > here on pkgdb_updater script to correct the package description here? Correct description is "Zend Framework xxx component" But yes, I think we can rely on pkgdb_updater script. Cool. Thanks Remi. I am just trying to understand here how this new way of mass review exception process will be working here. This is the first one, so process needs to be worked out since there aren't really existing tools. It's kind of early to ask for it to be written down. Of course, the rest of the process is already documented. For now I just asked Remi to file the ticket he filed so that I can work through the process and if this works then I can just codify what he's done. OK, that's finished. Had to find enough time to write the tool to create everything and after a fashion it actually worked. Though somehow it actually added me to one of the packages. In any case, this seemed to work well enough. @tibbs thanks All packages built in rawhide. |