We need to determine whether to support TPS backward compatibility (BC).
Here is a possible scenario, a user has a 10.1 CA and 10.1 TPS on different machines. When the user is doing a yum update on the first machine, the CA may get automatically upgraded to 10.2 due to some dependencies without the user realizing it. If BC is supported, the 10.1 TPS will continue to work with the new 10.2 CA. If BC is not supported, the 10.1 TPS may not be working properly anymore, and the solution is to upgrade it to 10.2 TPS, which could be difficult if there is no automatic TPS migration script.
If BC is not required in 10.2, there may be some configuration/protocol/database changes that can be done to significantly improve TPS on the long run. If these changes are not done in 10.2, changing it later may be more difficult because after 10.2 the BC is probably a must.
If BC is required in 10.2, there may be some changes that are already committed that need to be reverted. A proper testing will be needed to validate BC.
Proposed milestone: April
On 4/23/2014, a separate meeting was held on this which resulted in the creation of a Wiki page to document decisions:
Per discussions, targeted 10.2 - 04/14 (April)
Since the decision was made, this ticket can be closed.
Metadata Update from @edewata: - Issue set to the milestone: 10.2 - 04/14 (April)
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/1523
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Log in to comment on this ticket.