Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 335374 - Update plan to RHEL 6
Summary: Update plan to RHEL 6
Status: CLOSED DUPLICATE of bug 341264
Alias: None
Product: Platform
Classification: Eclipse Project
Component: PMC (show other bugs)
Version: 3.7   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: 3.7 M7   Edit
Assignee: John Arthorne CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-25 15:08 EST by John Arthorne CLA
Modified: 2011-04-04 13:06 EDT (History)
4 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description John Arthorne CLA 2011-01-25 15:08:40 EST 
In bug 333116 Martin asked:

... RHEL5-x64 is one of the widely used Linux distros, and RHEL6
is likely becoming one. Could these be promoted to Reference Platform?
Comment 1 John Arthorne CLA 2011-01-25 15:17:51 EST 
There are really three questions here:

- Do we add RHEL 6 as a reference platform
- Do we remove RHEL 5
- Do we remove RHEL 4

I thought we typically just listed the "latest" release of a given OS so I'm not sure why we have RHEL 4 listed at all. Was there an issue at some point in the past about 64-bit support on RHEL 5?

I think the default decision should be add RHEL 6 and remove 4/5. For SLES and Ubuntu we only list the latest one.

I checked with SWT and they haven't got a machine with the final RHEL 6 release yet, although they have done some testing on a beta. We should at least wait for them to do more thorough testing on RHEL 6 final before we move up.
Comment 2 John Arthorne CLA 2011-04-04 13:06:45 EDT 
At the January 21 PMC meeting we agreed to change the RHEL reference platform to 6 (dropping RHEL 4 and 5).

http://wiki.eclipse.org/Eclipse/PMC

I will update this in the next plan revision. Since this is already mentioned in bug 341264 I will mark this as a dup.

*** This bug has been marked as a duplicate of bug 341264 ***