You are missing the whole point here. The thread is not about delivery of patches, it is about version control. We got a eval version of the SmartGWT SDK into our product stream.
While tracing down the issue, it was discovered there is no traceability of the Isomorphic software back to the manufacturer (which is you guys). As Isomorphic support has indicated, you currently expect the customer (us) to manually mange the traceability and versioning of the Isomorphic software ourselves (the overall manual operation and the lack of traceability of the SDK delivery mechanism is probably why we got an eval copy leaked into our source control in the force place).
The concern with this is: ISO 9000-3, 4.8 Product Identification and Traceabilty
Based on the discussion on this thread, it is currently not possible to identify and traceback with accuracy the Isomorphic software back to the vendor (you guys).
Having the customer (us) hack in a standards compliant version control scheme for Isomorphic is a large overhead on our part and most likely not accurate or audit passable since we are black box proxying a version control scheme on software we don't even control or own.
Once again, we don't need any changes to our CM process since it is ISO compliant already. What we are having issues is the SDK deliverables that we get from Isomorphic are not ISO compliant.
While tracing down the issue, it was discovered there is no traceability of the Isomorphic software back to the manufacturer (which is you guys). As Isomorphic support has indicated, you currently expect the customer (us) to manually mange the traceability and versioning of the Isomorphic software ourselves (the overall manual operation and the lack of traceability of the SDK delivery mechanism is probably why we got an eval copy leaked into our source control in the force place).
The concern with this is: ISO 9000-3, 4.8 Product Identification and Traceabilty
Based on the discussion on this thread, it is currently not possible to identify and traceback with accuracy the Isomorphic software back to the vendor (you guys).
Having the customer (us) hack in a standards compliant version control scheme for Isomorphic is a large overhead on our part and most likely not accurate or audit passable since we are black box proxying a version control scheme on software we don't even control or own.
Once again, we don't need any changes to our CM process since it is ISO compliant already. What we are having issues is the SDK deliverables that we get from Isomorphic are not ISO compliant.
Comment