Hi all.
Apropos of the conversation this subject line evolved from, I was
thinking about this from Marcus:
"Pharo will do it completely differently: release often, integrate as
soon as possible, keep the bugtracker down to managable levels and do
not be religiously backwards-compatible."
This lead me to think various comments recently from Stef (I think - I
apologise if I'm miss-paraphrasing, but I can't find the exact
messages) about how to tell which tests have failed/passed etc as the
versions go by.
I submit that in order for early integration and regular release to
work, it needs to be an "all tests green or nothing" situation. Of
course, it's very difficult to make sure all the tests are passing,
but I just ran *all* the tests in the system, and there's only one
error and one failure.
This is fantastic work! Not only that but the error is down to
BookMorph (due for removal iirc?) and a #printString problem with
Array, the latter of which *has* to be simple to fix.
If this level of passing tests (or even better, all of them; not
necessarily possible as various things like EToys are stripped out I
imagine) is maintained, there's no need to tell what tests have
changed state from version to version; moreover Pharo will be far the
better for it, imho.
Just my €0.02 :)
Cheers,
Simon
******************************************************************************************************************************************
This email is from Pinesoft Limited. Its contents are confidential to the
intended recipient(s) at the email address(es) to which it has been addressed.
It may not be disclosed to or used by anyone other than the addressee(s), nor
may it be copied in anyway. If received in error, please contact the sender,
then delete it from your system. Although this email and attachments are
believed to be free of virus, or any other defect which might affect any
computer or IT system into which they are received and opened, it is the
responsibility of the recipient to ensure that they are virus free and no
responsibility is accepted by Pinesoft for any loss or damage arising in any
way from receipt or use thereof.
*******************************************************************************************************************************************
Pinesoft Limited are registered in England, Registered number: 2914825.
Registered office: 266-268 High Street, Waltham Cross, Herts, EN8 7EA
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
