- Dogtag 10.4 (master)
- Dogtag 10.3 (maintenance branch)
- Dogtag 10.2 (maintenance branch)
- Dogtag 10.2.6 (maintenance branch)
- Dogtag 10.2.5 (maintenance branch)
- Dogtag 10.2.4 (maintenance branch)
- Dogtag 10.2.3 (maintenance branch)
- Dogtag 10.2.2 (maintenance branch)
- Dogtag 10.2.1 (maintenance branch)
- Dogtag 10.2.0 (maintenance branch)
- Dogtag 10.1 (maintenance branch)
Dogtag 10.0 (maintenance branch)
Dogtag 9.0 (maintenance branch)
Revised Branch Names
On September 16, 2014, the PKI git repository branches were renamed to follow our new naming conventions:
|ORIGINAL BRANCH NAME||NEW BRANCH NAME|
|remotes/origin/HEAD -> origin/master||remotes/origin/HEAD -> origin/master|
The following table shows the corresponding platform vs. product version vs. branch names:
The following describes the branching philosophy associated with packaging:
Example of Updating an Existing Branch that has been Previously Checked-Out
(1) Identify the local branch
# git branch IPA_V3_RHEL_7_ERRATA_BRANCH
(2) Rename the local branch
# git branch -m IPA_V3_RHEL_7_ERRATA_BRANCH DOGTAG_10_0_RHEL_BRANCH
(3) Identify the local branch
# git branch DOGTAG_10_0_RHEL_BRANCH
(4) Attempt to update the local branch from the remote branch
# git pull . . . Your configuration specifies to merge with the ref 'IPA_V3_RHEL_7_ERRATA_BRANCH' from the remote, but no such ref was fetched.
(5) Setup remote upstream tracking on the branch you just renamed
# git branch -u origin/DOGTAG_10_0_RHEL_BRANCH Branch DOGTAG_10_0_RHEL_BRANCH set up to track remote branch DOGTAG_10_0_RHEL_BRANCH from origin.
(6) Attempt to update the local branch from the remote branch
# git pull Already up-to-date.
This new version of Dogtag will begin development using 64-bit x86_64 Fedora 16.
Much of this new version of Dogtag will be based upon the following versions of these major third-party components:
and will make use of the following third-party technologies:
Dogtag will also utilize the following third-party components:
See Development Tools.
The fedorahosted.org sunset on Tuesday, February 28, 2017; this involved migration of the numerous products away from the use of its TRAC Issue Trackers, storage of various SVN and GIT repositories, and movement away from TRAC Wiki material: