[mylyn-dev] Bugzilla conventions, Eclipse versions

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[mylyn-dev] Bugzilla conventions, Eclipse versions

From: Steffen Pingel <steffen.pingel@xxxxxxxxxxx>
Date: Thu, 12 Mar 2009 23:24:15 -0700
Delivered-to: mylyn-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/mylyn-dev>
List-help: <mailto:mylyn-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/mylyn-dev>, <mailto:mylyn-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/listinfo/mylyn-dev>, <mailto:mylyn-dev-request@eclipse.org?subject=unsubscribe>

We had a brief discussion about two conventions that are relevant to contributors and committers on today's conference call:

* The Bugzilla severity "trivial" is used to track easy to implement enhancements rather than cosmetic problems. Apart from that we have standardized on the Eclipse.org bug status conventions: https://bugs.eclipse.org/bugs/bug_status.html#bug_severity.

* The source in cvs head is always targeted at the latest Eclipse milestone (i.e. 3.5M5 at the moment). If you are using an older Eclipse version API tooling problems and other warnings maybe reported.

Steffen

--
Steffen Pingel
Committer, http://eclipse.org/mylyn
Senior Developer, http://tasktop.com

Prev by Date: [mylyn-dev] conference call today, 10am Pacific
Next by Date: [mylyn-dev] Reg Internal browser
Previous by thread: [mylyn-dev] Upgrading Trac from 0.10.4 to 0.11 - which Mylyn issues are to be expected
Next by thread: [mylyn-dev] Reg Internal browser
Index(es):
- Date
- Thread

Breadcrumbs