Overview of Proposal

One of the motivations for projects to get to Active status is that being in Active status is a requirement for having a "First Major Release". The reason for this requirement is that historically First Major Releases have been associated with significant Hyperledger expenses related to performing a security audit, getting approval from the TSC, and engaging in communication activities to promote the release. At the same time meeting all the Incubation Exit criteria can be challenging for projects even though the software they are producing might be well developed enough to otherwise qualify for a first major release.

This proposal is to introduce the notion of "Promoted Releases" which effectively separates all the activities currently associated with First Major Release previously mentioned from issuing a major release. This provide more flexibility in deciding what gets promoted and how the code gets released. In particular this will allow projects to have major releases while in Incubation, reducing the pressure on projects to move to Active status to do so and saving Hyperledger expenses.

Formal Proposal(s)

Introduce the notion of "Promoted Release". Redirect security audits, TSC review, and communication activities currently associated with First Major Release to Promoted Release. Allow projects in Incubation to have major releases that are not Promoted Releases.

Action Items

• Type your task here, using "@" to assign to a user and "//" to select a due date

Reviewed By

• Angelo de Caro
• Arnaud J LE HORS
• Christopher Ferris
• Dan Middleton
• Gari Singh
• Hart Montgomery
• Mark Wagner (Deactivated)
• Nathan George
• Swetha Repakula
• Tracy Kuhrt
• Troy Ronda