[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
[oniro-pmc] Oniro Alpha Release: basic information from EF
|
Hello Pavel,
this mail contains relevant information about how to release at EF and about
the timeline for Oniro Alpha release.
## Links and references
During the last Oniro IT meeting I mentioned that I would bring basic
information about Releases at EF as well as an update about how things are
going at Eclipse Foundation that might affect our release.
The first step would be to learn about EF default release process. Please read
the following information:
* Development Process: Project lifecycle: Release Review: https://
www.eclipse.org/projects/dev_process/#6_2_Project_Lifecycle
* EF Release Reviews: https://www.eclipse.org/projects/tools/reviews.php
* Development Process: Release: https://www.eclipse.org/projects/dev_process/
#6_4_Releases
* Project Handbook: Release: https://www.eclipse.org/projects/handbook/
#release
* Project Handbook:Project Management Infrastructure: https://www.eclipse.org/
projects/handbook/#pmi
* Releases and Reviews: https://www.eclipse.org/projects/handbook/#pmi-releases
* Simultaneous Releases: https://www.eclipse.org/projects/handbook/#pmi-joining-a-simultaneous-release
* Project Handbook:Project Checklist: https://www.eclipse.org/projects/
handbook/#checklist
Other interesting links
I would also check the Glossary. Learning about the terminology we use makes
communication easy.
* Project Handbook:Glossary: https://www.eclipse.org/projects/handbook/
#glossary
Licenses:
* 3rd Party Licenses: https://www.eclipse.org/legal/licenses.php
## Other relevant points to consider
My main goal is to try to provide the highest level possible or certainty to
developers and the project in general, considering that this is the first time
EF will release an operating system (family) and that this is the first time
for most developers that they release under EF.
Both, the Oniro project and EF have been adapting and introducing changes in
different areas, not just to come to this point and be efficient but to work
on a more continuous basis in the coming months to avoid risks in the Oniro
Platform v2.0 release.
### New IP Policy
New relevant changes have been introduced by the EF IP Team in the EF IP
Policy. Such changes will require EF Board approval. The vote is scheduled
already for June 28. The (potentially) approved policy will come into effect
thirty days later (July 28).
The changes introduced in IP Policy will have a highly positive effect in the
coming Oniro releases compared of releasing with the current policy. This
means that July 28 is the earliest date that we can apply the new policy, so
is the earliest date that Oniro can release under that policy.
Subsequent releases will not experience this constrain.
## License reviews
We would welcome a code freeze and starting the Release process for Oniro
Alpha as soon as possible. In any case, EF is already working on the Oniro
licenses review. We are expecting an initial output of this effort on week 24,
maybe earlier.
## Release Timeline
Considering that we need to release under the new IP Policy, the tentative
Oniro Alpha release day is July 28th.
The license review effort is expected to be done on time for that day. We will
have more certainty once we have the output of the preliminary license review.
We are optimistic.
I suggest to start with the Release process as soon as is technically
possible. At EF, we'll do the necessary leg work in advance to avoid any
further delay from the proposed date.
## Meeting
I suggest to have dedicated regular sessions to coordinate the release among
the different parties involved:
* Oniro Release Manager
* Project Committers and PMC
* Oniro Platform Release Roadmap Team (RR Team)
* Oniro Marketing
* EF Release Management (Sebastien) and Oniro IT team.
* Any other?
I put a couple of options on the table:
* Thursdays from 10 to 10:45 CEST
* Thursdays from 16:15 to 17:00 CEST
During the first session we can decide how we are going to publish the
timeline of the Oniro releases as well as the ToC of the required Release
Plan, including the Release checklist we mentioned during the meeting you were
present on Tuesday.
Let's not forget that the RR Team has some attributions related with the
Roadmap that will influence the discussions. But since such team is not
operational yet, we will need to do our best to promote alignment.
Best Regards
--
Agustin Benito Bethencourt
Oniro Program Manager | Eclipse Foundation
Eclipse Foundation: The Community for Open Innovation and Collaboration