On Tue, Aug 22, 2017 at 09:19:54AM +0200, Lukas Slebodnik wrote: > On (21/08/17 21:04), Jakub Hrozek wrote: > >Hi, > > > >1.15.4 will be released by the end of this months in a time-based > >fashion. But obviously, the milestone is too big, so we need to decide > >where do we push the tickets to. > > > >I added tags to the tickets with my proposed cleanup: > > - move to 1.16: > > > > https://pagure.io/SSSD/sssd/roadmap?status=Open&tag=cleanup-one-sixteen&no_stones= > > - move to 'future releases' > > https://pagure.io/SSSD/sssd/roadmap?status=Open&tag=cleanup-future&no_stones= > > - move to 'patches welcome' > > > > https://pagure.io/SSSD/sssd/roadmap?status=Open&tag=cleanup-patches-welcome&no_stones= > > > > What is a difference between 'future releases' and 'patches welcome' ?
future releses = this is what we look at when we plan a next version patches welcome = unless someone submits a PR, we won't look at this ticket. We're just leaving it around in case someone else is interested in providing a patch. > > Why is https://pagure.io/SSSD/sssd/issue/3399 proposed to move into > future releases if it already have PR? Because I missed it has a PR :) > > > >It would be nice to hear some feedback from others before I move the > >tickets. > > > >About the tickets that are proposed to stay in 1.15 -- most of them have > >PRs available, but those that we won't finish should IMO be rolled to > >1.15.5, because who knows when will 1.16.0 be released and especially > >the KCM related fixes are important to be included in Fedora around > >Sep-5, so I think we might want to do another release a week after .4.. > > > >And finally, about the 1.16 milestone -- I suggest we start chopping on > >that one as developers shake off 1.15.x tasks. We should do a time-based > >release by the end of September, then one by the end of October and see > >how many tickets are left.. > > > > We could afford to do time-based releases if we have full code coverage > in upstream. We are not there yet. Yes, but time-based here means 'we won't continue developing sssd in this milestone until all the tickets are fixed', but instead 'we release sssd by some date and move the tickets into other releases'. Of couse we would fix regressions and run tests. btw since sssd releases were historically driven by RHEL a lot, quite a few releases were time-based anyway based on RHEL schedule. I hope maintainers from other distributions would chime in with their schedule (and Timo did in a way with 1.15 lately on IRC..) _______________________________________________ sssd-devel mailing list -- sssd-devel@lists.fedorahosted.org To unsubscribe send an email to sssd-devel-le...@lists.fedorahosted.org
