Difference between revisions of "Dogtag"

Revision as of 19:29, 14 November 2017

Roadmap

Dogtag will be undergoing some exciting new changes to make it easier to be integrated with other projects.

For a roadmap of these changes, see Dogtag Future Directions.

Source Code

Dogtag source code is managed via the Git Revision Control System and can be viewed at the pki.git repository:

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/DOGTAG_10_0_BRANCH	remotes/origin/DOGTAG_10_0_BRANCH
remotes/origin/IPA_V3_RHEL_7_ERRATA_BRANCH	remotes/origin/DOGTAG_10_0_RHEL_BRANCH
remotes/origin/DOGTAG_10_1_BRANCH	remotes/origin/DOGTAG_10_1_BRANCH
remotes/origin/IPA_V4_RHEL_7_1_ERRATA_BRANCH	remotes/origin/DOGTAG_10_1_RHEL_BRANCH
'master' 7cf3bd73a7c41d8633fb2a92053a55e0e36a4925	remotes/origin/DOGTAG_10_2_RHEL_BRANCH
remotes/origin/DOGTAG_9_BRANCH	remotes/origin/DOGTAG_9_0_BRANCH
remotes/origin/IPA_v2_RHEL_6_ERRATA_BRANCH	remotes/origin/DOGTAG_9_0_RHEL_BRANCH
remotes/origin/RHEL_7_0_BRANCH
remotes/origin/RHEL_7_BRANCH
remotes/origin/autoformat
remotes/origin/autoformat2
remotes/origin/HEAD -> origin/master	remotes/origin/HEAD -> origin/master
remotes/origin/master	remotes/origin/master

The following table shows the corresponding platform vs. product version vs. branch names:

Platform vs. Product Version vs. Branch

The following describes the branching philosophy associated with packaging:

Package Versioning

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.

Platform

This new version of Dogtag will begin development using 64-bit x86_64 Fedora 16.

Third-Party Components

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:

Development Tools

Development of this new version of Dogtag will take advantage of the following development tools:

Javadocs

On-line Dogtag Javadocs

Designs

The following designs are for a future version of Dogtag:

Features should begin utilizing the following template:

PKI Feature Template

Proposals

Resources for Client Developers

Releases

'How-To' Procedures

Miscellaneous

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:

RELOCATION OF PROJECT ISSUES, REPOSITORIES, AND WIKI INFORMATION

@@ Line 190: / Line 190: @@
 == Proposals ==
 * [[Proposal to Separate Existing Single PKI Source Repository into Multiple PKI Source Repositories]]
+* [[Proposal to Combine Multiple SRPMS into a Single SRPM]]
 == Resources for Client Developers ==
 * [[REST|REST interfaces in Dogtag]]