> -----Original Message----- > From: Development <[email protected]> On Behalf Of > Jedrzej Nowacki > Sent: Monday, 28 January 2019 3:54 PM > To: Robert Loehning <[email protected]> > Cc: [email protected] > Subject: Re: [Development] Proposal: New branch model > > On Monday, January 28, 2019 2:38:44 PM CET Robert Loehning wrote: > > Am 28.01.2019 um 14:09 schrieb Jedrzej Nowacki: > > > > > On Friday, January 25, 2019 3:23:36 PM CET Robert Loehning wrote: > > > > > >>> Testing whether the bug that I’m fixing exists in dev or not is > > >>> part of the drill of fixing bug, isn’t it? Why would you spend > > >>> time on fixing something in 5.12 without checking whether the > > >>> issue is still present in the latest codebase? Perhaps the issue > > >>> has been fixed already, just without the author considering it > > >>> relevant for 5.12 (perhaps for good reasons). > > >> > > >> Why would somebody who maintains a project on Qt5 but made the > > >> decision to not migrate it to Qt6 care about fixing the latter? > > >> > > >> > > >> > > >> Cheers, > > >> Robert > > > > > > > > > Project that is not being updated is not maintained. Not maintained > > > projects > should not take part of the mainstream. > > > > > > Cheers, > > > > > > Jędrek > > > > > > > > > > > > > > > I mean an external project which is based on Qt, like some commercial > > application. Say they decided - for good or bad reasons - that they > > will not migrate to Qt 6, but they require a fix in Qt 5. They even > > provide this fix, but why would they care about making it work in Qt 6? > > > > Cheers, > > Robert > > We have the same problem right now, just in the opposite direction. One > want to fix version 5.9, why the person should help with merging and solving > problems in 5.12? At least the problem would be visible in gerrit as an not > staged change.
Don't changes have to go to 5.12 first and then be backported to 5.9 with the current model? > Cheers, > Jędrek > > > _______________________________________________ > Development mailing list > [email protected] > https://lists.qt-project.org/listinfo/development _______________________________________________ Development mailing list [email protected] https://lists.qt-project.org/listinfo/development
