Just to keep everyone in sync with the progress/tasks
towards our AR1 release...

-Jim

------------------------------------------------------------------------ -----
       Apache Incubator River Project - "AR1" Release

SET
====
* Goal:  initial release from River project, integrating the starter kit
  and serviceui contributions

* Should we go with the current starter kit release bundle structure?
   -> decided yes, for this release

* What kind of development process do we need?  JIRA issues for
   all changes?  code reviews?
   -> vote approved basic dev process (including: tracking issues and
        changes, issue discussions, code reviews, testing, and handling
        security -related issues)

* Bundle starterkit and serviceui in the release bundle?
   (assuming yes)  How should serviceui fit in?
-> JIRA-264 moving the service ui classes directly into the starter kit tree, including them in (jsk)-lib.jar and (jsk)-dl.jar and keeping
        the serviceui.jar around for at least a release or two.
        [Frank]

* Some (build) issues around outrigger sources to work
   -> JIRA-263  remove logstore as part of the outrigger build work
        for AR1
        [Frank]



IN PROGRESS
============

* Service UI Spec/Doc contribution (to get in release)
   -> JIRA-262   ServiceUI Specification
        [Bill]

* Update web:
      River project area
            <http://incubator.apache.org/river/>
      River Incubator Project Status page
            <http://incubator.apache.org/projects/river.html>
        [Jim]

* Name, Version, release bundle, top-level installation directory: ?
   -> JIRA-266
- Name (used in text on web page, and inside release): Apache River
       - Version #:  2.1.1
       - Name of downloads/distributions:
               apache-river-2.1.1-incubating-bin.{tar/zip}
              apache-river-2.1.1-incubating-src.{tar/zip}
       - Top-level install directory:  apache-river-2.1.1/
- jar package names unchanged (jsk-, serviceui-) for this release
       [Frank]

* Documentation in release
  -> JIRA-267
        - update documentation in release for:
             Name, Version #, download name, install directory
        [ ? ]

* Javadoc and API docs/specs on site
   ->  JIRA-268
         - provide Javadoc available for viewing on site as well as
           in a separate download
         - provide API docs/specs available from site (ala something
similar to: http://java.sun.com/products/jini/ 2_1index.html
        [ ? ]


OPEN
=====
* What kind of testing do we need?

* Apache incubator release process (export, PPMC approval,
   general approval, etc)

* Handling cryptography within the release
   (see:   <http://www.apache.org/dev/crypto.html> )

------------------------------------------------------------------------ -----

Reply via email to