[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[eclipse.org-architecture-council] [Bug 279539] New: [api] Deprecation: Should we require 2 years lead time from all train projects?
- From: bugzilla-daemon@xxxxxxxxxxx
- Date: Mon, 8 Jun 2009 20:00:36 -0400 (EDT)
- Delivered-to: firstname.lastname@example.org
Product/Component: Community / Architecture Council
Summary: [api] Deprecation: Should we require 2 years lead time
from all train projects?
OS/Version: Windows XP
Component: Architecture Council
CC: Olivier_Thomann@xxxxxxxxxx, jeff@xxxxxxxxxxxxxxxxx,
Depends on: 261544
+++ This bug was initially created as a clone of Bug #261544 +++
In the AC call on May 14, it was brought up that the single most important
point about API deprecation is whether we require all release train projects to
allow for 2 years lead time minimum before actually removing deprecated API.
I'm splitting out this discussion into a separate bug because it is a separate
aspect of the API deprecation discussion: "Indicate that it is not just idle
talk but will have consequences".
Please file your comments, thoughts, arguments and concerns here.
See bug 261544 comment 0 for an overview on issues related to deprecation.
Configure bugmail: https://bugs.eclipse.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.