I'd like to discuss deprecation. The only Gump API we have today is the metadata. I'd like to formalize that [perhaps even with version attributes on major (distributed/community edited) elements], have XSD schema for validation. I'd also like to be able to migrate/enhance it it. (I've stored up numerous many metadata changes/extension I've not put in 'cos of Traditional.)
That said we have environment/usage (functionality) deprecations that could impact users. Two I'd like to perform (either as deprecations or out-and-out removals): 1) The use of 'pgrep' [unless we can figure out process groups]. 2) The use of 'forrest *batch call*' [the forrest folks have deprecated the interface we rely upon for this, and with batch & xdocs (forrest webapp) we have convoluted code.] (BTW: I'm not ready to be able to generate HTML raw, w/o forrest doing the cooking, although I'd like to get there one day.) I'd like to be able to deprecate functionality. Since we don't have releases (we work from CVS HEAD), I'd consider tagging the tree (so folks can freeze themselves at a certain point). Unfortunately this'll freeze the metadata, so doesn't seem too workable. So, what do folks think? How ought we proceed? regards, Adam -- Experience the Unwired Enterprise: http://www.sybase.com/unwiredenterprise Try Sybase: http://www.try.sybase.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
