Issue #74: Sync up versions of resultsdb/frontend/api and build rpms from what's in develop - resultsdb - Pagure.io

Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.

taskotron / resultsdb

#74 Sync up versions of resultsdb/frontend/api and build rpms from what's in develop

Closed: Fixed Opened Feb 1, 2017 by jskladan.

^^^
I really believe that we should sync up at least the major versions of the resultsdb components. There also are a lot of user-facing fixes now, so it would be wise to rebuild and deploy the packages from the current state of the develop branches.
With _frontend, that should also contain the D1106.

somebody commented Feb 1, 2017

This ticket is a duplicate of https://pagure.io/taskotron/issue/208

somebody commented Feb 1, 2017

This ticket had assigned some Differential requests:
D1106
D1107

jskladan commented Feb 1, 2017

Also D1107, pls.

{meme, src=doge, above="such diff very update", below="much review pls"}

kparal commented Feb 2, 2017

Fixed in db96c6e21cf865038e , 864c63a4ad3e0e5aa7 and eb561f2aaa72e5717c9c8e3.

Metadata

Assignee

None

Tags

None

Blocking

None

Depending on

None

Priority

Low

Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.