Summary: | Intent | ||
---|---|---|---|
Product: | [Tools] CDT | Reporter: | Anne Jacko <anne.jacko> |
Component: | cdt-releng | Assignee: | cdt-releng-inbox <cdt-releng-inbox> |
Status: | RESOLVED FIXED | QA Contact: | Doug Schaefer <cdtdoug> |
Severity: | normal | ||
Priority: | P1 | CC: | cdtdoug, david_williams |
Version: | 6.0 | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Bug Depends on: | |||
Bug Blocks: | 252790 |
Description
Anne Jacko
2008-11-03 18:09:15 EST
Just testing the Q&A Contact field. Test finished. So, ... shouldn't this be marked "fixed"? No one on the CDT community has contributed to this "requirement". (In reply to comment #4) > No one on the CDT community has contributed to this "requirement". > So, to be clear, you do not have a project plan in the standard format? Or, you do not intend to be part of the Galileo Release? never mind, I can see myself you don't have a standard plan http://www.eclipse.org/projects/project-plan.php?projectid=tools.cdt But do have a wiki plan (for Galileo) at http://wiki.eclipse.org/index.php/CDT/planning I made a silly XML plan file to meet this requirement. Frankly David, none of the CDT committers care about these Galileo requirements. The only thing vendors want is a guaranteed release date for planning and to be released at the same time as the other components they build products with. I made a silly XML plan file to meet this requirement. Frankly David, none of the CDT committers care about these Galileo requirements. The only thing vendors want is a guaranteed release date for planning and to be released at the same time as the other components they build products with. (In reply to comment #8) > I made a silly XML plan file to meet this requirement. > Thanks for your token compliance. I've obviously done a bad job of communicating what this was about. The standard format aspect of the requirement is not a simultaneous release requirement, but a Board required EMO requirement stated in the Eclipse Development Process and is now part of any project release. See http://www.eclipse.org/projects/dev_process /development_process.php#5_Roadmap_Process "...each Project is required to create a transparently available Project Plan in an EMO-defined file format that meets the following criteria..." Where 'ya been? :) (See bug 215301). And the _simultaneous release_ part of this 'intent' requirement, was to do that EMO requirement by the 4th milestone ... and to use this bug simply to document compliance with the Development Process. > Frankly David, ... I look forward to many frank discussions with you on this and related topics. |