[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ecf-dev] ECF participation in the annual simultaneous release
- From: Scott Lewis <slewis@xxxxxxxxxxxxx>
- Date: Wed, 6 Jul 2016 15:01:49 -0700
- Delivered-to: email@example.com
- User-agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1
On 7/6/2016 2:18 PM, Wim Jongman wrote:
I don't think that this is a good idea. Every time I open the release
train repo I see ECF. This must almost be on a weekly basis. So will
thousands other people.
I think it is valuable 'free' publicity and with the whole
microservice and IoT surge I think giving up your front seat row is a
I think characterizing it as 'free' publicity and 'giving up a front row
seat' is not accurate. Truth is, according to Foundation we are not in
IoT and don't receive any publicity...either as a Runtime Project or as
an IoT project (logically we are both RT and IoT, but don't get any of
the promotional/marketing/visibility benefits for either of them). For
a timely example of what I'm talking about, please see discussion on
this bug  and subsequently on the runtime pmc mailing list .
I'm not arguing that leaving the SR is necessarily a 'good idea', I'm
just saying that under the current conditions, I can't meet the
necessary commitments and so since I'm currently responsible for those
commitments as project lead, I won't make them without having a way to
I don't think the overhead is all that much especially since you
already plan to release 4 times.
There is significant overhead of the SR that I experience as project
lead and primary active committer....meeting requirements,
communication/bug fixing with Platform and SR projects, regular releng,
doing specialized work under continually more difficult SR releng
conditions (for example last year see ), and other things.
All of  was/is imposed by the SR and would not even be of concern
with ECF-only releases. In my experience, something akin to  has
occurred nearly every SR (e.g. with p2/Filetransfer). Please trust
me...it is significant overhead, even if it doesn't seem so on this
I would rather advice to release 3 times but still keep riding the train.
Here's my bottom line: To stay on the train we need a commitment to do
the necessary work. I'm not able to continue being the only jockey
actually riding the train when it starts moving (i.e. see the part that
requires significant overhead) with no visible means of support. I've
asked previously for that commitment from Platform, EF, member companies
that depend upon us, and others, and it hasn't come through in previous
cycles, so I'm not at all confident that it will during this cycle.
Therefore, the only way I will agree to have ECF continue riding the SR
is when the request comes with necessary resources. Not because I think
it's a 'good idea', but because that's currently all I can do.