diff --git a/dogtag-pki.spec b/dogtag-pki.spec
index 4c87c67..2679d4d 100644
--- a/dogtag-pki.spec
+++ b/dogtag-pki.spec
@@ -1,7 +1,7 @@
 Summary:          Dogtag Public Key Infrastructure (PKI) Suite
 Name:             dogtag-pki
-Version:          10.2.6
-Release:          2%{?dist}
+Version:          10.3.0.a1
+Release:          1%{?dist}
 # The entire source code is GPLv2 except for 'pki-tps' which is LGPLv2
 License:          GPLv2 and LGPLv2
 URL:              http://pki.fedoraproject.org/
@@ -33,14 +33,6 @@ Requires:         pki-tools >= %{pki_core_version}
 Requires:         pki-symkey >= %{pki_core_version}
 Requires:         pki-base >= %{pki_core_version}
 
-# Make certain that this 'meta' package requires the latest version(s)
-# of ALL top-level Dogtag PKI support javadocs
-Requires:         jss-javadoc >= %{jss_version}
-
-# Make certain that this 'meta' package requires the latest version(s)
-# of ALL Dogtag PKI core javadocs
-Requires:         pki-javadoc >= %{pki_core_version}
-
 # Make certain that this 'meta' package requires the latest version(s)
 # of Dogtag PKI console
 Requires:         pki-console >= %{pki_console_version}
@@ -54,24 +46,27 @@ The Dogtag Public Key Infrastructure (PKI) Suite is comprised of the following
 five subsystems and a client (for use by a Token Management System):
 
   * Certificate Authority (CA)
-  * Data Recovery Manager (DRM)
+  * Key Recovery Authority (KRA)
   * Online Certificate Status Protocol (OCSP) Manager
   * Token Key Service (TKS)
   * Token Processing System (TPS)
   * Enterprise Security Client (ESC)
 
 Additionally, it provides a console GUI application used for server and
-user/group administration of CA, DRM, OCSP, and TKS, javadocs on portions
-of the Dogtag API, as well as various command-line tools used to assist with
-a PKI deployment.
+user/group administration of CA, KRA, OCSP, and TKS, as well as various
+command-line tools used to assist with a PKI deployment.
 
-To successfully deploy instances of a CA, DRM, OCSP, TKS, or TPS,
+To successfully deploy instances of a CA, KRA, OCSP, TKS, or TPS,
 a Tomcat Web Server must be up and running locally on this machine.
 
-To meet the database storage requirements of each CA, DRM, OCSP, TKS, or TPS
+To meet the database storage requirements of each CA, KRA, OCSP, TKS, or TPS
 instance, a 389 Directory Server must be up and running either locally on
 this machine, or remotely over the attached network connection.
 
+Finally, although they are no longer supplied by this 'meta' package,
+javadocs are available for both JSS (jss-javadoc) and portions of
+the Dogtag API (pki-javadoc).
+
 NOTE:  As a convenience for standalone deployments, this 'dogtag-pki'
        top-level meta package supplies Dogtag themes for use by the
        certificate server packages:
@@ -94,8 +89,14 @@ rm -rf %{buildroot}
 %doc README
 
 %changelog
-* Wed Feb 03 2016 Fedora Release Engineering <releng@fedoraproject.org> - 10.2.6-2
-- Rebuilt for https://fedoraproject.org/wiki/Fedora_24_Mass_Rebuild
+* Fri Mar  4 2016 Dogtag Team <pki-devel@redhat.com> 10.3.0.a1-1
+- Build for F24 alpha
+
+* Sat Aug  8 2015 Dogtag Team <pki-devel@redhat.com> 10.3.0-0.1
+- Updated version number to 10.3.0-0.1
+
+* Sat Jul 18 2015 Dogtag Team <pki-devel@redhat.com> 10.2.7-0.1
+- Updated version number to 10.2.7-0.1
 
 * Sat Jul 18 2015 Dogtag Team <pki-devel@redhat.com> 10.2.6-1
 - Update release number for release build