[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #30474] obsolete environment still set by default ... shouldn't be
|
From: |
Richard Frith-Macdonald |
|
Subject: |
[bug #30474] obsolete environment still set by default ... shouldn't be |
|
Date: |
Sun, 18 Jul 2010 21:08:26 +0000 |
|
User-agent: |
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_4; en-us) AppleWebKit/533.16 (KHTML, like Gecko) Version/5.0 Safari/533.16 |
Follow-up Comment #2, bug #30474 (project gnustep):
In base I use a rule of a complete release cycle (excluding bugfix
releases).
ie if something is deprecated in one release, it has to continue to exist
until the next release. Since we actually tend to do non-bugfix releases
about once a year, that's on average an 18 month process from the point of
deciding to deprecate something ...
a. decide to deprecate
b. 6 months later the release in which the feature is formally deprecated is
made
c. a year after that the release in which the feature is removed is made.
So even if you don't track svn or bugfix releases, you still get at full
release cycle (about a year) in which to deal with any changes.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?30474>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/