Deprecation

["Adam R. B. Jack" <aj...@trysybase.com>]

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: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org

Re: Deprecation

[Steve Loughran <st...@iseran.com>]

Adam R. B. Jack wrote:
> I'd like to discuss deprecation.

> 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.]


This raises a question with me: how should I be using Forrest in an 
ant/gump build process to generate documentation artefacts?

-steve

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org

Re: Deprecation

[Stefan Bodewig <bo...@apache.org>]

On Wed, 16 Jun 2004, Adam R. B. Jack <aj...@trysybase.com> wrote:

> I guess I could then teach gumpy.py to get from a TAG, and then
> overlay metadata from CVS HEAD. Not sure if CVS would be too happy
> with that (due to the overlap).

CVS will work OK as long as all files inside a single directory come
from the same tag.  So using projects, profile and repository from
HEAD and everything else from a tagged version should be possible.

Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org

Re: Deprecation

["Adam R. B. Jack" <aj...@trysybase.com>]

> > Unfortunately this'll freeze the metadata, so doesn't seem too
> > workable.
>
> Only tag the python directory?

Assuming I added this logic to templates (and other non-metadata areas), to
get all of Gumpy, I guess I could then teach gumpy.py to get from a TAG, and
then overlay metadata from CVS HEAD. Not sure if CVS would be too happy with
that (due to the overlap).

Hmm, getting eager for the re-organization that retiring traditional might
allow...

regards,

Adam


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org

Re: Deprecation

[Stefan Bodewig <bo...@apache.org>]

On Mon, 14 Jun 2004, Adam R. B. Jack <aj...@trysybase.com> wrote:

> 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).

Good idea.

> Unfortunately this'll freeze the metadata, so doesn't seem too
> workable.

Only tag the python directory?

Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org