March 2013 - qa-devel - Fedora mailing-lists

[Fedora QA] #367: Display flash messages in appropriate place
by fedora-badges 03 Jul '13

03 Jul '13

#367: Display flash messages in appropriate place --------------------------------------+---------------------------------- Reporter: mkrizek | Owner: tflink Type: enhancement | Status: new Priority: minor | Milestone: Undetermined Future Component: Blocker bug tracker page | Version: Keywords: | Blocked By: Blocking: | --------------------------------------+---------------------------------- = problem = Currently flash messages containing information for user are not displayed. = analysis = There should probably be a box right under the header on all pages that would display flash messages. = enhancement recommendation = -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/367> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 2

[Fedora QA] #372: Bugzilla Faults During Proposal are not logged, lead to http 500 errors
by fedora-badges 25 Jun '13

25 Jun '13

#372: Bugzilla Faults During Proposal are not logged, lead to http 500 errors --------------------------------------+------------------------ Reporter: tflink | Owner: tflink Type: defect | Status: new Priority: critical | Milestone: Fedora 19 Component: Blocker bug tracker page | Version: Keywords: | Blocked By: Blocking: | --------------------------------------+------------------------ = bug description = When bugzilla faults during proposal don't have fault code 51, the internal !BugzillaError class isn't used and the fault is lost when attempting to extract information from it {{{ [Wed Mar 27 13:26:38 2013] [error] [20130327-13:26PM] [blockerbugs] [ERROR] Exception on /propose_bug [POST] [Wed Mar 27 13:26:38 2013] [error] Traceback (most recent call last): [Wed Mar 27 13:26:38 2013] [error] File "/usr/lib/python2.6/site- packages/flask/app.py", line 1687, in wsgi_app [Wed Mar 27 13:26:38 2013] [error] response = self.full_dispatch_request() [Wed Mar 27 13:26:38 2013] [error] File "/usr/lib/python2.6/site- packages/flask/app.py", line 1360, in full_dispatch_request [Wed Mar 27 13:26:38 2013] [error] rv = self.handle_user_exception(e) [Wed Mar 27 13:26:38 2013] [error] File "/usr/lib/python2.6/site- packages/flask/app.py", line 1358, in full_dispatch_request [Wed Mar 27 13:26:38 2013] [error] rv = self.dispatch_request() [Wed Mar 27 13:26:38 2013] [error] File "/usr/lib/python2.6/site- packages/flask/app.py", line 1344, in dispatch_request [Wed Mar 27 13:26:38 2013] [error] return self.view_functions[rule.endpoint](**req.view_args) [Wed Mar 27 13:26:38 2013] [error] File "/usr/lib/python2.6/site- packages/blockerbugs/controllers/users.py", line 84, in decorated_function [Wed Mar 27 13:26:38 2013] [error] return f(*args, **kwargs) [Wed Mar 27 13:26:38 2013] [error] File "/usr/lib/python2.6/site- packages/blockerbugs/controllers/main.py", line 375, in propose_bug [Wed Mar 27 13:26:38 2013] [error] bugform.bugid.errors = [e.msg] [Wed Mar 27 13:26:38 2013] [error] AttributeError: 'Fault' object has no attribute 'msg' }}} = fix recommendation = Either all of the bugzilla faults need to be wrapped in a !BugzillaError or the error handling needs to be capable of handling multiple error types. -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/372> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 1

[Fedora QA] #370: Change active milestone list on index to clickable links
by fedora-badges 01 May '13

01 May '13

#370: Change active milestone list on index to clickable links --------------------------------------+---------------------------------- Reporter: tflink | Owner: tflink Type: enhancement | Status: new Priority: minor | Milestone: Undetermined Future Component: Blocker bug tracker page | Version: Keywords: easyfix | Blocked By: Blocking: | --------------------------------------+---------------------------------- = problem = Currently, the milestones listed as current on the index are not links. It would be nice if they linked to the milestone's buglist = enhancement recommendation = Change the index template such that the list of currently active milestones also links to the named milestone's buglist -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/370> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 1

[Fedora QA] #369: Logo in Upper Left Corner Should be a Link to Main Index
by fedora-badges 30 Apr '13

30 Apr '13

#369: Logo in Upper Left Corner Should be a Link to Main Index --------------------------------------+---------------------------------- Reporter: tflink | Owner: tflink Type: enhancement | Status: new Priority: minor | Milestone: Undetermined Future Component: Blocker bug tracker page | Version: Keywords: easyfix | Blocked By: Blocking: | --------------------------------------+---------------------------------- = problem = Many websites have the logo in the upper left hand corner as a link to the index. The blocker tracking app does not. = enhancement recommendation = Modify the base template such that the logo is a clickable link going to the main index -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/369> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 1

Review Request 18: Add cgit link to Main Page
by Martin Krizek 23 Apr '13

23 Apr '13

----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://reviewboard-tflink.rhcloud.com/r/18/ ----------------------------------------------------------- Review request for blockerbugs. Bugs: 343 https://fedorahosted.org/fedora-qa/ticket/343 Repository: blockerbugs Description ------- This is maybe trivial to have a review for but two things might be discussed: 1. do we want to show the link just on index or on all pages? 2. is the wording of the link ok? Diffs ----- sass/app.scss 1a4369d0911b77fc411089de0b05c8d5c80e304f blockerbugs/templates/index.html 088962bfcb16c3f0d163366f2235fc557e0d45dc Diff: http://reviewboard-tflink.rhcloud.com/r/18/diff/ Testing ------- Thanks, Martin Krizek

1 5

[Fedora QA] #373: Remove Mockup Warning from proposal thank you page
by fedora-badges 22 Apr '13

22 Apr '13

#373: Remove Mockup Warning from proposal thank you page --------------------------------------+------------------------ Reporter: tflink | Owner: tflink Type: defect | Status: new Priority: major | Milestone: Fedora 19 Component: Blocker bug tracker page | Version: Keywords: | Blocked By: Blocking: | --------------------------------------+------------------------ = bug description = The 'thank you' page after blocker proposal still contains a warning about being a mockup. = fix recommendation = Remove the warning from that template page; it shouldn't be there any more. -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/373> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 1

[Fedora QA] #374: Rework Logging Mechanisms
by fedora-badges 19 Apr '13

19 Apr '13

#374: Rework Logging Mechanisms --------------------------------------+------------------------ Reporter: tflink | Owner: tflink Type: enhancement | Status: new Priority: major | Milestone: Fedora 19 Component: Blocker bug tracker page | Version: Keywords: | Blocked By: Blocking: | --------------------------------------+------------------------ = problem = The logs for both the blocker tracking app and the sync operation are limited to stdout only instead of being separated out into a file. = analysis = The biggest problem here is recording what happens with sync - we used to deal with it by piping the output into a file but with the shift to RPM packaging and hosting in fedora infra, this is no longer an option. The log messages during normal app use go to httpd's error_log but that isn't as big of a problem. This bug will serve as a tracker bug for all the functionality which needs to be done in order to properly log output from sync and the blocker tracking app. -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/374> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 3

[Fedora QA] #377: Add log location to spec
by fedora-badges 19 Apr '13

19 Apr '13

#377: Add log location to spec --------------------------------------+------------------------ Reporter: tflink | Owner: tflink Type: enhancement | Status: new Priority: major | Milestone: Fedora 19 Component: Blocker bug tracker page | Version: Keywords: | Blocked By: Blocking: 374 | --------------------------------------+------------------------ = problem = Once logging has been implemented for sync and the blocker tracking application, that location will need to be created at install time for production systems. = enhancement recommendation = The spec file currently has no concept of the logging location - once the production location has been determined, create that dir in the spec and claim ownership of it. -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/377> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 2

[Fedora QA] #376: Change logging config for app
by fedora-badges 19 Apr '13

19 Apr '13

#376: Change logging config for app --------------------------------------+--------------------- Reporter: tflink | Owner: tflink Type: enhancement | Status: new Priority: minor | Milestone: Component: Blocker bug tracker page | Version: Keywords: | Blocked By: Blocking: 374 | --------------------------------------+--------------------- = problem = The error messages from the app are only sent to stdout instead of being directed to a log file. While this isn't a huge problem (everything will be caught by httpd's error_log), it is not the best solution. = enhancement recommendation = change the logging setup so that the location is configurable (stdout, file) and that both file and stdout could be used at the same time. -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/376> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 3

[Fedora QA] #375: Change logging config for sync
by fedora-badges 19 Apr '13

19 Apr '13

#375: Change logging config for sync --------------------------------------+------------------------ Reporter: tflink | Owner: tflink Type: enhancement | Status: new Priority: major | Milestone: Fedora 19 Component: Blocker bug tracker page | Version: Keywords: | Blocked By: Blocking: 374 | --------------------------------------+------------------------ = problem = The sync process uses a different logging instance than the blocker tracking app and is currently configured to just output to stdout instead of logging to a file. = enhancement recommendation = The sync should log to a file while in production but shouldn't force logging to a static location. The log location should be configurable (stdout, specific file) and it should be separable from app logging. -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/375> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 3

[Fedora QA] #378: Syncing is stuck
by fedora-badges 11 Apr '13

11 Apr '13

#378: Syncing is stuck --------------------------------------+--------------------- Reporter: kparal | Owner: tflink Type: defect | Status: new Priority: blocker | Milestone: Component: Blocker bug tracker page | Version: Keywords: | Blocked By: Blocking: | --------------------------------------+--------------------- https://qa.stg.fedoraproject.org/blockerbugs/milestone/19/alpha/buglist " This page was last synced with Red Hat Bugzilla at 2013-03-26 20:46:40 UTC. " But http://qa.fedoraproject.org/blockerbugs/milestone/19/alpha/buglist seems to sync well. -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/378> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 2

[Fedora QA] #371: HTTP 500 after proposing a blocker bug
by fedora-badges 27 Mar '13

27 Mar '13

#371: HTTP 500 after proposing a blocker bug --------------------------------------+--------------------- Reporter: kparal | Owner: tflink Type: defect | Status: new Priority: major | Milestone: Component: Blocker bug tracker page | Version: Keywords: | Blocked By: Blocking: | --------------------------------------+--------------------- I tried to propose https://bugzilla.redhat.com/show_bug.cgi?id=928339 as an alpha blocker and I got HTTP 500 after submitting the form. The bug was not proposed. -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/371> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 2

New and Improved Blocker Tracking App Beta
by Tim Flink 27 Mar '13

27 Mar '13

This took a bit longer than I was hoping but we finally have a staging instance of the new blocker tracking app up and running: https://qa.stg.fedoraproject.org/blockerbugs/ There are still a few kinks to work out around syncing with bugzilla and on the app administration side of things but it is ready for testing. This new version allows for blocker/FE proposal though the web interface after logging in with your FAS id and password. The first proposal will prompt you for your bugzilla credentials so that you will be added to the cc list of any bug you propose but this will only happen once (per database - this will be reset when the app moves to production) and we don't store any password information. Keep in mind that this is working against the PRODUCTION bugzilla for now - any bugs which are proposed using the web interface will show up as real blockers. Please don't propose blocker/FE bugs just to try it out. Once partner-bugzilla is back up and running, the staging instance will be more testable without affecting the regular processes. If you hit any issues, please let me know or file a bug against the blocker tracking app in the fedora-qa trac: - https://fedorahosted.org/fedora-qa/newticket Huge 'Thank You's to Martin Krizek for his help on the code, reviews and testing and to Kevin Fenzi for his help and patience in getting the app ready for staging deployment. Tim

3 3

[Fedora QA] #368: "Propose" bug page leads to Internal Server Error
by fedora-badges 26 Mar '13

26 Mar '13

#368: "Propose" bug page leads to Internal Server Error --------------------------------------+--------------------- Reporter: jreznik | Owner: tflink Type: defect | Status: new Priority: major | Milestone: Component: Blocker bug tracker page | Version: Keywords: | Blocked By: Blocking: | --------------------------------------+--------------------- https://qa.stg.fedoraproject.org/blockerbugs/propose_bug responds with 500 Internal Server Error after login. -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/368> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 1

Review Request 16: Initial Packaging Work
by Martin Krizek 25 Mar '13

25 Mar '13

----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://reviewboard-tflink.rhcloud.com/r/16/ ----------------------------------------------------------- Review request for blockerbugs. Bugs: 337 https://fedorahosted.org/fedora-qa/ticket/337 Repository: blockerbugs Description ------- Initial packaging work and reworking all the various cli scripts into a single module to make it more packaging friendly Diffs ----- update_blockers.sh d5229ea9b54119608e73cabcabbaaf4d99248876 sync_db.py 3489434c9cd6dc4f67ad82f61b171f94c4d65793 setup.py b4a51dc9c4bb9dadbd5ada286b8ddd5448811886 run_cli.py PRE-CREATION initialize.py eb3c3e160e66f5f044e20f53ff79994820fd4a7e init_db.sh 540dcb1f4baff9d7d0cad0dc75d67a4d6f3c3a98 docs/source/installation.rst PRE-CREATION docs/source/index.rst PRE-CREATION docs/source/development.rst PRE-CREATION docs/source/conf.py PRE-CREATION docs/Makefile PRE-CREATION doc/source/installation.rst 41319a6c345987bf50663ae4ff88068aed81334c doc/source/index.rst f07f013268aaa01cec780efec6e320c6cb267339 doc/source/development.rst 35b1b34a6b81d8d35e91fb11d32b35dc5d8269a9 doc/source/conf.py fc14e55effbd22e0c2b4fef5c7a395d16f0a5f70 doc/Makefile 8c16a97606680359188461c22ef48777b5ee9ee0 blockerbugs/cli.py PRE-CREATION blockerbugs/__init__.py 9030c04ee244ce21439075be9c446a83c05ed9ae blockerbugs.spec PRE-CREATION alembic.ini 848a3873008f231b03c12c4bcfe6d7367527f8fc Diff: http://reviewboard-tflink.rhcloud.com/r/16/diff/ Testing ------- I've done a bunch of local testing and have a staging instance set up in the cloud: https://209.132.184.164/blockerbugs/ Thanks, Tim Flink

1 4

Review Request 17: Implement Bugzilla Account Association
by Martin Krizek 15 Mar '13

15 Mar '13

----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://reviewboard-tflink.rhcloud.com/r/17/ ----------------------------------------------------------- Review request for blockerbugs. Bugs: 347 https://fedorahosted.org/fedora-qa/ticket/347 Repository: blockerbugs Description ------- This is a patch for tickets 347, 348, 349 and 350. Diffs ----- testing/test_bugchange.py 65f291122b4ae687872170517d196a621d548152 blockerbugs/util/bz_interface.py a8958be674e839d6c99694e33440a26331a8b041 blockerbugs/templates/propose_bug.html c97d72303dff2f49e4bb8bc5ff5fc2f4c764ce8b blockerbugs/templates/login.html 20674fe93eb96c6e1e9b12b5988cad67dc1a5181 blockerbugs/templates/layout.html 6d0ae9a7bc913aa408985028db4494d51379da9c blockerbugs/templates/fas_bugzilla.html PRE-CREATION blockerbugs/templates/base_nav.html ce7a7bb478ad57a65d646fa7326a210c6a4eb131 blockerbugs/models/userinfo.py PRE-CREATION blockerbugs/controllers/users.py 30b5fb5c8ef2196979a2d22c4380f302a5ce951a blockerbugs/controllers/main.py ce26c641b9db05f11510f16177b017a56cf757c2 blockerbugs/controllers/forms.py b213c055d9297b59c6cf5d83358dcd14e265e345 alembic/versions/1d12b74d12bd_add_userinfo_table.py PRE-CREATION Diff: http://reviewboard-tflink.rhcloud.com/r/17/diff/ Testing ------- Thanks, Martin Krizek

1 5

Re: [Fedora QA] #347: Implement Bugzilla Account Association
by fedora-badges 15 Mar '13

15 Mar '13

#347: Implement Bugzilla Account Association ---------------------------------------+----------------------- Reporter: tflink | Owner: mkrizek Type: enhancement | Status: closed Priority: major | Milestone: Fedora 19 Component: Blocker bug tracker page | Version: Resolution: fixed | Keywords: Blocked By: 348, 349, 350 | Blocking: ---------------------------------------+----------------------- Changes (by mkrizek): * status: new => closed * resolution: => fixed Comment: Fixed in [http://git.fedorahosted.org/cgit/blockerbugs.git/commit/?h=develop&id=4ffd2… 4ffd2dd5700cab8c676ce794720f1e9a5edeb485] -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/347#comment:5> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 0

Re: [Fedora QA] #350: Integrate Bugzilla Email Association with Blocker Proposal
by fedora-badges 15 Mar '13

15 Mar '13

#350: Integrate Bugzilla Email Association with Blocker Proposal ---------------------------------------+----------------------- Reporter: tflink | Owner: mkrizek Type: enhancement | Status: closed Priority: major | Milestone: Fedora 19 Component: Blocker bug tracker page | Version: Resolution: fixed | Keywords: Blocked By: | Blocking: 347 ---------------------------------------+----------------------- Changes (by mkrizek): * status: new => closed * resolution: => fixed Comment: Fixed in [http://git.fedorahosted.org/cgit/blockerbugs.git/commit/?h=develop&id=4ffd2… 4ffd2dd5700cab8c676ce794720f1e9a5edeb485] -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/350#comment:2> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 0

Re: [Fedora QA] #349: Implement Bugzilla Email Verification
by fedora-badges 15 Mar '13

15 Mar '13

#349: Implement Bugzilla Email Verification ---------------------------------------+----------------------- Reporter: tflink | Owner: mkrizek Type: enhancement | Status: closed Priority: major | Milestone: Fedora 19 Component: Blocker bug tracker page | Version: Resolution: fixed | Keywords: Blocked By: | Blocking: 347 ---------------------------------------+----------------------- Changes (by mkrizek): * status: new => closed * resolution: => fixed Comment: Fixed in [http://git.fedorahosted.org/cgit/blockerbugs.git/commit/?h=develop&id=4ffd2… 4ffd2dd5700cab8c676ce794720f1e9a5edeb485] -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/349#comment:2> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 0

Re: [Fedora QA] #348: Store Bugzilla Email Association in Database
by fedora-badges 15 Mar '13

15 Mar '13

#348: Store Bugzilla Email Association in Database ---------------------------------------+----------------------- Reporter: tflink | Owner: mkrizek Type: enhancement | Status: closed Priority: major | Milestone: Fedora 19 Component: Blocker bug tracker page | Version: Resolution: fixed | Keywords: Blocked By: | Blocking: 347 ---------------------------------------+----------------------- Changes (by mkrizek): * status: new => closed * resolution: => fixed Comment: Fixed in [http://git.fedorahosted.org/cgit/blockerbugs.git/commit/?h=develop&id=4ffd2… 4ffd2dd5700cab8c676ce794720f1e9a5edeb485] -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/348#comment:3> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 0

AutoQA Going Down for Updates
by Tim Flink 14 Mar '13

14 Mar '13

The physical machine which hosts autoqa.fp.o and autoqa-stg.fp.o is going down for maintenance and thus, autoqa will be down for a little while. I'm starting to stop new jobs and will be bringing the hosts down shortly. I'll send out an update when things are back up. Tim

1 1

Re: [Fedora QA] #343: Add cgit link to Main Page
by fedora-badges 13 Mar '13

13 Mar '13

#343: Add cgit link to Main Page ---------------------------------------+----------------------- Reporter: tflink | Owner: mkrizek Type: enhancement | Status: new Priority: trivial | Milestone: Fedora 19 Component: Blocker bug tracker page | Version: Resolution: | Keywords: Blocked By: | Blocking: ---------------------------------------+----------------------- Changes (by mkrizek): * cc: qa-devel@… (added) * owner: tflink => mkrizek -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/343#comment:1> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 0

[AutoQA] #437: Update repoinfo.conf - Add branch
by fedora-badges 12 Mar '13

12 Mar '13

#437: Update repoinfo.conf - Add branch -------------------------+------------------------ Reporter: ausil | Owner: Type: task | Status: new Priority: critical | Milestone: Hot issues Component: production | Keywords: Blocked By: | Blocking: -------------------------+------------------------ we have just branched for f19 -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/437> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 2

[AutoQA] #436: ghc Haskell library packages should not be tested multilib
by fedora-badges 12 Mar '13

12 Mar '13

#436: ghc Haskell library packages should not be tested multilib -----------------------+---------------------- Reporter: petersen | Owner: Type: defect | Status: new Priority: major | Milestone: Depcheck Component: core | Keywords: Blocked By: | Blocking: -----------------------+---------------------- AutoQA seems to think that ghc-* packages on x86_64 are multilib but multilib is not supported for ghc and mash is no longer composing ghc-* multilib: AutoQA should only test ghc-*.x86_64 on x86_64. See eg: https://admin.fedoraproject.org/updates/search/ghc-wai-logger but this happens for every ghc-* library update or new package in Bodhi. {{{ autoqa - 2013-02-19 06:18:21 AutoQA: depcheck test FAILED on x86_64. Result log: http://autoqa.fedoraproject.org/report/okgi (results are informative only) }}} {{{ autoqa - 2013-02-19 06:17:23 AutoQA: depcheck test FAILED on x86_64. Result log: http://autoqa.fedoraproject.org/report/okge (results are informative only) }}} which makes it look like ghc x86_64 packages are always broken on x86_64. -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/436> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 1

Re: [Fedora QA] #350: Integrate Bugzilla Email Association with Blocker Proposal
by fedora-badges 11 Mar '13

11 Mar '13

#350: Integrate Bugzilla Email Association with Blocker Proposal ---------------------------------------+----------------------- Reporter: tflink | Owner: mkrizek Type: enhancement | Status: new Priority: major | Milestone: Fedora 19 Component: Blocker bug tracker page | Version: Resolution: | Keywords: Blocked By: | Blocking: 347 ---------------------------------------+----------------------- Changes (by mkrizek): * owner: tflink => mkrizek * cc: qa-devel@… (added) -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/350#comment:1> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 0

Re: [Fedora QA] #349: Implement Bugzilla Email Verification
by fedora-badges 11 Mar '13

11 Mar '13

#349: Implement Bugzilla Email Verification ---------------------------------------+----------------------- Reporter: tflink | Owner: mkrizek Type: enhancement | Status: new Priority: major | Milestone: Fedora 19 Component: Blocker bug tracker page | Version: Resolution: | Keywords: Blocked By: | Blocking: 347 ---------------------------------------+----------------------- Changes (by mkrizek): * owner: tflink => mkrizek * cc: qa-devel@… (added) -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/349#comment:1> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 0

Re: [Fedora QA] #348: Store Bugzilla Email Association in Database
by fedora-badges 11 Mar '13

11 Mar '13

#348: Store Bugzilla Email Association in Database ---------------------------------------+----------------------- Reporter: tflink | Owner: mkrizek Type: enhancement | Status: new Priority: major | Milestone: Fedora 19 Component: Blocker bug tracker page | Version: Resolution: | Keywords: Blocked By: | Blocking: 347 ---------------------------------------+----------------------- Changes (by mkrizek): * owner: tflink => mkrizek * cc: qa-devel@… (added) -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/348#comment:2> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 0

Re: [Fedora QA] #347: Implement Bugzilla Account Association
by fedora-badges 11 Mar '13

11 Mar '13

#347: Implement Bugzilla Account Association ---------------------------------------+----------------------- Reporter: tflink | Owner: mkrizek Type: enhancement | Status: new Priority: major | Milestone: Fedora 19 Component: Blocker bug tracker page | Version: Resolution: | Keywords: Blocked By: | Blocking: ---------------------------------------+----------------------- Changes (by mkrizek): * cc: qa-devel@… (added) * owner: tflink => mkrizek -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/347#comment:1> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 0

Re: [Fedora QA] #330: Blocker Components are not updated when bug is reassigned
by fedora-badges 08 Mar '13

08 Mar '13

#330: Blocker Components are not updated when bug is reassigned ---------------------------------------+----------------------- Reporter: tflink | Owner: mkrizek Type: defect | Status: closed Priority: major | Milestone: Fedora 19 Component: Blocker bug tracker page | Version: Resolution: fixed | Keywords: Blocked By: | Blocking: ---------------------------------------+----------------------- Changes (by tflink): * resolution: => fixed * cc: qa-devel@… (added) * status: new => closed Comment: Replying to [comment:2 tflink]: > We think this was fixed with the field length changes from #325 but this needs to be confirmed before the ticket is closed. I've tested this with the current devel version and component changes do trigger an update in the relevant database fields. Please re-open the ticket if this issue re-appears -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/330#comment:3> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 0

Re: [Fedora QA] #314: Bug summaries are not updated
by fedora-badges 08 Mar '13

08 Mar '13

#314: Bug summaries are not updated ---------------------------------------+----------------------- Reporter: kparal | Owner: tflink Type: defect | Status: closed Priority: major | Milestone: Fedora 19 Component: Blocker bug tracker page | Version: Resolution: fixed | Keywords: Blocked By: | Blocking: ---------------------------------------+----------------------- Changes (by tflink): * cc: qa-devel@… (added) * resolution: => fixed * status: reopened => closed Comment: I have been unable to reproduce this in the current devel version of the blocker tracking app. It looks like the query was changed to detect summary changes and this bug wasn't updated - closing now. -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/314#comment:7> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 0

[Fedora QA] #362: Test day Request for 6/6/13
by fedora-badges 08 Mar '13

08 Mar '13

#362: Test day Request for 6/6/13 --------------------------------------+--------------------- Reporter: dpal | Owner: tflink Type: defect | Status: new Priority: major | Milestone: Component: Blocker bug tracker page | Version: Keywords: | Blocked By: Blocking: | --------------------------------------+--------------------- We would like to request a test day on 6/6/13 for the following feature: FreeIPA Two Factor Authentication https://fedoraproject.org/wiki/Features/FreeIPA_Two_Factor_Authentication -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/362> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 2

Re: [Fedora QA] #334: Implement Blocker/FE Proposal Page
by fedora-badges 05 Mar '13

05 Mar '13

#334: Implement Blocker/FE Proposal Page ---------------------------------------+----------------------- Reporter: tflink | Owner: tflink Type: enhancement | Status: closed Priority: major | Milestone: Fedora 19 Component: Blocker bug tracker page | Version: Resolution: fixed | Keywords: Blocked By: | Blocking: ---------------------------------------+----------------------- Changes (by tflink): * cc: qa-devel@… (added) * status: new => closed * resolution: => fixed Comment: Code reviewed and merged with develop: 506139dca38ae931e34be9f17cb2f4605d61293f -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/334#comment:1> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 0

Re: Review Request 2: Initial Blocker Review Code
by Martin Krizek 05 Mar '13

05 Mar '13

----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://reviewboard-tflink.rhcloud.com/r/2/ ----------------------------------------------------------- (Updated March 1, 2013, 6:10 a.m.) Review request for blockerbugs. Changes ------- I've updated the diff with the current changes to the blocker proposal code. There are still some minor issues (mostly with the delay when submitting a blocker and the lack of user integration with bugzilla) but it does work. The diff is slightly broken (see post to qa-devel@ as to why) but the major parts seem to be working. You can see the broken parts of the diff if you download the file or look @ git. Bugs: 334 https://fedorahosted.org/fedora-qa/ticket/334 Repository: blockerbugs Description ------- Initial code for blocker submission page Diffs (updated) ----- testing/test_bugchange.py PRE-CREATION sync_db.py 590d80adbf86bc9f7c27a4a8a0d46f5570c303f1 setup.py 32cf5b26caac1aced1dde2f0bf29d94bc2bebe83 initialize.py a6cd0a2766aaf88e8d87a4f72d6721075f6a219d init_f18db.sh c20df66c4b4a8f38ab79a1b61043d26de112f71c conf/blockerbugs.wsgi dcd819f4c4080546c84bd48f604ae6469d70d98a blockerbugs/util/bz_interface.py 2bae79db2d3a1206b7de1cee5f005f137ba2d6f3 blockerbugs/util/bug_sync.py 110fbe983a5cf177c35a9966162d0de23cf98d18 blockerbugs/templates/thanks.html PRE-CREATION blockerbugs/templates/propose_bug.html PRE-CREATION blockerbugs/templates/base_nav.html f3a89798a9dadf297e722c067ad3795a72ebbf74 blockerbugs/controllers/main.py 21bf27ce593a1398b1a08a6a4bcfc1d34146c027 blockerbugs/controllers/forms.py caae0e5b201fc6d85930246c31159ebbbe4f9ab7 blockerbugs/controllers/admin.py 01196b3d9b7284ebcab8bf1db061ad69f2d5f250 blockerbugs/config.py 75cf777d31e7fc3bfe3256704cd349e3ca88c866 blockerbugs/__init__.py cae54ab562f8a17a4473aa0bc58a73dacf5225f9 Diff: http://reviewboard-tflink.rhcloud.com/r/2/diff/ Testing (updated) ------- I've done quite a bit of local testing and there is a staging instance available: https://209.132.184.132/blockerbugs Thanks, Tim Flink

1 6

Problems with code reviews on reviewboard
by Tim Flink 04 Mar '13

04 Mar '13

Recently, we've been having some issues with code reviews on the reviewboard instance I set up. Petr was not able to create a review for a fedora-build-service patch and a review I set up is showing diff errors. I started digging into this yesterday, and it turns out to be a problem with the fedorahosted cgit instance that reviewboard uses to get files to generate the diffs - it's not returning the right file contents. In some cases, it returns blank files. In other cases, it returns 404 errors (what petr was hitting) or HEAD from MASTER instead of the file requested (what I was hitting). After talking with nirik in #fedora-admin, it looks like this might be an issue with the fedorahosted.org setup of cgit because while I can reproduce the issue on freedesktop.org's cgit instance (which is probably using the same redirects), I can't reproduce the problem on the upstream cgit instance [1]. [1] http://git.zx2c4.com/cgit/ I've filed an issue with infra [2] and will update this thread when we know more. However, until this is resolved - code reviews on reviewboard aren't likely to work 100%. [2] https://fedorahosted.org/fedora-infrastructure/ticket/3687 Tim

1 1

Re: [Fedora QA] #318: track blockers closed as duplicates to non-blockers
by fedora-badges 04 Mar '13

04 Mar '13

#318: track blockers closed as duplicates to non-blockers ---------------------------------------+--------------------------------- Reporter: kparal | Owner: tflink Type: enhancement | Status: new Priority: major | Milestone: Undetermined Future Component: Blocker bug tracker page | Version: Resolution: | Keywords: Blocked By: | Blocking: ---------------------------------------+--------------------------------- Changes (by tflink): * milestone: => Undetermined Future * cc: qa-devel@… (added) -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/318#comment:1> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 0

Re: [Fedora QA] #323: Add API support to the blocker tracking app
by fedora-badges 04 Mar '13

04 Mar '13

#323: Add API support to the blocker tracking app ---------------------------------------+--------------------------------- Reporter: tflink | Owner: tflink Type: enhancement | Status: new Priority: minor | Milestone: Undetermined Future Component: Blocker bug tracker page | Version: Resolution: | Keywords: Blocked By: | Blocking: ---------------------------------------+--------------------------------- Changes (by tflink): * cc: qa-devel@… (added) * milestone: => Undetermined Future -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/323#comment:1> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 0

Re: [Fedora QA] #356: Blocker Proposal is Slow
by fedora-badges 04 Mar '13

04 Mar '13

#356: Blocker Proposal is Slow ---------------------------------------+--------------------------------- Reporter: tflink | Owner: tflink Type: enhancement | Status: new Priority: major | Milestone: Undetermined Future Component: Blocker bug tracker page | Version: Resolution: | Keywords: Blocked By: | Blocking: ---------------------------------------+--------------------------------- Changes (by tflink): * milestone: Fedora 19 => Undetermined Future * cc: qa-devel@… (added) Comment: I did some digging into this and I don't think it's practical to plan on this for Fedora 19. It would be great but the blocker tracking app wouldn't be the only Fedora-related app that has some slow postings and I think our resources could be better spent elsewhere for now. -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/356#comment:1> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 0

Re: [fedora-build-service] #10: image_builder doesn't clean up after itself
by fedora-badges 01 Mar '13

01 Mar '13

#10: image_builder doesn't clean up after itself -----------------------------+-------------------------------- Reporter: tflink | Owner: pschindl Type: defect | Status: accepted Priority: major | Milestone: Initial Deployment Component: Image Building | Version: Resolution: | Keywords: -----------------------------+-------------------------------- Changes (by pschindl): * status: new => accepted * owner: somebody => pschindl -- Ticket URL: <https://fedorahosted.org/fedora-build-service/ticket/10#comment:1> fedora-build-service <https://fedorahosted.org/fedora-build-service> A service to build fedora images with a somewhat arbitrary package set from the standard fedora repos or builds from koji.

1 0

Re: Review Request 8: Add Fedora 19 Milestones
by Martin Krizek 01 Mar '13

01 Mar '13

----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://reviewboard-tflink.rhcloud.com/r/8/ ----------------------------------------------------------- (Updated March 1, 2013, 10:09 a.m.) Status ------ This change has been marked as submitted. Review request for blockerbugs. Bugs: 332 https://fedorahosted.org/fedora-qa/ticket/332 Repository: blockerbugs Description ------- Make navigation bar content loaded dynamically Diffs ----- blockerbugs/templates/index.html 17b98b686664754de74158afb4c793e245660690 blockerbugs/templates/base_nav.html f3a89798a9dadf297e722c067ad3795a72ebbf74 blockerbugs/controllers/main.py e7525f8433d74802f7c0cb2d719f0abdc13431c4 Diff: http://reviewboard-tflink.rhcloud.com/r/8/diff/ Testing ------- Thanks, Martin Krizek

1 0

Re: Review Request 8: Add Fedora 19 Milestones
by Martin Krizek 01 Mar '13

01 Mar '13

> On Feb. 26, 2013, 7:15 p.m., Tim Flink wrote: > > Code looks good to me for the most part. I realize that we've talked about g versus session for storing this data before but I'm hitting some minor issues regarding the ability of the menu bars to update. > > > > When I start adding/removing milestones, the only way that the menu bar is updated is if I start a new browser session - this means quitting the browser and re-starting _without_ restoring the previous session. There might be a better way to force a refresh but either way, I'm not so sure about putting the refresh burden on users instead of handling it in the app. > > > > Unfortunately, I can't think of many good ways to make this work well that don't involve an extra database query per request. One way would be to have a statically defined expiration in the session (like 1 day after initial load) and force refresh after that expiration. However, that has its own pitfalls and adds complexity - I'm not convinced this is a good idea. > > > > I'm wondering if it wouldn't be better to go back to what you had initially and use g. It would involve extra database queries but if that becomes a problem, caching would work well to reduce server load - most of the content is relatively static (in the timeframe of sync operations, 30 minutes right now) and caching could be a good way to work around this. > > Martin Krizek wrote: > In general, I agree. However, and please correct me if I am wrong, our use case is to put milestones into db before the testing starts (before the app is actually used by anyone). Then there is a testing period and then there is a testing break during which the session expires. And after the break we put the new milestones into db again. In this scenario I don't see the problem with refreshing the milestones. Or do we add/delete/change milestones during the testing period? Or are we planning to do that? If so, we should use the g object, otherwise, I think we're better off with session. True, the risk of having problems during the testing of a release are relatively small but I'd still rather not have to tell people to quit their browser or delete a cookie when new milestones aren't showing up in their browser. One possible solution would be to hack at permanent sessions so that the lifetime is something like 1 day (http://stackoverflow.com/questions/11783025/is-there-an-easy-way-to-make-se…) but honestly, I'm thinking that the use of g would be a better solution right now - postgres is supposed to be good at caching query results and this one shouldn't change all that often - if we end up with performance problems, we can always revisit. The change from g to session isn't much code. - Tim ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://reviewboard-tflink.rhcloud.com/r/8/#review10 ----------------------------------------------------------- On Feb. 26, 2013, 9:28 a.m., Martin Krizek wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > http://reviewboard-tflink.rhcloud.com/r/8/ > ----------------------------------------------------------- > > (Updated Feb. 26, 2013, 9:28 a.m.) > > > Review request for blockerbugs. > > > Bugs: 332 > https://fedorahosted.org/fedora-qa/ticket/332 > > > Repository: blockerbugs > > > Description > ------- > > Make navigation bar content loaded dynamically > > > Diffs > ----- > > blockerbugs/templates/index.html 17b98b686664754de74158afb4c793e245660690 > blockerbugs/templates/base_nav.html f3a89798a9dadf297e722c067ad3795a72ebbf74 > blockerbugs/controllers/main.py e7525f8433d74802f7c0cb2d719f0abdc13431c4 > > Diff: http://reviewboard-tflink.rhcloud.com/r/8/diff/ > > > Testing > ------- > > > Thanks, > > Martin Krizek > >

1 0

Re: Review Request 6: Fixing sync to work with new python-bugzilla and new FE naming convention
by Martin Krizek 01 Mar '13

01 Mar '13

----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://reviewboard-tflink.rhcloud.com/r/6/ ----------------------------------------------------------- (Updated March 1, 2013, 6:08 a.m.) Status ------ This change has been marked as submitted. Review request for blockerbugs. Bugs: 331 https://fedorahosted.org/fedora-qa/ticket/331 Repository: blockerbugs Description ------- Refactoring templates, bug sync and database to fit with new FreezeException nomenclature adding alembic upgrade script for db changes updated bug_sync code for python-bugzilla >= 0.8 Diffs ----- testing/testfunc_bugsync.py 719b530187a5e3fff7aba72c6776eecaad32cc40 testing/test_bugsync_extract_information.py 47df0e7cd34406aafb7c27f35944d6cff8cb96f3 setup.py e9fc12082a4d16afe93b04d7b96658715403eccc blockerbugs/util/bug_sync.py a85200dae03630d9407d7b27e235eb13c4a5b4a1 blockerbugs/templates/milestone_stats.html 8ff6bc4470967d7eaef633ef8b9b98330eac198b blockerbugs/templates/milestone_info.html 167dc0b1f5778c75f00e667240d03e8bf817e87a blockerbugs/templates/irc_format.txt a931c077f88cc998e9464b520a5625d7d9cc7e73 blockerbugs/templates/blocker_list.html 79a8a4b008319e80763f66de3ed6e56df89aa6d8 blockerbugs/templates/admin/modify_release.html 548c3d90c95bfe2a90d5d399d020b7bfcbcffc90 blockerbugs/templates/admin/main.html 121e79f4aa4330cc7b364f835ff2fd61178ac842 blockerbugs/templates/admin/add_release.html d396629f5f30787bbf136c163d24f272371cf06f blockerbugs/models/milestone.py cad913446157a15079a519fe0c29831b1635dc1f blockerbugs/models/bug.py dc25f060c470c0ad168e88c981ffe82203ca0d93 blockerbugs/controllers/main.py e7525f8433d74802f7c0cb2d719f0abdc13431c4 blockerbugs/controllers/forms.py 669d78a5030904d4559d6d68af093bd6f096888b blockerbugs/controllers/admin.py a6c8674820d602577363959be7d4eecd608cdf12 alembic/versions/487cb8ccce92_dropping_flask_login.py PRE-CREATION alembic/versions/31a6a2f222b7_changing_nth_and_tra.py PRE-CREATION Diff: http://reviewboard-tflink.rhcloud.com/r/6/diff/ Testing ------- I've done several syncs on both sqlite and postgres dbs and clicked around to make sure that all the templates that _were_ working are still working. Some of the admin pages still have issues but that is orthogonal to the changes here. I did an alembic upgrade of the database with no issues. Thanks, Tim Flink

1 0

Blocker Tracking App Deadlines and Schedules for F19
by Tim Flink 28 Feb '13

28 Feb '13

As we start getting closer to the time where we're all busy testing Fedora 19, it's time to start looking at what we want to get wrapped up before then. Looking at the Fedora 19 schedule [1], we have: 2013-03-12: F19 Branch from Rawhide 2013-04-02: Feature Freeze [1] https://fedoraproject.org/wiki/Releases/19/Schedule The way I'm thinking, the drop-dead-date is 2013-04-02. I don't remember a release where we weren't mostly consumed by testing tasks by the freeze date and even though we don't _think_ F19 is going to be a huge problem - that doesn't mean that we won't be busy :). I don't want to find ourselves in a situation where we really should be working on F19 but need to be wrapping up devel/integration work on any of the tools. The way I see it, we have some critical stuff left to do and some more nice-to-have stuff that won't cause too many problems if left unfinished. I've created a list at the end of this mail listing groups of tickets in order of priority. I'm not worried about (1) and (2) on that list. (1) is pretty much done and (2) should be pretty quick. (3) could be a problem but should be workable before F19 branches. That leaves (4) and (5) as the larger items which I don't think _have_ to be done before F19 but it would be really nice if they were done. Martin and I should know more about the likelihood of their completion in the next couple of days. (6) is a bunch of stuff that would be nice to have but I'm not going to lose any sleep if they aren't done in time. They would be great small things to pick up if anyone else is interested, though :) Tim == Critical to Finish Before F19 == 1. Finish in-progress work - https://fedorahosted.org/fedora-qa/ticket/334 * Implement Blocker/FE Proposal Page - https://fedorahosted.org/fedora-qa/ticket/332 * Add Fedora 19 Milestones These are either mostly done or close to being done - code reviews have been filed and code should be in develop soon 2. fixing some small bugs reported during F18 - https://fedorahosted.org/fedora-qa/ticket/314 * Bug summaries are not updated - https://fedorahosted.org/fedora-qa/ticket/330 * Blocker Components are not updated when a bug is reassigned These bugs were found during the F18 test cycle and shouldn't be too hard to actually get done. Since they were reported by users, the issues were noticed and thus really need to be fixed before F19 testing gets into full swing. 3. packaging and making sure we're able to use SSL for F19 - https://fedorahosted.org/fedora-qa/ticket/337 * Package Blocker Tracking App for Fedora and EPEL - https://fedorahosted.org/fedora-qa/ticket/359 * Create Ansible Playbooks for Deployment and Updating Now that we're using FAS logins for blocker proposals, we need to be able to use SSL so that passwords aren't transmitted in the clear. While using a self-signed cert is an option, it is kind of a last resort that decreases the usability of the site. I've been talking to the infra folks and the best way forward is if we can get the tracking app to the point where we are hosted in the production infrastructure. This means that we should be packaged in EPEL and have Ansible scripts for the deployment and updating of the app. I already have the Ansible playbooks mostly written - they mostly need some cleanup before submitting them. I'm not exactly sure how to handle alembic updates with playbooks and the package but I think that's something which could be figured out with packaging. The potential snag here is the CSS - right now that is being compiled from SCSS using sass/compass and the zurb-foundation framework. None of these things are currently packaged for EPEL6 (sass and compass are at least packaged for fedora so unless there are problems with the ruby version in EL6, those shouldn't be difficult). It's possible that CSS could be considered content instead of code which would allow us to continue distributing the compiled css instead of needing to compile it at build time. == Would be VERY nice to have but not absolutely critical for F19 == 4. improving the blocker submission so that it's either not so slow or not vulnerable to refresh during submission - https://fedorahosted.org/fedora-qa/ticket/356 * Blocker Proposal is Slow I haven't filed any detailed tickets for this yet because while I have ideas on how I want to fix this, I'm not sure if they would be practical or if there is enough time before F19 to actually get them done. 5. Bugzilla auth integration - https://fedorahosted.org/fedora-qa/ticket/347 * Implement Bugzilla Account Association - https://fedorahosted.org/fedora-qa/ticket/348 * Store Bugzilla Email Association in Database - https://fedorahosted.org/fedora-qa/ticket/349 * Implement Bugzilla Email Verification - https://fedorahosted.org/fedora-qa/ticket/350 * Integration Bugzilla Email Association with Blocker Proposal At the moment, Martin is planning to do this - not sure if it'll be done in time but we're going to be discussing that tomorrow. == Nice to have for F19 but not absolutely critical == 6. misc. cleanup (minifying css and js, reworking templates so that only the js _needed_ is loaded on every page, adding some links) - https://fedorahosted.org/fedora-qa/ticket/357 * Improve asset management - https://fedorahosted.org/fedora-qa/ticket/358 * Optimize Template CSS and JS includes - https://fedorahosted.org/fedora-qa/ticket/333 * Add visible Link to IRC Meeting Prep - https://fedorahosted.org/fedora-qa/ticket/343 * Add cgit link to Main Page

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

qa-devel March 2013