Re: [cft-dev] CFT 1.0.1 and Neon.1 schedule

["Elson Yuen" <eyuen@xxxxxxxxxx>]

I have created the project releases and plans for Neon SR1 and Oxygen. Here are the links to the plans:
Neon SR1 - https://projects.eclipse.org/projects/ecd.cft/releases/1.0.1-neon-sr1
Oxygen - https://projects.eclipse.org/projects/ecd.cft/releases/1.1.0-oxygen

You can also find the links from our main project overview page as well.

The plan is dynamic so any item that has been assigned with the keywords field "plan" and target to a milestone that starts with 1.0.1 or 1.1.0 will shows up on the release plan. Therefore, any feature that you want to list on the release plan need to have the keywords and milestone field setting to those values.

Regards,
Elson

-----------------------------------------------------------------
Elson Yuen, P.Eng.
WebSphere Server Tools and Bluemix Tools Architect
IBM Toronto Lab
Tel: (905) 413-2689, T/L: 313-2689


Nieraj Singh ---07/14/2016 02:34:45 PM---In preparation for Neon.1, below is a list of general tasks and schedule for CFT 1.0.1, which is the

From: Nieraj Singh <nsingh@xxxxxxxxxx>
To: cft developer discussions <cft-dev@xxxxxxxxxxx>, Elson Yuen/Toronto/IBM@IBMCA, Martin Lippert <mlippert@xxxxxxxxxx>, Andy Clement <aclement@xxxxxxxxxx>
Date: 07/14/2016 02:34 PM
Subject: 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