/
appeals-process.xml
105 lines (87 loc) · 4.92 KB
/
appeals-process.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
<!ENTITY % BOOK_ENTITIES SYSTEM "tck.ent">
%BOOK_ENTITIES;
]>
<chapter id="appeals-process">
<title>Appeals Process</title>
<para>While the Bean Validation TCK is rigourous about enforcing an
implementation's conformance to the &jsrVersion; specification, it's
reasonable to assume that an implementor may discover new and/or better ways
to validate the assertions. This chapter covers the appeals process, defined
by the Specification Lead, Red Hat Middleware LLC., which allows
implementors of the &jsrVersion; specification to challenge one or more
tests defined by the Bean Validation TCK.</para>
<para>The appeals process identifies who can make challenges to the TCK,
what challenges to the TCK may be submitted, how these challenges are
submitted, how and by whom challenges are addressed and how accepted
challenges to the TCK are managed.</para>
<para>Following the recent adoption of transparency in the JCP, implementors
are encouraged to make their appeals public, which this process facilitates.
The JCP community should recognize that issue reports are a central aspect
of any good software and it's only natural to point out shortcomings and
strive to make improvements. Despite this good faith, not all implementors
will be comfortable with a public appeals process. Instructions about how to
make a private appeal are therefore provided.</para>
<section>
<title>Who can make challenges to the TCK?</title>
<para>Any implementor may submit an appeal to challenge one or more tests
in the Bean Validation TCK. In fact, members of the &jsrVersion; Expert
Group (EG) encourage this level of participation.</para>
</section>
<section>
<title>What challenges to the TCK may be submitted?</title>
<para>Any test case (e.g. <literal>@Test</literal> method), test case
configuration (e.g. @Deployment, validation.xml), test entities,
annotations and other resources may be challenged by an appeal.</para>
<para>What is generally not challengable are the assertions made by the
specification. The specification document is controlled by a separate
process and challenges to it should be handled through the &jsrVersion; EG
by sending an e-mail to <ulink
url="mailto:jsr349-comments@jcp.org">jsr349-comments@jcp.org</ulink>.
(todo verify email)</para>
</section>
<section>
<title>How these challenges are submitted?</title>
<para>To submit a challenge, a new issue of type Bug should be created
against <ulink
url="https://hibernate.onjira.com/browse/BVTCK">BVTCK</ulink> in the
Hibernate JIRA instance. The appellant should complete the Summary,
Component (TCK Appeal), Environment and Description Field only. Any
communication regarding the issue should be added in the comments of the
issue for accurate record.</para>
<para>To submit an issue in the Hibernate JIRA, you must have a (free)
Jira member account. You can create a member account using the <ulink
url="https://hibernate.onjira.com/secure/Signup!default.jspa">on-line
registration</ulink>.</para>
<para>If you wish to make a private challenge, you should follow the above
procedure, setting the Security Level to Private. Only the issue reporter,
TCK Project Lead and designates will be able to view the issue.</para>
</section>
<section>
<title>How and by whom challenges are addressed?</title>
<para>The challenges will be addressed in a timely fashion by the Bean
Validation TCK Project Lead, as designated by Specification Lead, Red Hat
Middleware LLC. or his/her designate. The appellant can also monitor the
process by watching the issue filed against <ulink
url="https://hibernate.onjira.com/browse/BVTCK">BVTCK</ulink>.</para>
<para>The current TCK Project Lead is listed on the <ulink type=""
url="https://hibernate.onjira.com/browse/BVTCK" userlevel="">BVTCK Project
Summary Page</ulink>.</para>
</section>
<section>
<title>How accepted challenges to the TCK are managed?</title>
<para>Accepted challenges will be acknowledged via the filed issue's
comment section. Communication between the Bean Validation TCK Project
Lead and the appellant will take place via the issue comments. The issue's
status will be set to "Resolved" when the TCK project lead believes the
issue to be resolved. The appellant should, within 30 days, either close
the issue if they agree, or reopen the issue if they do not believe the
issue to be resolved.</para>
<para>Resolved issue not addressed for 30 days will be closed by the TCK
Project Lead. If the TCK Project Lead and appellant are unable to agree on
the issue resolution, it will be referred to the &jsrVersion;
specification lead or his/her designate.</para>
</section>
</chapter>