Skip to content
This repository has been archived by the owner on May 4, 2022. It is now read-only.

Commit

Permalink
docs(incubation): note successfully released during incubation
Browse files Browse the repository at this point in the history
  • Loading branch information
apetro committed Feb 19, 2018
1 parent 9eafc5d commit 2854ae8
Showing 1 changed file with 2 additions and 8 deletions.
10 changes: 2 additions & 8 deletions docs/apereo-incubation.md
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@ Items are checked where the project believes it now fulfills the exit criteria.
- [x] 4.4 Voting practices
- [ ] 4.5 Conflict resolution policy
- [ ] 4.6 Release planning
- [ ] 4.7 Successful release during incubation
- [x] 4.7 Successful release during incubation
- [ ] 4.8 Alignment and synergy with other Apereo software products
- [ ] 4.9 Infrastructure
- [ ] 4.9.a Version control
Expand Down Expand Up @@ -184,13 +184,7 @@ Next actions:

### 4.7 Successful release during Incubation

uPortal-home has had many releases.

Let's say Incubation starts for this purpose after governance and licensing is squared and the repos are moved to a uPortal-project context. Successfully releasing after those changes are in place will demonstrate that the product can still release under the new arrangements.

Next actions:

+ Make the transition to a uPortal-project GitHub organization context, then, cut a release.
uPortal-home has had many releases, including many during incubation after governance and licensing squared and the repos moved to a uPortal-project context. Successfully releasing after those changes demonstrated that the product can still release under the Apereo arrangements.

### 4.8 Alignment and synergy with other Apereo software products

Expand Down

0 comments on commit 2854ae8

Please sign in to comment.