[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[cft-dev] CFT 1.0.1 and Neon.1 schedule
|
In preparation for Neon.1, below is a list of general tasks and
schedule for CFT 1.0.1, which is the version that will be included in
Neon.1
For Neon.1, we only have one milestone called a “checkpoint”.
We will be updating the CFT project page with a Neon.1/CFT 1.0.1 plan
in the next week or so:
https://projects.eclipse.org/projects/ecd.cft
1. Important Notes:
- If there are any new features and major changes to the code base,
the deadline to include them is RC1. We generally have a freeze date 3
business days before RC1 to allow for testing, but ideally, all major
changes should be in a week before RC1 deadline.
- Any work items for 1.0.1 require a bugzilla ticket:
https://bugs.eclipse.org/bugs/enter_bug.cgi?product=CFT
- For third-party/non-contributor submissions, please ensure that you
have a signed Eclipse CLA and follow guidelines as described in the
main page here:
https://github.com/eclipse/cft
- All third-party/non-contributor pull requests MUST be submitted,
reviewed and accepted by CFT dev team, and merged into master one week
before RC1 deadline.
2. Tasks:
- Create release record and page plan for CFT 1.0.1.
- Verify that the v1 CF Java client snapshot is in final form by RC1,
including dependency changes.
- Push all major changes and features to master by RC1.
- Submit IP Log by RC1.
- Schedule release review.
3. Schedule:
CFT 1.0.1.M3 - July 27
Neon.1 checkpoint (the only “milestone” for Neon.1) - July 27
Neon.RC1/CFT 1.0.1.RC1 - August 24
Neon.RC2/CFT 1.0.1.RC2 - August 31
Neon.RC3/CFT 1.0.1.RC3 - September 7 (IMPORTANT: LAST day to include
any changes for 1.0.1 and JEE EPP)
Neon.RC4 - September 14
Neon.1/ CFT 1.0.1 GA - September 28
