[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [dsdp-tm-dev] ready to begin 2.0?
|
Hi Dave,
These are good questions.
Let's discuss these in the committer meeting tomorrow.
For now, I would like everyone to focus on the unit tests.
We MUST increase our test coverage in order to reduce the time wasted
through manual tests, increase our stability, and insure that code /
implementation changes keep the API contracts intact.
So, everyone - until this is discussed and decided among the committers,
please don't break the APIs and start implementing more test cases
instead. You could start e.g. with a bug that needs to be fixed: write a
test case that fails for this bug, then fix the bug and ensure that the
test case runs ok.
Thanks
Martin
David Dykstal schrieb:
Martin -
I've stored up some API changes that would need to go into our 2.0 stream.
I can begin these today, but want to make sure that the head stream is
ready to be used for 2.0. I would rather these get into the stream sooner
than later so that folks have time to adjust. I expect most of these to be
quite small. Do you think we are ready to do this?
Also, as we modify the code base for 2.0, should the developers making the
changes assume the responsibility for updating the version numbers of the
appropriate plugins and features, or should this be centralized?
_______________________
David Dykstal
david_dykstal@xxxxxxxxxx
_______________________________________________
dsdp-tm-dev mailing list
dsdp-tm-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dsdp-tm-dev
--
Martin Oberhuber
Wind River Systems, Inc.
Target Management Project Lead, DSDP PMC Member
http://www.eclipse.org/dsdp/tm
