RELEASE PLAN for Apache WSIF 2.0: * 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.)! * 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 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) * 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) * 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. * 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 * DONE nirmal documented complex soap samples * DONE Jeremy: Forrest proposal check in into proposals directory in CVS * DONE [alek] get out an intial (alpha) release today! * DONE [Jeremy Sat 11a GMT (6am EST)] fixing problem with text files marked by Eclipse as binary in CVS * DONE [alek] but will need mroe work [alek] split README.html into smaller pices and make it addressing two communities: WSIF users and WSIF developers; README.html right now is kind of mixed up * 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 * DONE [nirmal + alek] document how to run samples (step by step) * DONE [nirmal + alek] document how to build (step by step) * DONE owen: fix documentation/web pages - we need to be constistant with file extensions - always use .html rather than .htm. This is currently causing broken links!! See bugzilla bug # 15691 ----- 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 * [owen] Convert web pages to use Forrest * [owen] Automatically generate web site from CVS * [jeremy] automatic generation of javadoc API on website * write/test sample that uses xmethods WSDL (DynamicInvoker + stub) * document how to run tests (step by step) * get the link to the API javadoc off the home page working * work on developer guide that explains what different methods on WSIFOperation are doing with exampels (such as executeRequestResponseAsync ...) * check (and edit if necessary) Javadoc on the main WSIF API (org.apache.wsif) * check (and edit if necessary) Javadoc on util and base (WSIFUtils and org.apache.wsif.base) TASKS (lower priority) * check (and edit if necessary) Javadoc for AXIS provider * check (and edit if necessary) Javadoc for Apache SOAP provider * check (and edit if necessary) Javadoc for JMS/SOAP provider * [piotrp] check (and edit if necessary) Javadoc for J2C provider * DONE documentation for J2C binding * improve Javadoc for Java provider * improve Javadoc for EJB provider * figure out how to make JMS sample to use as simple as possible maybe with some locally started JMS serivce ... * document how to run sample interacting using JMS * DONE figure out how to make JCA sample to use as simple as possible maybe with some local JCA connetor, the sample will run against MyEIS Connector which is included itself as a sample. * [piotrp] document how to run samle interacting using JCA * document how to run samle interacting using EJB * sample showing customisation of WSIF: how to write simple code to pick your preferred port at runtime LATER * [nirmal, alek, Jeremy ???] for sampels it would be good to have something pernament for EJB/JMS using Open Source EJBs/JMS (such as JBoss), etc. can we do that? is that feasible? * [alek ...] LATER: modularisation * allow compiling with only AXIS jars on CLASSPATH (generate only Apapche Axis SOAP provider)