Re: [jakarta.ee-spec.committee] naming convention for specification docu

[Wayne Beaton <wayne.beaton@xxxxxxxxxxxxxxxxxxxxxx>]

I added a column to the Projects, Specifications, and Documents spreadsheet (code) with my SWAG at what we might use as the equivalent of project "short names" for each of the specifications. I've tried to be consistent... e.g., spelling out "enterprise-beans" and "_expression_-language" instead of "eb" and "el" (for example). I could be convinced that compact is better.

I'm going to write a script using data from this script to build the initial contents for a "specs" directory. As part of that, I'm going to need version numbers for each specification. What's our algorithm for that? Current number, or current number +1 on the minor version?

Wayne

On Wed, Jul 3, 2019 at 7:02 PM Bill Shannon <bill.shannon@xxxxxxxxxx> wrote:

What should be the naming convention for specification documents?

1. wombat-spec-1.0.pdf
2. Wombat-spec-1.0.pdf
3. Wombat-Spec-1.0.pdf
4. WombatSpec-1.0.pdf
5. Something else
_______________________________________________
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

--

Wayne Beaton

Director of Open Source Projects | Eclipse Foundation, Inc.