Brett Porter a écrit :
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)
agreed
- SCM-156, 157, 158: TCK tests for various providers. Ties in to the above.
we can't implement TCK tests for all providers without access to all SCM tools.
And it seems that contributors on providers without TCK implementation doesn't want or don't find time to do it, maybe it will be different when the TCK will be documented (I don't know yet how to
document it)
- SCM-18: it seems some commands are not currently implemented in some
providers?
Yes. I don't think the implementation of all commands is a requirement for a
release.
1. If we don't allow to release without all commands, I'm not sure contributor
will contribute more and they probably keep their provider private with what
they need.
2. it isn't possible to implement all commands in all providers because some
command aren't supported by some SCM tool
3. without contribution or an access to a SCM tool, we can't implement missing
commands
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
if we want it before 1.0, it would be good to implement it in a beta, so it
will can be tested before the 1.0 release
I'm not sure we'll can do it easily in all providers without contribution.
Probably possible if we keep in API the current behaviour.
- SCM-133: API clean up around repositories
same comment for a new beta, but I'm thinking to a big API change for Maven-SCM
2 that will simplify provider implementation and will allow specific SCM
options (I'll write a design doc about that later)
Low priority:
- SCM-243: 'X' is treated as unknown in SVN. Seems like a simple fix,
might be worth doing.
Yes it's a simple fix I can include in the release. I'll like to parse svn
properties changes too, but probably later.
I'll also review the docs.
I think it's critical we have the testing in order before doing the 1.0
release - wdyt?
I'll move all IT tests under a src/it directory in each provider and try to
document the TCK ASAP.
Emmanuel
- 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
