|
I'd rather not include another reference to a specific
implementation in a policy document, but being explicit is
probably better than talking about the means of specifying the
information abstractly.
I've opened a bug to track the creation of the field.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=509251
Wayne
On 14/12/16 12:02 PM, David Williams
wrote:
PC Members,
One of the action items from our last meeting was for me to
document our new requirement to "document yearly update policy".
I have added a draft in the requirements document at
https://wiki.eclipse.org/SimRel/Simultaneous_Release_Requirements#Document_Yearly_Update_Policy
And have opened a supporting bug at
https://bugs.eclipse.org/bugs/show_bug.cgi?id=509237
Apologies for the short notice, but please review by Thursday,
let's say by 5 PM (Eastern). Feel free to simply make minor edits
to fix grammar, spelling or my tendency toward wordiness. But if
there are any large issues that require discussion of the council
please post comments here to this PC list.
If there are no objections, I will remove the "draft" note on
Friday (M4 day!) and announce on cross-project list.
Thank you,
_______________________________________________
eclipse.org-planning-council mailing list
eclipse.org-planning-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-council
IMPORTANT: Membership in this list is generated by processes
internal to the Eclipse Foundation. To be permanently removed
from this list, you must contact emo@xxxxxxxxxxx to request
removal.
--
Wayne Beaton
@waynebeaton
The Eclipse Foundation
 |
