On Fri, Dec 08, 2017 at 02:14:53PM +0200, Timo Aaltonen wrote:
On 07.12.2017 22:07, Jakub Hrozek wrote:
> Hi Timo, Howard and sssd-devel list,
>
> Per Timo’s request (which makes sense also in general as we didn’t release for some
time), we’d like to release the 1.16.1 upstream tarball before the Christmas break.
Because I don’t want to plan any important work for the last week before Christmas, the
tentative date we’re thinking about is December 15th. Would that work for you or would it
disrupt any of your distributions schedule?
>
> As per the contents, the only ticket that must be included in the remaining week are
fixes for regressions:
>
https://pagure.io/SSSD/sssd/roadmap?status=Open&tag=regression&mi...
>
> Are there any other tickets that you think should be fixed in 1.16.1?
>
> btw the plan for us is to triage the (ridiculously long) 1.16.1 milestone by the
beginning to only include user-facing bugs, move other tickets (RFEs/internal changes) to
later releases and switch the 1.16.x release stream to bugfix-only. All the user-facing
tickets that won’t make the 1.16.1 cut would be moved to 1.16.2. I think we should do at
least one more 1.16 release, but whether we do more would also depend on you distribution
schedule..see also my other e-mail about SSSD 2.0..
Thanks, Dec 15th works fine for me.
I'm afraid we need to push the release after Christmas as we still don't
have all regressions fixed:
https://pagure.io/SSSD/sssd/roadmap?status=Open&tag=regression&mi...
at least #3594 has a patch proposed now..
Ubuntu 18.04 will be released on Apr
26th, and the feature-freeze is on Mar 1st. Might be too risky to push
2.0.x there, but I'll discuss this with others.
FWIW, I also don't know whether we'll include 2.0.x in RHEL-7 or only in
Fedora for now..we can always work with you on releasing a tarball if
you need use to apply some fixes from the master/2.x branch atop the
sssd-1-16 branch