#1724 Re-base Dogtag pki packages to 10.3.x
Closed: Fixed Opened by mkosek.

Re-base pki-core to version 10.3.x, to include the latest stabilization and enhancements required by Identity Management.

Additionally, this ticket shall also be used to re-base the remainder of the Dogtag pki packages including:

  • dogtag-pki
  • dogtag-pki-theme
  • pki-console

Per discussions in the Dogtag 10.3 Triage meeting of 01/06/2016: priority high

First release is slated to be called 10.3.0.a1 and has a goal target of F24 alpha.

The following spec file clean-up was checked into master:

commit 68bfe81d7892c26d2e9485084c430575a921bddc Author: Matthew Harmsen ​mharmsen@pki.usersys.redhat.com Date: Mon Mar 7 12:14:33 2016 -0700

Miscellaneous cleanup of spec files
PKI TRAC Ticket #1701 - Removed javadocs from 'meta' package
PKI TRAC Ticket #1099 - Rename DRM nomenclature to KRA nomenclature

Fedora 24 (alpha):

  • http://koji.fedoraproject.org/koji/buildinfo?buildID=742778 dogtag-pki-theme-10.3.0.a1-1.fc24
  • http://koji.fedoraproject.org/koji/buildinfo?buildID=742790 pki-core-10.3.0.a1-1.fc24
  • http://koji.fedoraproject.org/koji/buildinfo?buildID=742838 dogtag-pki-10.3.0.a1-1.fc24
  • http://koji.fedoraproject.org/koji/buildinfo?buildID=742813 pki-console-10.3.0.a1-1.fc24

Fedora 25 (rawhide):

  • http://koji.fedoraproject.org/koji/buildinfo?buildID=742787 dogtag-pki-theme-10.3.0.a1-1.fc25
  • http://koji.fedoraproject.org/koji/buildinfo?buildID=742807 pki-core-10.3.0.a1-1.fc25
  • http://koji.fedoraproject.org/koji/buildinfo?buildID=742840 dogtag-pki-10.3.0.a1-1.fc25
  • http://koji.fedoraproject.org/koji/buildinfo?buildID=742852 pki-console-10.3.0.a1-1.fc25

Metadata Update from @mkosek:
- Issue assigned to mharmsen
- Issue set to the milestone: 10.3.0.a1

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/2282

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Metadata