Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ecf-dev] Luna comitment

Adding to Wims response:

And we get bit of visibility via the EF marketing.

Thanks and Regards,
Harshana Martin
Harshana Eranga Martin
Senior Software Engineer,
WSO2 Inc.

ECF Committer:

On 9 September 2013 11:13, Wim Jongman <wim.jongman@xxxxxxxxx> wrote:
> The main advantage is that ECF is then in the big repo. If ECF is not part
> of the train then ppl have to pull it from a different repo. This alone is a
> huge advantage imo.
> Cheers,
> Wim
> On Mon, Sep 9, 2013 at 8:06 PM, Markus Alexander Kuppe
> <> wrote:
>> On 09/09/2013 07:57 PM, Scott Lewis wrote:
>> > I would like to have a public discussion about whether ECF will
>> > participate in the Luna release.  We soon have to publicly submit our
>> > intention to participate or not, and although my inclination is 'yes', I
>> > would like to have a community discussion about this, because I may not
>> > have the personal resources to do all the necessary work, and it so it
>> > does/will require work from many if not all the existing committers
>> > (e.g. review materials, release engineering, as well as
>> > code/development/test/docs contributions, etc).
>> >
>> > Question:  Should ECF participate in Luna next year?
>> > Corollary (for existing committers at least):  Are you able and willing
>> > to commit some time to ECF work to help meet the project deadlines?
>> Do we have any (empirical) data that ECF benefits from participating in
>> a release train? My gut feeling is that our consumers usually do not
>> need/use an ECF release that is synced with the rest of the release train.
>> M.
>> _______________________________________________
>> ecf-dev mailing list
>> ecf-dev@xxxxxxxxxxx
> _______________________________________________
> ecf-dev mailing list
> ecf-dev@xxxxxxxxxxx

Back to the top