Jim Hurley wrote:
We did have to touch on this in our project proposal (see:
<http://wiki.apache.org/incubator/RiverProposal>, "(2) identify
the initial source from with the project is to be populated". We
had identified the Starter Kit (and link to the latest published
version). Although we did not explicitly state v2.1, it was certainly
meant to be implied that it would be the latest published version.
We also identified ServiceUI and a link to the latest published
version (v1.1a).
Finally, we identified the QATests project, which contained the
tests and harness we used for testing releases of the Starter Kit.
You are right.
4) Outstanding issues against JTSK version 2.1.1
I'm not sure of the logistics for getting issues moved from our
internal system to JIRA, but it's something we'll need to look
at relatively soon. We certainly want and expect to get the major
issues we have logged moved over.
JIRA supports various type of imports see
http://www.atlassian.com/software/jira/docs/v3.7.1/, but the list of
public open issues for Jini is 206 in the Sun bug database. It might be
faster to do it by hand as that will also allow you to assign it to
proper components, and to the type of levels we might decide upon. You
can even play with the text decoration features so you can make
beautiful bugs ;-)
--
Mark
