| Re: [tcf-dev] TCF ramp-down for Luna ! Change plans to use 1.3 ? |
|
Hi all, I’ve only received positive response on the plan, so here’s what we are going to do to minimize disruption: 1.
Uwe is going to create a *new* branch named “1.2_luna” off master.
a.
In this new branch, we will revert all version numbers to 1.2 , and have the Jenkins 1.2 jobs build off the new branch from now on. 2.
We are going to create a *new* branch named “1.2_pre” with identical contents like the current “1.2” branch. The current “1.2” branch is going to remain an alias of “1.2_pre” for 1 more week in order to give clients a chance to migrate. ·
Anybody who has existing builds off the current “1.2” branch and does not want to migrate, should switch their builds to “1.2_pre” ·
Anybody who does want to migrate can either stick to “1.2” or migrate to using “1.2_luna”. Next Monday (Luna RC3) we will switch the “1.2” branch and make it an alias of “1.2_luna” instead. Open question: What do we want to do with the Agent Source ? Current status quo is that 1.2 split off on 15-Feb-2014 and there’s exactly 1 screenful of commits in master on top of it: https://git.eclipse.org/c/tcf/org.eclipse.tcf.agent.git/log/?h=master Those commits add the PPC disassembler support (important community contribution!) which I would really like to make easily available. Other than that, I see only bug fixes (but I might miss something). My personal preference would be doing the same as on the host side: -
Rename 1.2 à 1.2_pre -
Create new “1.2” branch off master for stabilization for Luna from now on -
Revert the version number change (1.3 back to 1.2) in the “1.2” branch for the agent. Any comments or concerns ? Thanks, Martin -- Martin Oberhuber, SMTS / Product Owner – 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 Martin, The plan sounds OK to me. No commit to exclude from Target Explorer POV. Thanks, Uwe
J From:
tcf-dev-bounces@xxxxxxxxxxx [mailto:tcf-dev-bounces@xxxxxxxxxxx]
On Behalf Of Oberhuber, Martin Dear TCF committers, Here is an announcement and a question : Please read carefully and reply ASAP. The Luna release is fast approaching – RC2 to be closed next week, and then only 2 more weeks to go until RC4 which is the final build. For TCF, our plan had been to release Luna off tcf-1.2 which was forked off on 2014-02-25 already. Now it turned out that Luna is a great opportunity to win Community attention (and thus potentially contributors) by exposing our Terminal feature. I have published the TCF Terminals feature on Eclipse Marketplace only 1 week ago, and within that week we’ve received 138 installs , 2 “stars” and a slight, but visible increase of traffic on our homepage. Try it out if you haven’t yet, give us a “star” on marketplace if you like it, and vote us up on StackOverflow: http://marketplace.eclipse.org/content/tcf-terminals http://stackoverflow.com/a/23691697 The point is, that in order to get to the current Terminal’s quality a very large number of changes was needed on the TCF-1.3 stream And therefore I’d like to change plans and release Luna off the TCF-1.3 stream. Since TCF-1.2 has never officially been released, here’s what I would like to do for the host-side (Java) code:
1.
Rebase the “1.2” branch in git onto current HEAD
a.
As an alternative, abandon 1.2 and create a new 1.2 branch on HEAD
2.
In the new 1.2 branch, revert version numbers to “1.2”
3.
Revert any other potentially dangerous commits that are “not ready” for Luna
4.
From that point on, apply stringent testing and change control on the 1.2 branch. So first question to committers … do you agree with that plan ? If yes, then I need your help on point 3 : Which – if any – commits should we revert for 1.2 ? I personally only saw one to be discussed (“discontinue support of 0.4 and older agents”) which is something that we’d need to announce to the community before releasing: But there might be other changes to consider taking back.
Please let me know what you think ASAP !! Thanks, Martin -- Martin Oberhuber, SMTS / Product Owner –
Development Tools, Wind River direct +43.662.457915.85 fax +43.662.457915.6 |