[Freeipa-devel] Releasing FreeIPA 4.1.2

[Alexander Bokovoy]

On Thu, 20 Nov 2014, Alexander Bokovoy wrote:
>On Thu, 20 Nov 2014, Martin Kosek wrote:
>>Hello,
>>
>>We seem to have enough content to release 4.1.2 that will be required to fix
>>some of the Fedora 21 blockers:
>>
>>https://bugzilla.redhat.com/show_bug.cgi?id=1165856
>>https://bugzilla.redhat.com/show_bug.cgi?id=1165261
>>
>>and Freeze exception:
>>https://bugzilla.redhat.com/show_bug.cgi?id=1165674
>>
>>Current plan is to release stabilization release 4.1.2 with what we have as it
>>contains the important installation and upgrade fixes.
>>
>>The only problem there is that some patches require components that are not in
>>Fedora stable repos, more specifically commits:
>>
>>7aa855a3  -> requiring new certmonger
>>4e119311  -> requiring new pki-core
>>
>>We can release 4.1.2 with them, but they would need to be removed from Fedora
>>21 downstream release and added back in normal 0day Fedora 21 update.
>>Alternative way would be to just include selected patches for existing Fedora
>>21 build.
>>
>>Any comments, what else are missing in 4.1.2? I only know about
>>https://fedorahosted.org/freeipa/ticket/4718
>>https://fedorahosted.org/freeipa/ticket/4728
>>which is ACKed at the moment, AFAIK.
>
>certmonger and pki-core parts can be backed out in the F21 build, they
>don't create issues for install time -- by definition we are not
>renewing certs at that point and we are not supporting becoming MS CA
>subordinate in the FreeIPA Server Role.
>
>Thus, we can do the release without them to Fedora 21 (and with them to
>rawhide) and have 0day update.
It looks like we'll have to pick up required fixes and do a build with
just them for Fedora 21 final to make sure we don't violate release
rules.

We can do the full release after it and push it to updates-testing once
stable updates consumed the fixed build for the Fedora 21 release.
-- 
/ Alexander Bokovoy