avalon-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From nicola...@apache.org
Subject cvs commit: jakarta-avalon STATUS.txt
Date Sat, 01 Feb 2003 10:20:01 GMT
nicolaken    2003/02/01 02:20:00

  Modified:    .        STATUS.txt
  Log:
  Added latest proposals and votes.
  
  Revision  Changes    Path
  1.30      +29 -2     jakarta-avalon/STATUS.txt
  
  Index: STATUS.txt
  ===================================================================
  RCS file: /home/cvs/jakarta-avalon/STATUS.txt,v
  retrieving revision 1.29
  retrieving revision 1.30
  diff -u -r1.29 -r1.30
  --- STATUS.txt	1 Feb 2003 10:15:33 -0000	1.29
  +++ STATUS.txt	1 Feb 2003 10:20:00 -0000	1.30
  @@ -85,7 +85,34 @@
   
         
   Pending issues:
  -      
  +
  +    o nicolaken: Deprecation policy
  +      Removing deprecated classes between major versions is a safe bet.
  +      Between point versions it's a possibility.
  +      Between fixes it's an error.
  +      I'd suggest the following as a guideline:
  +       - deprecating classes results in @deprecated being added
  +       - in the next minor point release, they are moved to a
  +         deprecated source tree for the component that is compiled
  +         *after* the main ones, so that we are sure that /we/ do not
  +         rely on those.
  +       - in the major releases the classes can be removed with a vote.
  +
  +    o nicolaken: Previously, I had asked that the maven descriptor in 
  +      the avalon CVS not be in the main dir, not to confuse our users.
  +      But it's also possible that we just don't include it in the
  +      releases.
  +      Given that there is much discussion on things that developers 
  +      don't even know what is about, I think it's in the best 
  +      interest of all Avalon that build tools alternative to Ant 
  +      are included in the correct places in our projects so that 
  +      all developers can evaluate them and decide on merit rather 
  +      than feeling.
  +      This of course also means that we accept the POMs from Jason,
  +      and can commit any other build system too for comparative 
  +      evaluation.
  +      What do you guys think, is this reasonable?
  +
       o [VOTE] Do you want that we discuntinue Excalibur CLI in favor of 
         Jakarta Commons CLI?
   
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: avalon-cvs-unsubscribe@jakarta.apache.org
For additional commands, e-mail: avalon-cvs-help@jakarta.apache.org


Mime
View raw message