| Re: [tcf-dev] TCF 1.5 / participation in Oxygen |
|
Hi Martin, Please, make our participation in Oxygen official. I don’t mind doing whatever necessary to support the release. Could you give more info on what you call “release engineering”? Any tips/hints would be helpful. Thanks, Eugene From: tcf-dev-bounces@xxxxxxxxxxx [mailto:tcf-dev-bounces@xxxxxxxxxxx]
On Behalf Of Oberhuber, Martin Greetings TCF Committers, As per below, the time has come where we need to declare participation in the Eclipse Oxygen (4.7) simultaneous release, planned to release in June 2017. I’ve already created a
-
https://wiki.eclipse.org/TCF/DraftPlan15 but wanted YOUR (committers) buy-in before I declare the intent officially. I already noticed that PTP/Remote 3.0 broke an API we use, so we’ll need to react if we are on the train; so it does come at a (small) cost, see attached. Also please note
that Uwe may not be able to handle release engineering like he did in the past, so we may need other committer’s help there.
On the other hand, the benefit of participation is significant in terms of market exposure IMO. Please send your +1 (buy-in to participating in Oxygen) until Friday Oct 7 COB if possible, and I’ll declare participation by creating a release record. Please also let me
know any questions / concerns, or plans for TCF 1.5. Thanks, Martin -- Martin Oberhuber, SMTS / Product Owner – Development Tools, Wind
River direct +43.662.457915.85 fax +43.662.457915.6 From:
<cross-project-issues-dev-bounces@xxxxxxxxxxx> on behalf of "wayne@xxxxxxxxxxx"
<wayne@xxxxxxxxxxx> Greetings folks. I believe that I've gotten my list of participating projects [1] up-to-date with those projects that have used this list to declare their intent to participate in the Oxygen Simultaneous Release. I also added a few projects that participated in Neon and
had created release records dated June 28/2017 on an assumption that by bothering to create the record for the release they could reasonably be understood to be "paying attention". If you have not yet formally declared intent, please do so (this will get you off of the inappropriately labeled "Dropped in this Release" list hidden in the Overview block). If you project is on that list but does not have a version number beside it, that means that you either did not create a release record or that I could not identify it. If you have not yet created a release record for your Oxygen release, please do so at
your earliest convenience. Placeholder release records are fine. Ideally, however, it would be very helpful if you can provide an "executive summary" for the release in the description field. Note that there is no value in stating that the release is part of Oxygen in the executive
summary; I'm looking for a few words describing the main areas of development focus or cool new features.
While I have your attention, I'd like to take a run at building an aggregate change log for the release (see Bug 488598 [3]) and am of the mind that the easiest way to do this consistently is to leverage the technology that underlies the "issues" tab that
already exists in the PMI [4]. If you name your target milestones in Bugzilla, your project will automatically participate in this.
Thanks! Wayne [1]https://projects.eclipse.org/releases/oxygen -- This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately. |