[SSSD] Re: Which tickets do we need to close before the release of the next upstream version?
On Mon, Oct 16, 2017 at 01:08:32PM +0200, Jakub Hrozek wrote: > > - https://pagure.io/SSSD/sssd/issue/2653 - Group renaming issue when > > "id_provider = ldap" is set. > > - there is a PR already and a test, let's review both > > Although there's a PR and a test written, this bug is stalled > > *again*. I'm sincerely failing to see the interest from SSSD team in > > order to have it merged; > > This one is on Lukas since he was the one who requested changes.. Hi Lukas, did you already have the chance to run the tests you wanted to? ___ sssd-devel mailing list -- sssd-devel@lists.fedorahosted.org To unsubscribe send an email to sssd-devel-le...@lists.fedorahosted.org
[SSSD] Re: Which tickets do we need to close before the release of the next upstream version?
On Mon, Oct 16, 2017 at 01:08:32PM +0200, Jakub Hrozek wrote: > > There are a few other PRs that would be nice to have merged in the tarball: > > - https://pagure.io/SSSD/sssd/pull-request/3320 > >What's the status of this one? Is it planned to be part of 1.16? > > What's needed in order to have it merged? What has been already done? > > I failed to find any info or status in the PR itself. > > > > - https://pagure.io/SSSD/sssd/issue/3463 > >This issue is related to the enumeration tests which are a blocker > > for this release. I've tried to work on this and failed due to the > > lack of knowledge both from the code and from the decisions > > historically taken when this code has been implemented. Would be > > really nice if someone could take a look on this one before the > > release. > > I think Michal is looking at both. Hi Michal, how do these two look like wrt the release we'll be doing soon? ___ sssd-devel mailing list -- sssd-devel@lists.fedorahosted.org To unsubscribe send an email to sssd-devel-le...@lists.fedorahosted.org
[SSSD] Re: Which tickets do we need to close before the release of the next upstream version?
On Mon, Oct 16, 2017 at 08:49:14AM +, Fabiano Fidêncio wrote: > On Thu, Oct 12, 2017 at 4:01 PM, Fabiano Fidêncio wrote: > > On Wed, Oct 11, 2017 at 5:29 PM, Jakub Hrozek wrote: > >> Hi, > >> > >> Because of downstream deadline, we need to release the next SSSD tarball > >> by the end of next week, or on the beginning of the next one at latest. > >> > >> And the 1.16.0 milestone is still really big and there are still tickets > >> in 1.15.4, so I'm trying to trim 1.16.0 and merge it with 1.15.4, > >> because realistically, I don't think we have another choice. > >> > >> Here's what I propose should *stay* in 1.16.0. Any other tickets should > >> be moved to 1.16.1: > >> - https://pagure.io/SSSD/sssd/issue/3507 - Long search filters are > >> created during IPA sudo command + command group retrieval > >> - there is a PR which pbrezina is assigned to. Let's keep the > >> ticket for now, if the PR can't be reviewed in time, we will > >> move the ticket. Downstreams can always patch their tarball > >> > >> - https://pagure.io/SSSD/sssd/issue/3496 - [RFE] Add a configuration > >> option to SSSD to disable the memory cache > >> - there is a PR already, let's review it > >> > >> - https://pagure.io/SSSD/sssd/issue/1872 - [RFE] Support User > >> Private Groups for main domains, too > >> - there is a PR already, let's review it > >> > >> - https://pagure.io/SSSD/sssd/issue/3503 - Do not index objectclass, > >> add and index objectcategory instead > >> - this is WIP, there was already a PR at one point > >> > >> - https://pagure.io/SSSD/sssd/issue/2653 - Group renaming issue when > >> "id_provider = ldap" is set. > >> - there is a PR already and a test, let's review both > >> > >> - https://pagure.io/SSSD/sssd/issue/2727 - Add a memcache for > >> SID-by-id lookups > >> - Sumit indicated that this is WIP, but we can move the ticket > >> to 1.16.1 if the PR doesn't make the cut > >> > >> - https://pagure.io/SSSD/sssd/issue/3468 - SSSD doesn't use AD > >> global catalog for gidnumber lookup, resulting in unacceptable > >> delay for large forests > >> - I'm working on this now > >> > >> - https://pagure.io/SSSD/sssd/issue/3307 - RFE: Log to syslog when > >> sssd cannot contact servers, goes offline > >> - Fabiano is working on this > >> > >> - https://pagure.io/SSSD/sssd/issue/3265 - [RFE] sssd should > >> remember DNS sites from first search > >> - I'd like to have this ticket fixed for the next release and > >> per discussion with Pavel, it's not a lot of work either > >> > >> - https://pagure.io/SSSD/sssd/issue/3264 - [RFE] Make 2FA prompting > >> configurable > >> - same as above > >> > >> At the same time, I would like to change the "Milestone" tag of all bugs > >> that were fixed in 1.15.4 to 1.16.0 and do not release another 1.15.x > >> version at all, but go straight to 1.16.0. > >> > >> And finally, all the unfished tickets in 1.15.4 would be moved to 1.16.1 > >> and at the same time triaged, because there are some tickets that can be > >> closed or moved to a future milestone completely. > >> > >> Opinions? > > > > Would be really nice if we could have the PR#275 > > (https://github.com/SSSD/sssd/pull/275) merged as well as part of 1.16 > > release, as the code seems good (according to the reviewer), has tests > > and comes from an external contributor. > > So, after 4 days I have to tell that I'm pretty much worried that we > will *not* reach our theoretical goal for 1.16. > > From the bugs in the list, I'm concerned about: > > - https://pagure.io/SSSD/sssd/issue/2653 - Group renaming issue when > "id_provider = ldap" is set. > - there is a PR already and a test, let's review both > Although there's a PR and a test written, this bug is stalled > *again*. I'm sincerely failing to see the interest from SSSD team in > order to have it merged; This one is on Lukas since he was the one who requested changes.. > > There are a few other PRs that would be nice to have merged in the tarball: > - https://pagure.io/SSSD/sssd/pull-request/3320 >What's the status of this one? Is it planned to be part of 1.16? > What's needed in order to have it merged? What has been already done? > I failed to find any info or status in the PR itself. > > - https://pagure.io/SSSD/sssd/issue/3463 >This issue is related to the enumeration tests which are a blocker > for this release. I've tried to work on this and failed due to the > lack of knowledge both from the code and from the decisions > historically taken when this code has been implemented. Would be > really nice if someone could take a look on this one before the > release. I think Michal is looking at both. ___ sssd-devel mailing list -- sssd-devel@lists.fedorahosted.org To unsubscribe
[SSSD] Re: Which tickets do we need to close before the release of the next upstream version?
On Thu, Oct 12, 2017 at 4:01 PM, Fabiano Fidêncio wrote: > On Wed, Oct 11, 2017 at 5:29 PM, Jakub Hrozek wrote: >> Hi, >> >> Because of downstream deadline, we need to release the next SSSD tarball >> by the end of next week, or on the beginning of the next one at latest. >> >> And the 1.16.0 milestone is still really big and there are still tickets >> in 1.15.4, so I'm trying to trim 1.16.0 and merge it with 1.15.4, >> because realistically, I don't think we have another choice. >> >> Here's what I propose should *stay* in 1.16.0. Any other tickets should >> be moved to 1.16.1: >> - https://pagure.io/SSSD/sssd/issue/3507 - Long search filters are >> created during IPA sudo command + command group retrieval >> - there is a PR which pbrezina is assigned to. Let's keep the >> ticket for now, if the PR can't be reviewed in time, we will >> move the ticket. Downstreams can always patch their tarball >> >> - https://pagure.io/SSSD/sssd/issue/3496 - [RFE] Add a configuration >> option to SSSD to disable the memory cache >> - there is a PR already, let's review it >> >> - https://pagure.io/SSSD/sssd/issue/1872 - [RFE] Support User >> Private Groups for main domains, too >> - there is a PR already, let's review it >> >> - https://pagure.io/SSSD/sssd/issue/3503 - Do not index objectclass, >> add and index objectcategory instead >> - this is WIP, there was already a PR at one point >> >> - https://pagure.io/SSSD/sssd/issue/2653 - Group renaming issue when >> "id_provider = ldap" is set. >> - there is a PR already and a test, let's review both >> >> - https://pagure.io/SSSD/sssd/issue/2727 - Add a memcache for >> SID-by-id lookups >> - Sumit indicated that this is WIP, but we can move the ticket >> to 1.16.1 if the PR doesn't make the cut >> >> - https://pagure.io/SSSD/sssd/issue/3468 - SSSD doesn't use AD >> global catalog for gidnumber lookup, resulting in unacceptable >> delay for large forests >> - I'm working on this now >> >> - https://pagure.io/SSSD/sssd/issue/3307 - RFE: Log to syslog when >> sssd cannot contact servers, goes offline >> - Fabiano is working on this >> >> - https://pagure.io/SSSD/sssd/issue/3265 - [RFE] sssd should >> remember DNS sites from first search >> - I'd like to have this ticket fixed for the next release and >> per discussion with Pavel, it's not a lot of work either >> >> - https://pagure.io/SSSD/sssd/issue/3264 - [RFE] Make 2FA prompting >> configurable >> - same as above >> >> At the same time, I would like to change the "Milestone" tag of all bugs >> that were fixed in 1.15.4 to 1.16.0 and do not release another 1.15.x >> version at all, but go straight to 1.16.0. >> >> And finally, all the unfished tickets in 1.15.4 would be moved to 1.16.1 >> and at the same time triaged, because there are some tickets that can be >> closed or moved to a future milestone completely. >> >> Opinions? > > Would be really nice if we could have the PR#275 > (https://github.com/SSSD/sssd/pull/275) merged as well as part of 1.16 > release, as the code seems good (according to the reviewer), has tests > and comes from an external contributor. So, after 4 days I have to tell that I'm pretty much worried that we will *not* reach our theoretical goal for 1.16. From the bugs in the list, I'm concerned about: - https://pagure.io/SSSD/sssd/issue/2653 - Group renaming issue when "id_provider = ldap" is set. - there is a PR already and a test, let's review both Although there's a PR and a test written, this bug is stalled *again*. I'm sincerely failing to see the interest from SSSD team in order to have it merged; There are a few other PRs that would be nice to have merged in the tarball: - https://pagure.io/SSSD/sssd/pull-request/3320 What's the status of this one? Is it planned to be part of 1.16? What's needed in order to have it merged? What has been already done? I failed to find any info or status in the PR itself. - https://pagure.io/SSSD/sssd/issue/3463 This issue is related to the enumeration tests which are a blocker for this release. I've tried to work on this and failed due to the lack of knowledge both from the code and from the decisions historically taken when this code has been implemented. Would be really nice if someone could take a look on this one before the release. Best Regards, -- Fabiano Fidêncio ___ sssd-devel mailing list -- sssd-devel@lists.fedorahosted.org To unsubscribe send an email to sssd-devel-le...@lists.fedorahosted.org
[SSSD] Re: Which tickets do we need to close before the release of the next upstream version?
On Wed, Oct 11, 2017 at 5:29 PM, Jakub Hrozek wrote: > Hi, > > Because of downstream deadline, we need to release the next SSSD tarball > by the end of next week, or on the beginning of the next one at latest. > > And the 1.16.0 milestone is still really big and there are still tickets > in 1.15.4, so I'm trying to trim 1.16.0 and merge it with 1.15.4, > because realistically, I don't think we have another choice. > > Here's what I propose should *stay* in 1.16.0. Any other tickets should > be moved to 1.16.1: > - https://pagure.io/SSSD/sssd/issue/3507 - Long search filters are > created during IPA sudo command + command group retrieval > - there is a PR which pbrezina is assigned to. Let's keep the > ticket for now, if the PR can't be reviewed in time, we will > move the ticket. Downstreams can always patch their tarball > > - https://pagure.io/SSSD/sssd/issue/3496 - [RFE] Add a configuration > option to SSSD to disable the memory cache > - there is a PR already, let's review it > > - https://pagure.io/SSSD/sssd/issue/1872 - [RFE] Support User > Private Groups for main domains, too > - there is a PR already, let's review it > > - https://pagure.io/SSSD/sssd/issue/3503 - Do not index objectclass, > add and index objectcategory instead > - this is WIP, there was already a PR at one point > > - https://pagure.io/SSSD/sssd/issue/2653 - Group renaming issue when > "id_provider = ldap" is set. > - there is a PR already and a test, let's review both > > - https://pagure.io/SSSD/sssd/issue/2727 - Add a memcache for > SID-by-id lookups > - Sumit indicated that this is WIP, but we can move the ticket > to 1.16.1 if the PR doesn't make the cut > > - https://pagure.io/SSSD/sssd/issue/3468 - SSSD doesn't use AD > global catalog for gidnumber lookup, resulting in unacceptable > delay for large forests > - I'm working on this now > > - https://pagure.io/SSSD/sssd/issue/3307 - RFE: Log to syslog when > sssd cannot contact servers, goes offline > - Fabiano is working on this > > - https://pagure.io/SSSD/sssd/issue/3265 - [RFE] sssd should > remember DNS sites from first search > - I'd like to have this ticket fixed for the next release and > per discussion with Pavel, it's not a lot of work either > > - https://pagure.io/SSSD/sssd/issue/3264 - [RFE] Make 2FA prompting > configurable > - same as above > > At the same time, I would like to change the "Milestone" tag of all bugs > that were fixed in 1.15.4 to 1.16.0 and do not release another 1.15.x > version at all, but go straight to 1.16.0. > > And finally, all the unfished tickets in 1.15.4 would be moved to 1.16.1 > and at the same time triaged, because there are some tickets that can be > closed or moved to a future milestone completely. > > Opinions? Would be really nice if we could have the PR#275 (https://github.com/SSSD/sssd/pull/275) merged as well as part of 1.16 release, as the code seems good (according to the reviewer), has tests and comes from an external contributor. > ___ > sssd-devel mailing list -- sssd-devel@lists.fedorahosted.org > To unsubscribe send an email to sssd-devel-le...@lists.fedorahosted.org ___ sssd-devel mailing list -- sssd-devel@lists.fedorahosted.org To unsubscribe send an email to sssd-devel-le...@lists.fedorahosted.org
