axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From as...@apache.org
Subject cvs commit: xml-axis-wsif/java/doc RELEASE_TASKS.txt
Date Mon, 13 Jan 2003 17:24:19 GMT
aslom       2003/01/13 09:24:19

  Modified:    java/doc RELEASE_TASKS.txt
  Log:
  updated release plan with some tasks moved to post-2.0 release
  
  Revision  Changes    Path
  1.17      +44 -32    xml-axis-wsif/java/doc/RELEASE_TASKS.txt
  
  Index: RELEASE_TASKS.txt
  ===================================================================
  RCS file: /home/cvs/xml-axis-wsif/java/doc/RELEASE_TASKS.txt,v
  retrieving revision 1.16
  retrieving revision 1.17
  diff -u -r1.16 -r1.17
  --- RELEASE_TASKS.txt	7 Jan 2003 15:23:02 -0000	1.16
  +++ RELEASE_TASKS.txt	13 Jan 2003 17:24:19 -0000	1.17
  @@ -1,50 +1,47 @@
   RELEASE PLAN for Apache WSIF 2.0: 
  -* VERY IMPORTANT: _all_ pending tasks for final release and RCs must be in RELEASE_TASK.txt
  - - anybody waorking on releease should put there what is happening (including bug fixes)
  - (it is in CVS in doc/ subdirectory)
  -* next IRC chat on Moday Jan 13th - we keep discussing about release on mailing list
  -* RC1 on friday and necxt RC releases  later final releease in mid-January shortly after
Mon 13)
  -* final RC is converted to final relelase in few weeks
  +* next IRC chat on Thursday Jan 23th - just before final release (if RC2 decided to be
final)
  +* confirm the dates for the RC2 and the 2.0
  +* RC2 ASAP (just cut it - Tuesday/Wednesday would be good)
  +* schedule a 2.0 release for say Thursday/Friday next week, if that is ok?
  +* after that do a 2.01 or 2.1 ASAP 
  +	put in some bugs Ant has been fixing related to doc style support, 
  +	put the Forrest-ed web pages
  +	users feedback ....
   * TASK to keep discussing best build structure and how to make it easy
    - also tentatively Ant in next RC will move all jar files to one lib directory
   * keep updating list tof changes in doc (including new additions, bug fixes etc.)!
  -* maybe aslo remove some of "high priority" tasks as nobody signed for them (or seems to
be working on them ...)
  +* moved to next release some of "high priority" tasks that nobody signed for them (or seems
to be working on them ...)
   * release often after 2.0 (including bug fixes and doc changes)
     baseline would be 2.0.x then if we really have something significant change the 0
  +* VERY IMPORTANT: _all_ pending tasks for final release and RCs must be in RELEASE_TASK.txt
  + - anybody working on releease should put there what is happening (including bug fixes)
  + (it is in CVS in doc/ subdirectory) - finished tasks will beused for release notes
   
  -TASKS for RC release (high priority):
  -* put HERE all remaining tasks, for example: remaining critical bugs including URLs such
as:
  -  Bug 13646 WSIFOperation_ApacheAxis fails to set up Call's Parameter list http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13646
  -* check current RC1 release (when it is out) and report problems
  +TASKS for 2.0 release (high priority):
  +* check current RC1 release (soon RC2) and report problems
     ESPECIALLY: look on how build scripts work (including build.* and classpath.*) and on
lib/subdires structure
     also consider how to structure jar dependencies (subdirectories or everything in one
directory) 
  -* fix nightly builds (check how they are created and how they are propagated?)
  -* add sample to demonstrate how to use WSIF async operations [as requested by Jeff Greif]
  -* [ant] finish fixing problems in AXIS provider as described in bugzillas to be raised
  -* regularly monitor bugzilla bugs and decide as appropriate if fix should be included in
RCx or final
  +* put HERE all remaining tasks, for example: remaining critical bugs including URLs such
as:
  +  Bug 13646 WSIFOperation_ApacheAxis fails to set up Call's Parameter list http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13646
  +  and regularly monitor bugzilla bugs and decide as appropriate if fix should be included
in RCx or final
  +* checkproblem with build srcdist and zip taks that throws NPE (at least on IBM JDK)
  +* piotrp? fix build for JCA samples 
  +* documentation: we have most of it now but some reading/checking will only make it better
  +* we need more people to check documentation
  +* document each sample (Nirmal is doing great work here both writing and documenting samples)
  +* alek: check initial readme/overview docs
  +* alek: check sample documentation for simplesoap and run sample
  +* alek: check sample documentation for complexsoap and run sample
   * alek: check if we can distribute all jar files
   * alek: JAVAMAIL/JAF issue especially in context of http://java.sun.com/products/javamail/FAQ.html#free

   	and http://java.sun.com/products/javamail/LICENSE.txt 
     (that would greatly simplify WSIF installtion if activation.jar and mail.jar coul dbe
included)
     (note, you shouldn't need these jars to run WSIF unless you really are using attachments
now)
  -* samples (we need to decide what does in and what is not to be in release -as nobody works
on JCA or EJB samples AFAIK)
  -* samples are crucial to show what WSIF can do and how to use it
  -* we need sample for EJB
  -* we need sample for JMS/SOAP
  -* piotrp: expand J2C provider sample. The sample currently included in a complete 
  +* DONE piotrp: expand J2C provider sample. The sample currently included in a complete

     rar file including all the sources of the sample J2C connector (MyEIS) using wsif j2c
provider.
     The script to build rar from the source as well as sample proxy that uses MyEIS connector
     to execute interaction with the back end. 
  -* documentation: we have most of it now but some reading/checking will only make it better
  -* we need more people to check documentation
  -* document each sample (Nirmal is doing great work here both writing and documenting samples)
  -* alek: check initial readme/overview docs
  -* alek: check sample documentation for simplesoap and run sample
  -* alek: check sample documentation for complexsoap and run sample
  -* check sample documentation for localjava and run sample
  -* document WSIF code and give higher level docs than just Javadocs
  -* if possible no code changes until we have this release finished unless it is bug fix
...
  -* make sure that all dependencies are documented
  +* DONE nirmal we need sample for EJB
   * DONE nirmal need sample for simple soap
   * DONE nirmal need sample for soap with comlex types
   * DONE nirmal documented simple soap sample
  @@ -57,8 +54,23 @@
   * DONE [alek] simplify wsif.css
   * DONE [alek] check in JAR files that we know WSIF works OK with LICENSE and README(and
can be checked in)
   * DONE [alek] test process to build binary and source distributions
  -* [nirmal + alek] document how to run samples (step by step)
  -* [nirmal + alek] document how to build (step by step)
  +* DONE [nirmal + alek] document how to run samples (step by step)
  +* DONE [nirmal + alek] document how to build (step by step)
  +
  +----- Post 2.0 release
  +
  +TASKS for next release (high priority):
  +* some limitations on DOC style w/attachments which Ant is working to 
  +* fix nightly builds (check how they are created and how they are propagated?)
  +* add sample to demonstrate how to use WSIF async operations [as requested by Jeff Greif]
  +* [ant] finish fixing problems in AXIS provider as described in bugzillas to be raised
  +* [ant] working on removing some limitations on DOC style w/attachments 
  +* samples are crucial to show what WSIF can do and how to use it
  +* we need sample for JMS/SOAP
  +* check sample documentation for localjava and run sample
  +* document WSIF code and give higher level docs than just Javadocs
  +* if possible no code changes until we have this release finished unless it is bug fix
...
  +* make sure that all dependencies are documented
   
   TASKS (medium priority):
   * [owen] Convert documentation to use Forrest
  
  
  

Mime
View raw message