FreeIPA release - better automation of wiki updates
by Martin Kosek
Hi all,
I was thinking about improvements to FreeIPA release processes and
related wiki updates. Relevant changes and upgrades to the wiki and it's
plugins [1] that I did recently will may enable us to leverage some of
the new functionality to fully automate the wiki updates.
If I check the release instructions [2] I see lot of manual steps that
prolong the release procedure. I think these could be improved to not
make wiki the bottleneck of full release automation:
1) Downloads - add pointer to new tarball
I would propose moving this information to release page, along with
information/link how we sign the release (or use signature as only mean
of verifying the release). Downloads page could then for example just
simply list links to the 5 most recent releases, utilizing the updated
plugin [3].
This means that the page would *not be changed* during release.
2) Main_Page - add info on new release
This document could again just list most recent 5 releases with [3],
filtered by category. We just need to make sure the Release pages have
some category assigned, which can be done easily if related template
{{ReleaseDate|YYY-MM-DD}} is used on every release (it was missed couple
last releases).
3) News - add similar info as on Main_Page
I see this page is now even obsolete, so we just remove it from [2]
4) Roadmap - add info on new release, check if Roadmap is up to date
This is still valid, but not may be a requirement for the release
person, this is just something we need to do when opening new milestones
or updating the upstream course.
5) Documentation - update links and version numbers
I am actually not sure what version numbers are meant here.
6) Build - update COPR repositories if new ones are introduced or old
abandoned
Same as 4) - something to be done when a new milestone is done,
especially if the release is a major release.
Summary: I think that if we leverage the new wiki capabilities and
changes proposed in this mail, the wiki changes for releasing a minor
FreeIPA release may be just creating the single release page and all
other pages should update automatically themselves.
[1] https://github.com/freeipa/freeipa-wiki
[2] https://www.freeipa.org/page/Release#Wiki_pages_to_be_updated
[3] https://www.mediawiki.org/wiki/Extension:DynamicPageList_(Wikimedia)
--
Martin Kosek <mkosek(a)redhat.com>
Manager, Software Engineering - Identity Management Team
Red Hat, Inc.
5 years, 9 months
[freeipa PR#1415][opened] Include ipa_krb5.h without util prefix
by tiran
URL: https://github.com/freeipa/freeipa/pull/1415
Author: tiran
Title: #1415: Include ipa_krb5.h without util prefix
Action: opened
PR body:
"""
Fixes out-of-tree builds.
ipa_kdb_certauth.c is the only place that includes the header file with ``util`` prefix
```
$ find -name '*.[ch]' | xargs grep 'include "ipa_krb5.h"'
./client/ipa-getkeytab.c:#include "ipa_krb5.h"
./util/ipa_krb5.c:#include "ipa_krb5.h"
./daemons/ipa-slapi-plugins/ipa-pwd-extop/ipapwd.h:#include "ipa_krb5.h"
./daemons/ipa-slapi-plugins/ipa-pwd-extop/encoding.c:#include "ipa_krb5.h"
./daemons/ipa-kdb/ipa_kdb.h:#include "ipa_krb5.h"
./daemons/ipa-kdb/ipa_kdb_certauth.c:#include "ipa_krb5.h"
./asn1/ipa_asn1.h:#include "ipa_krb5.h"
```
"""
To pull the PR as Git branch:
git remote add ghfreeipa https://github.com/freeipa/freeipa
git fetch ghfreeipa pull/1415/head:pr1415
git checkout pr1415
5 years, 9 months