[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
[jakarta.ee-spec.committee] Agenda for 22-AUG-18 Spec Committee Call
|
All,
Both Wayne and Tanja are unavailable today, so I will be acting
as the meeting chair for our call at noon Eastern.
I would like to propose a two-part agenda for today's call.
- Agree on what our medium term goals are. For example:
- Creating a version 1.0 of the Spec Process document which
focuses solely on the processes necessary for creating new
specification in the jakarta namespace.
- Creating a draft Spec Process document for community
feedback.
- ...others?
- Continue discussion on the TCK topic, as outlined in Richard's
email below.
Talk soon. Thanks.
Call info just in case:
You can always refer
to this document for the agenda and
previous meeting minutes.
Join from PC, Mac, Linux, iOS or Android: https://eclipse.zoom.us/my/jakarta.ee.committee
Or iPhone one-tap :
US: +16699006833,,355402799# or +16468769923,,355402799#
Or Telephone:
Dial(for higher quality, dial a number based on your
current location):
US: +1 669 900 6833 or +1 408 638 0968 or +1 646 876
9923
Canada: +1 647 558 0588
France: +33 (0) 1 8288 0188
Germany: +49 (0) 30 3080 6188
United Kingdom: +44 (0) 20 3695 0088
Switzerland: +41 (0) 31 528 0988
Sweden: +46 (0) 8 4468 2488
Denmark: +45 89 88 37 88
Netherlands: +31 (0) 20 241 0288
Japan: +81 (0) 3 4578 1488
Meeting ID: 355 402 799
International numbers available: https://zoom.us/u/bcTrDbvzw
-------- Forwarded Message --------
The Draft of the TCK document (see link below) has
been available and commented on. More comments are welcome.
https://docs.google.com/document/d/1civpv_KLHvUXgILQYCh0HR9Xgsv78PISPc9wbRUUKMc/edit?usp=sharing
While some issues are easy to resolve in comments on the
document others require a more focused resolution. These
other issues are enumerated below. Please take the time to
read and respond.
- TCK Challenges: When a vendor challenges a TCK test
who should determine if the challenge is valid? The
following options have been suggested:
- The TCK Project (assuming its separate from the
Specification Project)
- The Specification Project with Escalation to the
Specification Committee allowed
- The Specification Committee only.
- Vendor Releases and TCK patches: If a vendor
releases a new version minor of their product, which
continues to support the same specifications claimed
by the original major version, can the new minor
version be tested against the original TCK used for
the original version, or does it need to be tested
against the latest patch/revision of that TCK?
- Versioning: Should the TCK versions match the major
and minor versions of the Specification?
- Versioning: If an errata level error (anything that
doesn't change the described behavior of the software
or its API usage) is found in a specification which of
the following options should we use?
- An errata is published with the correction but the
specification is not updated.
- The specification is updated and a new Rev version
is released. (e.g. X Specification Version 1.2 Rev
2)
- The specification is updated and a new Maintenance
version is released (e.g. X Specification Version
1.2 MR 2)
- Specification Updates and TCK updates: What kinds
of corrections to a specification should require a new
version of the TCK?
thanks,
Richard
|
This email has been checked for viruses by Avast antivirus software.
www.avast.com
|
|
_______________________________________________
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://dev.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee