[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [eclipse-dev] Platform Planning Meeting post-notes, Oct 1, 2008
|
This is probably obvious but I'll say it anyway...
for an ordinary user, "RT>Equinox>p2" is made up entirely of jargon terms
that they're probably unfamiliar with, while "Eclipse>Platform>Update" is
quite self-explanatory. I suspect that just marking Update as "legacy" or
"deprecated" will just cause frustration for people trying to report or search
for bugs.
There needs to be some clear way to discover the new
category, not just a way to dissuade from the old category. I am not sure,
within the webmasters' bag of tricks, what that might be, but there needs to be
one.
The underlying problem here is that we are categorizing
bugs according to architectural details rather than functionality - an ordinary
user doesn't think "I'm going to try to use p2 now", they think "I'm going to
try to update." Of course there are some good reasons for that, not least
that bugs are for teams and teams work on components while functionality
crosscuts components. I know that the bug entry wizards are one attempt to
address this.
-walter
To clarify the bugzilla issue, the
problem is that many bugs are being reported against
Eclipse>Platform>Update rather than RT>Equinox>p2. The
Eclipse>Equinox product was removed from bugzilla so there is no confusion
for other parts of Equinox. I'm going to investigate getting the Update
component marked as "legacy" or "deprecated" to avoid the confusion.
For EasyMock, I have added some details
on the wiki here: http://wiki.eclipse.org/Automated_Testing#Using_EasyMock.
Unless your tests aleady require Java 5, I suggest holding off on adopting
EasyMock until we move our testing completely to Java 5+.
John
