I think it's definitely time for another beta ASAP.
For 1.0, I'd still like to review (if not include) the following JIRAs.
High priority:
- SCM-17: I think the test structure needs some review, and we need
to ensure all unit tests run fast and without the software installed.
The TCK should be used to execute as integration tests when the
software is installed. I think this sets us in a good position for a
more stable API and the ability to have quality providers (per the
other discussion on the list)
- SCM-156, 157, 158: TCK tests for various providers. Ties in to the
above.
- SCM-18: it seems some commands are not currently implemented in
some providers?
Note: I'm happy to cut down the number of providers for the 1.0
release (and version the others as beta or have a larger sandbox) if
that's what it takes. That would be more around the model of
separated releases though.
Medium priority (because they might change the API it could be better
to do before 1.0):
- SCM-21: separate revision and tag handling
- SCM-133: API clean up around repositories
Low priority:
- SCM-243: 'X' is treated as unknown in SVN. Seems like a simple fix,
might be worth doing.
I'll also review the docs.
I think it's critical we have the testing in order before doing the
1.0 release - wdyt?
- Brett
On 28/03/2007, at 2:37 AM, Emmanuel Venisse wrote:
Hi,
Now, we have only one issue to fix and all issues assigned to 1.0
will be fixed :)
I added two development guide in the site, it would be cool if you
can look at it.
Emmanuel
