Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AdoptOpenJDK Quality Assurance (AQA) 1.0 - Goals and Definition #965

Closed
smlambert opened this issue Mar 9, 2019 · 4 comments
Closed

AdoptOpenJDK Quality Assurance (AQA) 1.0 - Goals and Definition #965

smlambert opened this issue Mar 9, 2019 · 4 comments

Comments

@smlambert
Copy link
Contributor

smlambert commented Mar 9, 2019

Verification of AdoptOpenJDK binaries should:

  • be open & transparent
  • consist of a diverse & robust set of test suites
  • evolve alongside implementations
  • have continual investment
  • have process to modify
  • be measured by codecov & other metrics
  • allow for comparative analysis
  • be portable
  • get tagged & published alongside binaries (build confidence, results transparency)

This epic will collect the various issues related to this overall goal, and also link to a separate Google document entitled AdoptOpenJDK Quality Assurance (AQA) 1.0 where the community can discuss and refine our goals and the definition of this quality bar together.

@smlambert smlambert changed the title AdoptOpenJDK Quality bar - Goals and Definition AdoptOpenJDK Quality Assurance (AQA) 1.0 - Goals and Definition Mar 11, 2019
@smlambert
Copy link
Contributor Author

Related: #186

@smlambert
Copy link
Contributor Author

Incorporated feedback into the google doc.

For the upcoming release, we will use it as an initial trial of mechanisms required for AQA (bill of materials that include SHAs of all repos housing test materials used to verify builds).

@smlambert
Copy link
Contributor Author

smlambert commented Jun 6, 2019

Issues that need to be completed to deliver AQA v1.0:

@smlambert smlambert added the AQA label Jun 6, 2019
@smlambert
Copy link
Contributor Author

smlambert commented Jan 2, 2020

I will close this issue as completed

2 pieces to be discussed and if kept, to be moved to next drop of AQA (#1522) are:

  • pushing SHA.txt to release repo (currently archived with test results on Jenkins at Adopt, and in artifactory at other projects
  • the possible addition of a badge on the website

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants