[Freeipa-devel] Releasing FreeIPA 4.1.2

[Martin Kosek]

On 11/25/2014 10:56 AM, Martin Kosek wrote:
> On 11/25/2014 09:36 AM, Alexander Bokovoy wrote:
>> On Tue, 25 Nov 2014, Martin Kosek wrote:
>>> On 11/20/2014 01:09 PM, 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.
>>>
>>> We will need to release 4.1.2 today to make sure that the 4.1.2 release can be
>>> picked up in CentOS FreeIPA container.
>>>
>>> Petr1, I assume you will do the build now :-) We just need to make sure that
>>> any pending acked patches are pushed. We also need to make sure that our new
>>> dependencies (like the POODLE ones) that were built for Fedora are also in our
>>> CentOS repo so that FreeIPA 4.1.2 is still well installlable there.
>> My patch 0170 is needed for trusts to ease debugging in a typical case
>> of firewall/replication issues.
> 
> I see patch 0170 as a useful patch, but not as blocking for 4.1.2 which we need
> for the CentOS containers. IMO it can wait for 4.1.3.
> 
> Martin

Ok, you won - the patch was reviewed fast enough so it ends up in 4.1.2 :-)

We can go ahead with 4.1.2 tagging then.

Martin