| 00000 |
[OASIS Issue Tracker] (OSLCCCM-11) Some form of subscription and/or update notification may be required |
OASIS Issues Tracker
|
2016-06-01 20:30 |
| 00001 |
[OASIS Issue Tracker] (OSLCCCM-19) Resource shapes for versioned type systems |
OASIS Issues Tracker
|
2016-06-01 20:30 |
| 00002 |
[OASIS Issue Tracker] (OSLCCCM-14) How should previousBaseline behave when an intermediate baseline is deleted? |
OASIS Issues Tracker
|
2016-06-01 20:33 |
| 00003 |
[OASIS Issue Tracker] (OSLCCCM-14) How should previousBaseline behave when an intermediate baseline is deleted? |
OASIS Issues Tracker
|
2016-06-01 20:35 |
| 00004 |
[OASIS Issue Tracker] (OSLCCCM-22) Provide a way for a client to discover the configuration used to resolve a request |
OASIS Issues Tracker
|
2016-06-01 20:40 |
| 00005 |
[OASIS Issue Tracker] (OSLCCCM-22) Provide a way for a client to discover the configuration used to resolve a request |
OASIS Issues Tracker
|
2016-06-01 20:40 |
| 00006 |
OASIS OSLC CCM TC meeting this week - confirmation - voting members please attend! |
Nicholas Crossley
|
2016-06-01 21:16 |
| 00007 |
[OASIS Issue Tracker] (OSLCCCM-22) Provide a way for a client to discover the configuration used to resolve a request |
OASIS Issues Tracker
|
2016-06-02 13:42 |
| 00008 |
[OASIS Issue Tracker] (OSLCCCM-14) How should previousBaseline behave when an intermediate baseline is deleted? |
OASIS Issues Tracker
|
2016-06-02 13:48 |
| 00009 |
[OASIS Issue Tracker] (OSLCCCM-22) Provide a way for a client to discover the configuration used to resolve a request |
OASIS Issues Tracker
|
2016-06-02 14:30 |
| 00010 |
[OASIS Issue Tracker] (OSLCCCM-14) How should previousBaseline behave when an intermediate baseline is deleted? |
OASIS Issues Tracker
|
2016-06-02 14:48 |
| 00011 |
[OASIS Issue Tracker] (OSLCCCM-22) Provide a way for a client to discover the configuration used to resolve a request |
OASIS Issues Tracker
|
2016-06-02 14:50 |
| 00012 |
Review of change management spec |
Sarabura, Martin
|
2016-06-02 14:56 |
| 00013 |
[OASIS Issue Tracker] (OSLCCCM-22) Provide a way for a client to discover the configuration used to resolve a request |
OASIS Issues Tracker
|
2016-06-02 16:17 |
| 00014 |
[OASIS Issue Tracker] (OSLCCCM-22) Provide a way for a client to discover the configuration used to resolve a request |
OASIS Issues Tracker
|
2016-06-02 17:48 |
| 00015 |
[OASIS Issue Tracker] (OSLCCCM-22) Provide a way for a client to discover the configuration used to resolve a request |
OASIS Issues Tracker
|
2016-06-02 18:00 |
| 00016 |
Comments on Change Management specs |
David Honey1
|
2016-06-03 11:22 |
| 00017 |
Re: [oslc-ccm] Comments on Change Management specs |
Nicholas Crossley
|
2016-06-03 14:54 |
| 00018 |
[OASIS Issue Tracker] (OSLCCCM-23) oslc_cm:status range is String in CM 2.0 and can't be changed to oslc_cm:Status |
OASIS Issues Tracker
|
2016-06-03 20:34 |
| 00019 |
Re: [oslc-ccm] Review of change management spec |
Jim Amsden
|
2016-06-03 20:48 |
| 00020 |
Version Control Commit by ndjc |
[email protected]
|
2016-06-03 20:55 |
| 00021 |
Re: [oslc-ccm] Comments on Change Management specs |
Jim Amsden
|
2016-06-06 14:13 |
| 00022 |
[OASIS Issue Tracker] (OSLCCCM-23) oslc_cm:status range is String in CM 2.0 and can't be changed to oslc_cm:Status |
OASIS Issues Tracker
|
2016-06-07 17:08 |
| 00023 |
[OASIS Issue Tracker] (OSLCCCM-24) Moving ChangeReques properties to subclasses could create incompatibilities |
OASIS Issues Tracker
|
2016-06-07 17:21 |
| 00024 |
[OASIS Issue Tracker] (OSLCCCM-23) oslc_cm:status range is String in CM 2.0 and can't be changed to oslc_cm:Status |
OASIS Issues Tracker
|
2016-06-07 17:24 |
| 00025 |
[OASIS Issue Tracker] (OSLCCCM-25) CM Section 4.5 Usage Identifiers should be deprecated |
OASIS Issues Tracker
|
2016-06-07 17:30 |
| 00026 |
Version Control Commit by jamsden |
[email protected]
|
2016-06-08 21:19 |
| 00027 |
Version Control Commit by jamsden |
[email protected]
|
2016-06-08 21:20 |
| 00028 |
Version Control Commit by jamsden |
[email protected]
|
2016-06-09 19:44 |
| 00029 |
Version Control Commit by ndjc |
[email protected]
|
2016-06-13 17:05 |
| 00030 |
Cancelled: OASIS OSLC-CCM TC Call |
OASIS Open
|
2016-06-14 15:25 |
| 00031 |
OASIS OSLC CCM TC meeting this week canceled |
Nicholas Crossley
|
2016-06-14 15:28 |
| 00032 |
Issue with vocabulary document |
Sarabura, Martin
|
2016-06-16 20:05 |
| 00033 |
Version Control Commit by jamsden |
[email protected]
|
2016-06-16 21:00 |
| 00034 |
Version Control Commit by jamsden |
[email protected]
|
2016-06-16 21:00 |
| 00035 |
Re: [oslc-ccm] Issue with vocabulary document |
Nicholas Crossley
|
2016-06-16 22:38 |
| 00036 |
Re: [oslc-ccm] Issue with vocabulary document |
Jim Amsden
|
2016-06-17 12:09 |
| 00037 |
Version Control Commit by jamsden |
[email protected]
|
2016-06-24 14:50 |
| 00038 |
[OASIS Issue Tracker] (OSLCCCM-22) Provide a way for a client to discover the configuration used to resolve a request |
OASIS Issues Tracker
|
2016-06-27 18:55 |
| 00039 |
[OASIS Issue Tracker] (OSLCCCM-22) Provide a way for a client to discover the configuration used to resolve a request |
OASIS Issues Tracker
|
2016-06-27 18:57 |
| 00040 |
[OASIS Issue Tracker] (OSLCCCM-21) Provide a way for a client to discover the default configuration for a given configuration provider |
OASIS Issues Tracker
|
2016-06-27 19:17 |
| 00041 |
[OASIS Issue Tracker] (OSLCCCM-14) How should previousBaseline behave when an intermediate baseline is deleted? |
OASIS Issues Tracker
|
2016-06-27 19:26 |
| 00042 |
[OASIS Issue Tracker] (OSLCCCM-10) Are multiple global configuration providers supported, and how do they discover each other? |
OASIS Issues Tracker
|
2016-06-27 19:29 |
| 00043 |
Version Control Commit by ndjc |
[email protected]
|
2016-06-27 19:32 |
| 00044 |
Confirmation of OASIS OSLC CCM TC meeting this Thursday |
Nicholas Crossley
|
2016-06-27 19:35 |
| 00045 |
Feedback on change management |
Sarabura, Martin
|
2016-06-28 16:37 |
| 00046 |
Re: [oslc-ccm] Feedback on change management |
Jim Amsden
|
2016-06-28 21:09 |
| 00047 |
[OASIS Issue Tracker] (OSLCCCM-24) Moving ChangeRequest properties to subclasses could create incompatibilities |
OASIS Issues Tracker
|
2016-06-29 21:18 |
| 00048 |
[OASIS Issue Tracker] (OSLCCCM-25) CM Section 4.5 Usage Identifiers should be deprecated |
OASIS Issues Tracker
|
2016-06-30 15:29 |
| 00049 |
[OASIS Issue Tracker] (OSLCCCM-25) CM Section 4.5 Usage Identifiers should be deprecated |
OASIS Issues Tracker
|
2016-06-30 15:34 |
| 00050 |
[OASIS Issue Tracker] (OSLCCCM-23) oslc_cm:status range is String in CM 2.0 and can't be changed to oslc_cm:Status |
OASIS Issues Tracker
|
2016-06-30 15:50 |
| 00051 |
[OASIS Issue Tracker] (OSLCCCM-23) oslc_cm:status range is String in CM 2.0 and can't be changed to oslc_cm:Status |
OASIS Issues Tracker
|
2016-06-30 15:54 |
| 00052 |
[OASIS Issue Tracker] (OSLCCCM-18) Change Management draft spec refers to obsolete OSLC SCM spec for change set type |
OASIS Issues Tracker
|
2016-06-30 15:58 |
