Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakarta.ee-spec.committee] Guides

This looks pretty great!

Parts we'd still need are links to the staged EFTL TCK  and staged EFSL PDF.  If projects can give us the link to a staged directory, we can easily make a Jenkins job where all we have to do is feed that in as a parameter and have it both sign and copy the binaries to the final location.  A link to that staged dir somewhere in the template is perfect.

The last part, which likely we can evolve, is we need to create a `mail/1.6/index.adoc` that looks like this:


Almost everything on that page is stuff we could create ourselves, sans the compatible implementations list.  Perhaps that's another PR template implementations have to do and involves a link an approved certification request from the project.

Anyway, that's wonderful.  Feels like this is all coming together.  I like the improvement you have of making that version a dir vs a file (mail/1.6/* vs mail/1.6.md).

-- 
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com


On Jul 11, 2019, at 3:50 PM, Bill Shannon <bill.shannon@xxxxxxxxxx> wrote:

I created a test PR.  Tell me what's wrong with it.

Bill Shannon wrote on 7/11/19 3:14 PM:
Great progress, thanks Scott!

I'm going to push some updates to the spec_page_template; you can yell at me if you really wanted to see a PR.  :-)

What should the directory structure under the specifications directory be?  I think we're expecting something like:

specifications
  wombat
    1.0
      wombat.md (from spec page template)
      wombat.pdf
      wombat.html
      javadocs (or "api"?)
    1.1
      ...
  platform
    8.0 (or "8"?)

We need to add this information to the README or pull request template.

Are there more "index" pages needed to link all the way down to wombat/1.0/wombat.md?  Or does hugo take care of that?  (I haven't learned anything about hugo yet.)


Scott Stark wrote on 7/10/19 9:49 PM:
The guides have been copied to the spec public folder and links emailed to the spec leads list.

TCK Process Guide:

I created a PR template:

And a spec page template based on the example servlet spec page Wayne had mocked up:

Finalizing exactly what needs to be in spec review PRs as well as the spec page template should be the focus of this Friday’s call.


_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee


_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee


Back to the top