| Re: [tcf-dev] Releasing TCF 1.2 in March |
|
Hi, For the org.eclipse.tcf repository, the “master” branch is now building “1.3.0.qualifier” plug-in and feature id’s. Best regards, Uwe J From: tcf-dev-bounces@xxxxxxxxxxx [mailto:tcf-dev-bounces@xxxxxxxxxxx]
On Behalf Of Stieber, Uwe Hi again, TCF 1.2 build job created and P2 repository is deployed. Job: https://hudson.eclipse.org/tcf/job/tcf-1.2/ P2 Repository:
http://download.eclipse.org/tools/tcf/builds/1.2/nightly Best regards, Uwe J From: tcf-dev-bounces@xxxxxxxxxxx [mailto:tcf-dev-bounces@xxxxxxxxxxx]
On Behalf Of Oberhuber, Martin Thanks Uwe, I have created bugzilla “Version” 1.3 and “Target Milestone” 1.3 ,
And I have marked all recently fixed bugs as 1.2 target milestone. Moving forward, please ONLY set the 1.2 target milestone for fixes that go into 1.2 branch between now and release. We need these bugzilla target milestones for some bugzilla statistics as part of the release review requirements. (FYI: 79 defects were fixed, 16 of them major and 2 critical). I have not yet decided on whether we’ll want to create an “1.2.1” target milestone, since such a release might actually never exist. Any concerns about just creating an “1.2+” target milestone to denote fixes in the 1.2 stream post 1.2 release ? Or does anyone foresee already releasing tcf-1.2.1 ? Next steps: IP Review, request release review from Wayne, and any polishing items in the code (Copyright Updates, Docs). Thanks, Martin -- Martin Oberhuber, SMTS / Product Architect – Development Tools,
Wind River direct +43.662.457915.85 fax +43.662.457915.6 From:
tcf-dev-bounces@xxxxxxxxxxx [mailto:tcf-dev-bounces@xxxxxxxxxxx]
On Behalf Of Stieber, Uwe Hi, Tags (TCF_1_2) and branches (1.2) are created in both repositories. Have to refocus on some other high priority tasks, will move the Eclipse plug-in version in “master” to “1.3.0.qualifier” later. Also will create the “tcf-1.2” job later. Best regards, Uwe
J From:
tcf-dev-bounces@xxxxxxxxxxx [mailto:tcf-dev-bounces@xxxxxxxxxxx]
On Behalf Of Oberhuber, Martin Hi all, Since there has been no concerns about cutting a TCF-1.2 release, we will proceed doing this. Note that I’d like to release both front-end (plugins) and agent at the same time. We can use this as rough guideline for our Release Review Checklist: https://wiki.eclipse.org/TM/3.2_Release_Checklist
1.
Uwe has already done a “Fix Copyrights” pass on the front-end (plugins).
a.
Plug-in and feature ID’s should also be good, Unittests are all good.
b.
Who could do a “Fix Copyrights” pass on the agent before we branch off ?
c.
Who could review the checked-in Docs for any obvious fixes that need to be made ?
d.
Let us know of any other concerns before we branch off.
2.
Uwe is going to create an 1.2 branch in GIT which will hold our stable release, along with Tycho config and Hudson jobs for 1.2-stable
a.
We would like to create the 1.2 branches some time tomorrow.
3.
In master, we’ll update the version number in master to “1.3”
a.
Uwe will do o.e.tcf /
Eugene, could you do this for o.e.tcf.agent or shall we proceed ?
4.
I will create a Bugzilla “Version” 1.3, and “Target Milestones” 1.3 , 1.2 and 1.2+ No change should be needed for any developers, you’ll simply continue as usual.
5.
I will send E-Mail to the Eclipse Foundation asking for an 1.2 release review
a.
I will update any necessary release review material on
http://projects.eclipse.org
b.
I will review our IP Log and submit to the Eclipse IP Team
i. We may have to disclose a WORKSWITH dependency of tcf-agent on OpenSSL
c.
I will set the target milestone of all recently FIXED bugzilla items to “1.2”
6.
Once the Eclipse IP team has approved the submitted IP log, Wayne will announce the release review
a.
Release review is “virtual” ie a 1-week period in which people may issue concerns …
b.
After that we can declare on the homepage and downloads, and apply a git tag “1.2”. Any backports of changes into the 1.2 branch should have an associated bugzilla item at this point with target milestone set to “1.2” (if before final release) or “1.2+” (if after 1.2
release). We should see git changesets on the 1.2 branch easily, so we’ll get you if you forget
J Let me know if there’s any Thanks, Martin -- Martin Oberhuber, SMTS / Product Architect
– Development Tools, Wind River direct +43.662.457915.85 fax +43.662.457915.6 From:
tcf-dev-bounces@xxxxxxxxxxx [mailto:tcf-dev-bounces@xxxxxxxxxxx]
On Behalf Of Eugene Tarassov It sounds good to me. Eugene From:
tcf-dev-bounces@xxxxxxxxxxx [mailto:tcf-dev-bounces@xxxxxxxxxxx]
On Behalf Of Oberhuber, Martin Hi TCF committers, We are interested in cutting a stable TCF 1.2 release early this year, potentially in the next couple weeks (in time for EclipseCon March 17-20). Main driver is that we consider TCF in a stable state at this point which we’d like to maintain for a while with small patches only (while making bigger changes in mainstream). The overhead for cutting the 1.2 release early should be relatively small at Eclipse.org -- basically just
1.
review the IP Log, 2.
convert the “Plan” items in the http://projects.eclipse.org portal into release docuware, and 3.
set a Tag + branch in the repository along with a Hudson Job for maintenance builds. We could do all those work items relatively easily. It would then be a separate discussion whether we make our Luna contribution in June off 1.2.1 or 1.3. Does anybody have any concerns with this plan ? Any bigger changes pending maybe ? Thanks, Martin -- Martin Oberhuber, SMTS / Product Architect
– Development Tools, Wind River direct +43.662.457915.85 fax +43.662.457915.6
|