Hi,
Stanislav raised a good question of a release planning. I'll try to cover my thoughts here.
We are getting close to that time of year with many vacations so I'd like to see us to release as much as possible before blending into white (or blue, or green) serenity.
Rob and I just released FreeIPA 4.8.2. There will probably be another release in December to collect an expected set of bug-fixes as we work on FIPS mode support across FreeIPA, MIT Kerberos, and Samba.
FreeIPA presence in various distributions can be tracked with Repology project: https://repology.org/project/freeipa/versions
For FreeIPA 4.7 series, there are three major users: Fedora 29, Debian-derivatives, and ALT Linux. RHEL 8 already moved to FreeIPA 4.8. Fedora 29 will become unsupported in early December 2019 according to the https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedul...
As FreeIPA 4.7 was a transitional Python 3 release, we expect to focus more on FreeIPA 4.8 and don't do much of backports to 4.7 branch going forward. So the idea is to have one more FreeIPA 4.7 release and then only do security-based releases.
ipa-4-7 branch right now contains 65 commits on top of FreeIPA 4.7.3 release. About 38% of them (25 out of 65) are related to tests and PR CI.
If distributions that keep working with FreeIPA 4.7 need to keep it alive, I'd like to see more involvement upstream from those. But probably moving to 4.8 is easier?
For FreeIPA 4.6 series, one of the major users is RHEL 7. It is already in a state where RHEL development cannot accept any requests for enhancements (RFE) and there is little chance for any version rebase, so picking up patches from upstream is OK there.
On the other hand, FreeIPA 4.6 is the last Python 2 release.
ipa-4-6 branch right now contains 57 commits on top of FreeIPA 4.6.6.
We can release 4.6.7 version to collect the changes for those distributions that need Python 2. It seems, AUR and Deepin are the most affected here as other distros moved on to 4.7 and 4.8.
On 13.11.2019 13.35, Alexander Bokovoy wrote:
Hi,
Stanislav raised a good question of a release planning. I'll try to cover my thoughts here.
We are getting close to that time of year with many vacations so I'd like to see us to release as much as possible before blending into white (or blue, or green) serenity.
Rob and I just released FreeIPA 4.8.2. There will probably be another release in December to collect an expected set of bug-fixes as we work on FIPS mode support across FreeIPA, MIT Kerberos, and Samba.
FreeIPA presence in various distributions can be tracked with Repology project: https://repology.org/project/freeipa/versions
For FreeIPA 4.7 series, there are three major users: Fedora 29, Debian-derivatives, and ALT Linux. RHEL 8 already moved to FreeIPA 4.8. Fedora 29 will become unsupported in early December 2019 according to the https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedul...
As FreeIPA 4.7 was a transitional Python 3 release, we expect to focus more on FreeIPA 4.8 and don't do much of backports to 4.7 branch going forward. So the idea is to have one more FreeIPA 4.7 release and then only do security-based releases.
ipa-4-7 branch right now contains 65 commits on top of FreeIPA 4.7.3 release. About 38% of them (25 out of 65) are related to tests and PR CI.
If distributions that keep working with FreeIPA 4.7 need to keep it alive, I'd like to see more involvement upstream from those. But probably moving to 4.8 is easier?
For FreeIPA 4.6 series, one of the major users is RHEL 7. It is already in a state where RHEL development cannot accept any requests for enhancements (RFE) and there is little chance for any version rebase, so picking up patches from upstream is OK there.
On the other hand, FreeIPA 4.6 is the last Python 2 release.
ipa-4-6 branch right now contains 57 commits on top of FreeIPA 4.6.6.
We can release 4.6.7 version to collect the changes for those distributions that need Python 2. It seems, AUR and Deepin are the most affected here as other distros moved on to 4.7 and 4.8.
Hi,
Just having a release for 4.8.x is fine by me, it's what I care about at this point. Regarding the versions on the repology page:
Debian stable - 4.7.2 was client only Deepin - synced from a Debian upload in Feb'18 Devuan - synced from Debian, 4.8 essentially needs systemd, which is amusing for Devuan.. Parrot/PureOS/Raspbian - 4.7.2 was client only Trisquel - ancient crap.. latest version based on Ubuntu 16.04 Ubuntu ->14.04, 18.10 - EOL Ubuntu 16.04 - meh Ubuntu 18.04 - probably will never be properly updated to 4.7.x since 20.04 is close, so meh Ubuntu 19.04 - client only, and soon EOL
Alexander, thank you for writing this.
13.11.2019 14:35, Alexander Bokovoy via FreeIPA-devel пишет:
FreeIPA presence in various distributions can be tracked with Repology project: https://repology.org/project/freeipa/versions
Unfortunately, ALT Linux is presented there only by one branch (don't know why). Just for your information, we have the following FreeIPAs:
- 4.3. I understand, that this is on my own support. There is a plan to migrate to 4.6+, but this is just a plan for now.
- 4.7. I don't have any reason to stay on this, but only time to rebase (plan: by the end of this year).
So, my targets are 4.6 and 4.8.
I would like to ask you about release dates. For example, FreeIPA has one minor release per year, this happens at the end of some month. Also there could be patch-releases - the end of each quarter. I understand that releases could be tied to the releases of major distros, but is some date schedule applicable?
Thanks.
On to, 14 marras 2019, Stanislav Levin wrote:
Alexander, thank you for writing this.
13.11.2019 14:35, Alexander Bokovoy via FreeIPA-devel пишет:
FreeIPA presence in various distributions can be tracked with Repology project: https://repology.org/project/freeipa/versions
Unfortunately, ALT Linux is presented there only by one branch (don't know why). Just for your information, we have the following FreeIPAs:
- 4.3. I understand, that this is on my own support. There is a plan to
migrate to 4.6+, but this is just a plan for now.
- 4.7. I don't have any reason to stay on this, but only time to rebase
(plan: by the end of this year).
So, my targets are 4.6 and 4.8.
Thanks. Then I think we can do one final scheduled FreeIPA 4.7 release and close the branch for normal backports.
I would like to ask you about release dates. For example, FreeIPA has one minor release per year, this happens at the end of some month. Also there could be patch-releases - the end of each quarter. I understand that releases could be tied to the releases of major distros, but is some date schedule applicable?
I wish I could give any date-based promise but I simply cannot. From my experience, committing to date-based releases is very stressful. It is not about making the release itself but rather ensuring we have releasable content all the time. We try to achieve that with CI but CI cannot account for in-progress features that being merged piece-by-piece.
We continue to be driven by completion of major features for time being. Before doing actual date-based releases, we need to automate release process, it is all manual right now.
I think for 2020 we need to look into definition of actual themes to base releases on and may be have some rough deadlines defined by which those themes need to be completed to get into a next release. Once that is announced, we try to stick to the release deadlines (give or take couple weeks, hopefully).
freeipa-devel@lists.fedorahosted.org
-
Alexander Bokovoy -
Stanislav Levin -
Timo Aaltonen