On Wed, Sep 12, 2018 at 6:44 AM, Neal Gompa <ngompa13@xxxxxxxxx> wrote: > On Wed, Sep 12, 2018 at 9:34 AM Rex Dieter <rdieter@xxxxxxxxxxxx> wrote: >> >> Matthew Miller wrote: >> >> > On Wed, Sep 12, 2018 at 12:27:03AM +0200, Luigi Toscano wrote: >> >> It does not make sense to do it for Frameworks (which is always keeping >> >> the API), nor for the bundle known as KDE Applications (where you want >> >> the last version), nor for the applications which independent release >> >> schedule (Krita, Krusader, Tellico, etc; same as KDE Applications). >> > >> > One thing that you could do, if you want, is only maintain a single branch >> > and spec file for each of these which would build across all current >> > supported releases... >> >> Now that part does sound appealing, is essentially what we do for plasma >> releases already by hand. >> > > We could technically do this now simply by ignoring the other branches > and just tell fedpkg to kick off builds against the master branch all > the time. Modules do not solve this specific problem. Allowing us to > use fedpkg to push to multiple releases simultaneously without work > would help more. > does "fedpkg build --target f27" work? Or does that mess up the whole testing infrastucture? Troy _______________________________________________ kde mailing list -- kde@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to kde-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kde@xxxxxxxxxxxxxxxxxxxxxxx
