New OpenLDAP was released two days after branch freeze (2011-02-10). New release contains many bugfixes. Mozilla NSS patches we had separately are now included. There are a few improvements of server backends. API was extended * libldap adds: ldap_destroy ldap_dup ldap_sasl_interactive_bind * libldif adds: ldif_put_wrap ldif_sput_wrap (DB5 support was added, but I left it to use DB4. I would like to test this particular feature in F-16.) It would be pity if the new OpenLDAP didn't get it into F-15 Alpha. +++ This bug was initially created as a clone of Bug #676888 +++ Latest upstream release: 2.4.24 Current version in Fedora Rawhide: 2.4.23 URL: ftp://ftp.openldap.org/pub/OpenLDAP/openldap-release Please consult the package update guidelines before you issue an update to a stable branch: https://fedoraproject.org/wiki/Package_update_guidelines More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring --- Additional comment from jvcelak on 2011-02-14 15:19:22 CET --- openldap-2.4.24-1.fc16
openldap-2.4.24-1.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/openldap-2.4.24-1.fc15
There's no obvious reason this should be an Alpha blocker; please let us know why it's been submitted for consideration as one. Thanks!
(In reply to comment #2) > There's no obvious reason this should be an Alpha blocker; please let us know > why it's been submitted for consideration as one. Thanks! Hi Adam, I originally requested rel-eng to tag the build for F15 Alpha. I was suggested to use this way, filing a bug with blocker [1]. To summarize my reasons to support this request: - New OpenLDAP was released two days after our branch freeze (bugfixes, new features in backends, extended API, documentation updates), complete list on [2]. - Fedora QA proventesters are unable to test any openldap updates. That's sad but it is right. To prove this argument, the last stable update for F14 is openldap-2.4.23-4.fc14 (84 days old), the newest update in testing is openldap-2.4.23-8.fc14 (12 days old) which obsoletes 3 other (working) updates. Latest F13 update: 129 days before proventesters approval. - Getting the new package into Alpha will give us more time for testing and can reveal potential problems. - We are leading edge distribution. We want to have last versions of programs in GA release. - Upstream is in generally unwilling to help with resolving any issues in other than last release or development version. Jan [1] https://fedorahosted.org/rel-eng/ticket/4435 [2] http://www.openldap.org/software/release/changes.html
None of that really justifies tagging the build into a frozen release; a lot of it seems to be written from the assumption that you need this update in the Alpha or it can't be in F15, and that's not the case. The proventester issue is problematic, though, and we should solve that, or you will have trouble getting the packages in now, because we've branched and openldap is critpath. I will mail you to discuss ways we can solve the proventester issue, as it's beyond the scope of this bug report. we'll vote on this at the next blocker bug review. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
openldap-2.4.24-1.fc15 has been pushed to the Fedora 15 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update openldap'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/openldap-2.4.24-1.fc15
@Adam ... should we move this into NICE-TO-HAVE (F15Alpha-accepted)?
Um. I would not vote for this as blocker or NTH. Remember, when evaluating blockers we keep in mind that the concept of being 'in the Alpha' is only particularly meaningful as far as things that get hit during installation, live use, or pre-update use are concerned. If the update doesn't make desired changes to LDAP login stuff, I'm not sure any of that is satisfied, and I don't see any reason for a freeze exception for this. Anyone who actually installs the Alpha will get it as an update, after all.
I have to agree with adam here, Lets make sure we get it the needed testing to get included in GA, but i dont see it as critical to alpha getting out.
OK guys, I agree. Thank you. Shall I remove the F15Alpha blocker? Do we have some other for GA?
yes, there are blockers for alpha, beta and final: f15alpha, f15beta, f15blocker . I don't think this meets the criteria for any of them, though. The release criteria / blocker process is focused on functionality, not on including some particular version of any given thing; we don't consider it a release blocking issue simply for something to be old. Once Alpha is out we unfreeze till Beta - you have several weeks in which you can simply submit the updated openldap through the regular process (do a build, submit it as an update via bodhi) and it will go in (as long as it receives the necessary karma).
OK. Thank you. Removing F15Alpha blocker.
openldap-2.4.24-2.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/openldap-2.4.24-2.fc15
openldap-2.4.24-2.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.