Re: [jakartaee-spec-project-leads] Update to specification document temp

["Kevin Sutter" <sutter@xxxxxxxxxx>]

Are we sure we don't
want the "Final Release" in the footer on every page?  The
final version of the Java EE 8 Platform and Web Profile specifications
has "Final Release" in the footer on every page.  It seems
like it would be an easier change to just override the <status> element
to "Final Release" either by updating the pom.xml or mvn property
setting.  This would not require a change in the efsl document.

Is there some
reason why the "Final Release" in the footer is not desirable?

---------------------------------------------------
Kevin Sutter 
STSM, MicroProfile and Jakarta EE architect
e-mail:  sutter@xxxxxxxxxx     Twitter:  @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)    
LinkedIn: https://www.linkedin.com/in/kevinwsutter



From:
       Bill
Shannon <bill.shannon@xxxxxxxxxx>
To:
       JakartaEE
Spec Project Leadership discussions <jakartaee-spec-project-leads@xxxxxxxxxxx>
Date:
       07/18/2019
03:44 PM
Subject:
       [EXTERNAL]
[jakartaee-spec-project-leads] Update to specification document  
     template
Sent
by:        jakartaee-spec-project-leads-bounces@xxxxxxxxxxx

---

The template for the spec doc projects
allows for setting the "status" of
a document in the pom.xml.  The status then appears in the footer
of every page, and on the copyright/license page for the spec.

My intent was that the status would be "DRAFT" or "BETA"
or something
like that during development, and then would be "" for the final
release.
That works great for the page footer, but results in the copyright/license
page having this entry:

Status:

What we probably want in that case is:

Status: Final Release

But I don't think we need that in the page footer.

(I would do a page watermark instead of the footer, if I knew how to do
that.)

We have a fix for the above problem:

ifeval::["{revremark}" != ""]
Status: {revremark}
endif::[]
ifeval::["{revremark}" == ""]
Status: Final Release
endif::[]

You can pick up a new version of the license-efsl.adoc file with the fix
here:
https://raw.githubusercontent.com/bshannon/spec-template/master/src/main/asciidoc/license-efsl.adoc

Please update your spec documents with this fix.

Thanks.
_______________________________________________
jakartaee-spec-project-leads mailing list
jakartaee-spec-project-leads@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads