| Re: [modeling-pmc] Modeling Project Overhaul |
|
With the new Project Management Infrastructure [1], we have a
first-class concept of releases that capture a lot of information.
I'd like to add a means of specifying some number of update sites
and other downloads. Is that enough? i.e. is it enough to just allow
a committer to associate a couple of links (with optional
annotation) to the release record? e.g. Here's what the 4.2 release looks like for BIRT: [2]. I'm hoping that the convenience of being able to specify release information in this way will encourage projects to actually specify release information. If this works, then we'll be able to consistently display this information for all projects. There is an ongoing discussion regarding standard download pages [3]. Anything to add to this discussion? Wayne [1] [2] http://projects.eclipse.org/projects/birt/release/4.2.0 [3] https://bugs.eclipse.org/bugs/show_bug.cgi?id=207108 On 07/16/2012 12:35 PM, Ed Willink wrote: IMHO, most Modeling projects share the quite good modeling infrastructure for download pages that allows sensible categorisation, ordering and archiving with extra surrounding notes, whereas most non-Modeling projects that I try to download from have poor to non-existent downloads pages. Projects that have 'better' modeling pages for users provide what again IMHO are very poor inconsistent pages for Eclipse committers, and I suspect committers are the main consumers of download pages. It would be good to have a common Foundation infrastructure that automatically presented downloads and update pages; provided projects follow the naming practices that are already shared across many projects. |