Good catch. The problem is that we only deal with HTML (and the generated PDF) in our release processes, and not images. I don’t think this should hold up the release, but we do need to figure out how to address this. Either by not putting images in specs or by addressing images in our releases.
+1 (community, Garden State Java User Group)
One comment: the image in the "Architecture" section in the HTML spec doc is missing, but is present in the PDF version.
Mike. To approve and ratify the Release Review of MicroProfile OpenAPI 2.0
Specification, the Steering Committee Representatives vote is requested.
Please respond with +1 (positive), 0 (abstain), or -1 (reject). Any
feedback that you can provide to support your vote will be appreciated. The
MicroProfile Specification Process requires the Specification Committee
and the Community to provide feedback during the approval process using
the relevant documents: https://github.com/microprofile/microprofile-wg/issues/20 This
ballot will be fourteen days, ending on Thursday, Dec 24. The ballot
requires a Super-majority positive vote of the Steering Committee
members. There is no veto. Community input and Community votes are
welcomed. However, only the votes delivered by Steering Committee
Representatives will be counted. -- Thank you Emily Jiang on behalf of MicroProfile Steering Committee
microprofile-wg mailing list
microprofile-wg@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/microprofile-wg
-- Code, Write, Cycle, Run, Drink, Sleep ... Repeat
Laissez Les Bon Temps Rouler
_______________________________________________ microprofile-wg mailing list microprofile-wg@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/microprofile-wg
|
