Community
Participate
Working Groups
Have an www.eclipse.org/downloads/earlyadopters or www.eclipse.org/earlyadopters page or earlyadopters.eclipse.org that is driven by RSS feeds from bug 205205 and bug 130150: INPUT: * Each project that wants to participate can register any number of Nick-format RSS streams (http://wiki.eclipse.org/index.php/Category:RSS) using their project meta-data in the portal. * At regular intervals (once an hour?), we'll check those RSS streams and recompute the page's database. PAGE: * By default the page will list the latest builds from the RSS streams in strict date-time order, most recent first. * Perhaps we should have a different default? Maybe the list should be sorted by the most popular downloads first, i.e., the most recent RSS build result for the most popular download first, then the most recent RSS build result for the second most popular download second, etc. * The page will have a set of dropdown filters or "buttons of popularity" at the top. These could filter by date, by type (milestone, I-build), by project/packaging (Eclipse RCP, Modeling Amalgation, ...), etc. These filters would filter the list. * The page would look more or less like the Eclipse Top-Level Project downloads page (well, except that it would Phoenix skinned) (http://download.eclipse.org/eclipse/downloads/) in that it would list Project, Build Type, Build Id, Date. OTHER: * The source RSS feeds would be listed on the page so that if someone wanted to subscribe to the feeds themselves, they would have one simple place to find the feeds. * The page will have a descriptive paragraph at the top talking about early adopters and helping to support the projects through community-based testing and that these are not real releases and that there could be unchecked IP in these downloads. * The main Eclipse downloads page will have a link to this page something like "Looking for bleeding edge builds for early adopters and tests?"
How does this relate to bug 126471? Seems like two of a kind to me.
Adding Phoenix as a cc
*** Bug 126471 has been marked as a duplicate of this bug. ***
I think the Developers tab is as close as it will get.