[JSR348-34] Permit Spec Leads to submit no quarterly certification report if nothing has changed Created: 29/Jul/11  Updated: 22/Sep/11  Resolved: 22/Sep/11

Status: Closed
Project: jsr348
Component/s: Process Doc
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: pcurran Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


Bill Shannon said, in comments on the draft document:

"I still don't think there should be a requirement to submit
anything if nothing has changed. who's going to detect failure to
submit? the PMO? if the PMO sends the quarterly "why haven't you
submitted anything" message, we'll just use that as the reminder to
say "nothing has changed". I don't want to be required to proactively
say "nothing has changed" every quarter. who's going to sign up for
doing that forever for JSRs that are no longer being used?"

I responded:

I still think that starting out with the assumption that people need
not report unless they have something to say will lead to people
ignoring this requirement. The PMO can use its judgment about who to
remind, but I really do want the "there's nothing to report this quarter"
messages so we don't have to guess whether or not we're being ignored.

Comment by pcurran [ 05/Aug/11 ]

See also http://java.net/jira/browse/JSR348-32

Comment by Bill Shannon [ 05/Aug/11 ]

I say with complete confidence that Spec Leads will not reliably provide this
information quarterly.

Comment by pcurran [ 06/Aug/11 ]

I understand that (some) Spec Leads won't want to do this. Some Spec Leads don't want to do most of what the JCP requires them to do (subject their Specs to EC votes, for example.) That doesn't necessarily mean that the requirements are a bad thing, or that we should turn a blind eye to violations of the process, or that the requirements should be watered down or dropped.

Bring it on!

Comment by Bill Shannon [ 07/Aug/11 ]

Note that generally it's not the Spec Lead who is maintaining the list of
compatible implementations. More likely it's a Marketing or Product Management

Comment by starksm64 [ 09/Aug/11 ]

The current http://java.net/projects/jsr348/downloads/download/Working%20documents/JCP%20NEXT%202.8-10AUG2011-Clean.pdf version states on line 302 that this is done quarterly and at every MR. Inclusion of the MR does not seem helpful as it is likely that only the RI has passed the TCK. The next quarterly report should pick up the new implementations passing any changes introduced in the MR. When MRs do exist, the compatibility report should be specifying to what MR the testing has been done.

Comment by pcurran [ 22/Sep/11 ]

As Scott Stark suggested, I've removed the requirement to report at Maintenance Release times.

Re Bill Shannon's request that it permissible not to report if there's nothing new, we've discussed this several times and agreed that we want to hold the line.

So - I'm closing this. Hopefully Bill himself won't have to do anything

Generated at Thu Mar 05 12:56:22 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.