Page History

...

1. Team ACKs security report.
2. Team investigates report and either rejects it or accepts it.
3. If rejected, write to submitter and explain why.
4. If accepted, write to submitter and let them know it is accepted and we are working on a fix.
5. Request a CVE number from security@a.o
6. Agree on a fix on our private@ list.
7. Provide the submitter with a copy of the fix and a draft vulnerability announcement for comment.
8. Reach an agreement for the fix, announcement and release schedule with the submitter.
9. Commit Create a JIRA and commit the fix in all actively maintained releases.
10. Roll a release for each actively maintained branch (unreleased trunk can wait.)
11. Announce the vulnerability (users, dev, security@a.o, bugtraq at securityfocus.com, full-disclosure at lists.grok.org.uk and project security pages)
12. Update the JIRA and svn log to include the CVE number.
13. Roll a release for each actively maintained branch (unreleased trunk can wait.)

Access to Geronimo TCK Test Harness

Apache committers can request access to the TCK following this process:

...

1. Requester should send a note to jcp-open@apache.org requesting access to the JCP TCKs
2. Requester should also send a note to the PMC list requesting access to the Geronimo Test Harness with a quick summary of their goals.
3. PMC member acknowledges receipt of the request back to the user.

...

2. PMC member confirms that requester has submitted an NDA:
   • ASF members can confirm by inspecting the contents of https://svn.apache.org/repos/private/foundation/Correspondence/JCP/tck-nda-list.txt or
   • Non-member can send a note to the appropriate keeper of NDAs on jcp-open and the Geronimo PMC with a subject of:
     
     **[TCK] Request for TCK access for Apache Geronimo TCK materials. Please verify NDA is on file.
     
     and includes relevant information about the committer and their request.
     
     
   • Waiting period:
     • Geronimo committers will be granted r/w access to svn, TCK wiki and accounts on selene, phoebe and tck01-tck08 upon confirmation of the NDA being on file.

...

1. • • Other

...

1. • • Apache

...

1. • • committers

...

1. • • will

...

1. • • be

...

1. • • granted

...

1. • • read-only

...

1. • • access

...

1. • • to

...

1. • • svn

...

1. • • and

...

1. • • TCK

...

1. • • wiki

...

1. • • (but

...

1. • • no

...

1. • • access

...

1. • • to

...

1. • • selene,

...

1. • • phoebe,

...

1. • • tck01-08)

...

1. • • upon confirmation of the NDA being on file.

The chair or authorized member will update the SVN authorization file, provide access to other resources as appropriate and notify the user of the URL and current relevant information. Geronimo committers are given r/w access and others are given read-only and they can start earning karma.