Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cross-project-issues-dev] Re-spin process / DSDP-TM Re-spinrequest

Hi John and all,
 
I'm fine with distributing TM 2.0.0.1 via our project update site only, and wait for Europa SR1 before it gets pushed out to Europa - if this is what the community wants.
 
I was trying to think like a commercial vendor in that case, and since the two discovered bugs could lead to loss of data in our case, I felt responsible for avoiding such loss at the client's side if anyhow possible. If TM / Europa were a commercial product, I'd seriously consider updating the downloadable bits, though perhaps not stop ship already manufactured CD's.
 
It's up to us all to decide what kinds of patches we'd like to see pushed to Europa before the Fall Maintencane release or not. That's why I consider this an extension of our Ramp Down Policy, and we all need to assess any patches with respect to appropriateness and risk.
 
I agree that it's easier to explain everybody it's recommended to "Check for Updates" once rather than explaining everybody what has changed in Europa day X since Europa June 29. (It's just that I personally felt "Check for Updates" doesn't really work too well and it's PAINFULLY slow so I'd prefer updating the bits).

Cheers,
--
Martin Oberhuber
Wind River Systems, Inc.
Target Management Project Lead, DSDP PMC Member
http://www.eclipse.org/dsdp/tm


Back to the top