What is the bar, for allowing the PRs to be merged? Is it, the
submission is believed to be ready for the Ballot?
-- Ed
On 8/2/2019 5:35 AM, Edwin Derks wrote:
Thanks all, for the additional information so far.
A merged PR would indeed be greatly beneficial in understanding
what a finalised specification should look like. As soon as
there is one, please broadcast. ;)
Cheers,
Edwin
Guillermo
González de Agüero wrote on 8/1/19 10:57 AM:
> Hi,
>
> Besides what you mention, I also see two things made
different on each spec:
> - Status: some say "Final", others "Final Release"
Doesn't matter. You can also just leave it blank.
> - File names. I've seen:
>
<spec-name>/<version>/<spec-name>-<version>.html
>
/<spec-name>-spec-<version>.html
>
/<maven-coordinates>-<version>.html
>
> For consistency, we should aim to use at least the same
paths. Which are the
> correct patterns?
I don't think we've placed any requirements on the name of the
spec document,
but the second one above is the recommended choice.
> Reviews will be easier once there's at least one PR
merged so that we can
> compare others to it.
Yes, we're still struggling to find one perfect PR! :-)
_______________________________________________
jakarta.ee-wg mailing list
jakarta.ee-wg@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-wg
_______________________________________________
jakarta.ee-wg mailing list
jakarta.ee-wg@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-wg
|