Project

General

Profile

Task #7509

Story #7506: Tracker for libraries that need to be updated

Decide if other CN libraries should be updated

Added by Ben Leinfelder about 8 years ago. Updated about 8 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Start date:
2015-12-04
Due date:
% Done:

100%

Estimated time:
0.00 h
Story Points:
Sprint:

Description

Other libraries that use d1_cn_common directly, include:
* d1_cn_tools
* d1_replication
* d1_synchronization
* d1_cn_approve_node
* d1_cn_index_tool

Do we need to update these to keep the entire CN server using the same exact version of d1_cn_common? It would mean redeploying many other components of the CN even though the only thing that changed is the LDAPSerice abstract superclass in d1_cn_common.

History

#1 Updated by Ben Leinfelder about 8 years ago

  • Description updated (diff)

#2 Updated by Ben Leinfelder about 8 years ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100
  • translation missing: en.field_remaining_hours set to 0.0

Sounds like we will update the downstream projects to keep consistency on the CN.

#3 Updated by Ben Leinfelder about 8 years ago

  • Description updated (diff)
  • Estimated time set to 0.00

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)