Hi there!
Kohei Yoshida wrote:
[...]
By the way, that feature is not yet ready, neither is its spec. It was
going into 2.4 because you guys needed it (so Niklas put it in
partically). So, I don't think I'm obligated to finish the spec when I
don't even think it's ready.
So, what do you suggest we do then?
In this case, maybe we just have to live with the implied consequences.
The Szenario is just the following:
0.) A specification is being written
1.) A Spec-URL to the specification and an issue_id are entered in EIS
for a new feature announcement.
2.1) The spec URL complies to one of the templates => First sentence of
the Abstract is mentioned in the Document that is automatically
generated for creating ReleaseNotes or Milestones when the issue is one
that is fixed betweeen this new user release and the last user release
or this new developer milestone and the last developer milestone.
2.2) If this spec URL does not comply to one of the 2 templates (ODT or
wiki) => only the title of the feature mail is available in the document
generated as an interim document for creating release notes.
3.) If the document from 2.1 is reformatted to comply to the Wiki
template later than for Release notes created later the normal handling
of 2.1 is applied.
So well as long as the spec is not finished and not using the template
it doesn´t appear correctly in the release notes interim document. But
this currently only affects the release notes for the first developer
milestone the feature appears in. If we do 3.) before an offical user
release everything will be fine for the release notes of that user
release. If we don´t do 3.) that feature might eventually be missing
from the release notes.
As you said the feature itself isn´t even finished so I suppose we can
also have just another issue-id for the rest of the work to be done and
integrated and a feature-announcement announcing the new features with
usable content on the specification URL used containing the complete
stuff (usable means document is using the Wiki template, of course)
laster. And that´s probably the best to do.
Note: I implied that a feature mail was already written and an issue was
already fixed and integrated with a ChildWorkspace from what I think is
the case here but that may be wrong.
Kohei
Kind regards,
Bernd Eilers
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
