Can we please deprecate the 'version' argument of registerStep?
This is the interface description:
o 'version' is a string for comparing versions, it is preferred to
be a yyyy/mm/dd-ii formatted string (date plus two-digit
ordinal). when comparing two version strings, the version with
the lower sort order is considered the older version.
- Newer versions of a step supplant older ones.
- Attempting to register an older one after a newer one results
in a KeyError.
AFAICT this feature was never used, became inoperable after adding
extension profiles and makes absolutely no sense in a global step
registry. Originally steps were linked to specific files in the profile,
the 'version' described the version of the XML files.
A profile version can now be set in metadata.xml. AFAICS this supersedes
the import step version approach.
Am I missing something?
no, you're not. i agree that the idea as it was originally intended no longer
makes much sense. but i think the underlying idea (i.e.that there should be
some way to indicate that changes have happened at a more finely-grained level
than the entire profile) is still a good one. i'd love to have some UI that
indicates what exactly changed within a profile from one version to the next,
so i can selectively choose which configuration to reapply, minimizing the
possbility of side effects.
and i want a pony.
+1 to the deprecation.
Zope-CMF maillist - Zope-CMF@lists.zope.org
See http://collector.zope.org/CMF for bug reports and feature requests