On Sun, 15 Jul 2018 12:35:13 +0900 Carsten Haitzler said:
> On Sat, 14 Jul 2018 12:01:34 +0300 Jonathan Aquilina
> said:
>
> > Where can I begin?
>
> first step is writing code that uses efl api's. then writing simple mini-apps.
> they don't have to have a gui, but tbh to get better coverage a
On Sat, 14 Jul 2018 12:01:34 +0300 Jonathan Aquilina
said:
> Where can I begin?
first step is writing code that uses efl api's. then writing simple mini-apps.
they don't have to have a gui, but tbh to get better coverage at this point and
best "bang for your buck" or "more code paths covered per
Sure, have a great time!
On Sat, Jul 14, 2018 at 12:33 PM Jonathan Aquilina
wrote:
> It would have to be after he 22nd as I am currently on honeymoon is that
> ok for you
>
> Sent from my iPhone
>
> > On 14 Jul 2018, at 19:20, Mike Blumenkrantz <
> michael.blumenkra...@gmail.com> wrote:
> >
> >
It would have to be after he 22nd as I am currently on honeymoon is that ok for
you
Sent from my iPhone
> On 14 Jul 2018, at 19:20, Mike Blumenkrantz
> wrote:
>
> If you have interest in writing tests it's actually very simple, and I
> would not expect a new unit test to take more than 1-2 mi
If you have interest in writing tests it's actually very simple, and I
would not expect a new unit test to take more than 1-2 minutes to write and
run. The biggest issue with it at present is that there are no docs for it.
I can try to work with you a bit on this (mentoring test writing and adding
Where can I begin?
Sent from my iPhone
> On 14 Jul 2018, at 10:25, Carsten Haitzler wrote:
>
> On Sat, 14 Jul 2018 10:00:41 +0300 Jonathan Aquilina
> said:
>
>> Hi Raster with what you said below and other threads I’ve seen with people
>> complaining about lack of unit tests etc wouldn’t it b
On Sat, 14 Jul 2018 10:00:41 +0300 Jonathan Aquilina
said:
> Hi Raster with what you said below and other threads I’ve seen with people
> complaining about lack of unit tests etc wouldn’t it be better to get nightly
> builds to those that like to be on bleeding edge and help us test and report
>
On Sat, 14 Jul 2018 10:12:29 +0300 Jonathan Aquilina
said:
> I can get a vps from Linode and sponsor it myself I can work on setting up
> docker containers for build systems if need be.
that's total overkill. just chroots will do fine. it's not the need for vm's -
its the heed to create and main
I can get a vps from Linode and sponsor it myself I can work on setting up
docker containers for build systems if need be.
Also what is interesting is with Linode you can setup and use a GUI through
what they call glish
https://www.linode.com/docs/platform/using-the-linode-graphical-shell-glish
Hi Raster with what you said below and other threads I’ve seen with people
complaining about lack of unit tests etc wouldn’t it be better to get nightly
builds to those that like to be on bleeding edge and help us test and report
bugs. Not to mention I think nightly builds are possible as I see
On Fri, 13 Jul 2018 18:51:30 +0300 Jonathan Aquilina
said:
> I think it was me not being clear I think what I’m thinking is nightly tar
> balls and if need be I’m willing to work on pre packaged binaries for nightly
> builds
TBH fixes don't move into a stable branch fast enough to justify nightl
On Fri, 13 Jul 2018 09:46:14 -0400 Stefan Schmidt
said:
> Hello.
>
> On 13.07.2018 03:20, Jonathan Aquilina wrote:
> > Some food for thought wouldn’t it be better to do more frequent point
> > releases?
>
> If you look at the releases before 1.20 you will see that we did quite a
> few. I aimed
On Fri, 13 Jul 2018 10:36:53 -0400 Stefan Schmidt
said:
> Hello.
>
> On 12.07.2018 13:12, Mike Blumenkrantz wrote:
> > Now that we're interacting more as a community, I think there is the
> > general expectation that if you're a core developer then you should try to
> > notify the project if you
On Fri, 13 Jul 2018 14:35:10 -0400 Stefan Schmidt
said:
> Hello.
>
> On 13.07.2018 13:09, Jonathan Aquilina wrote:
> > I think my take is more from the end user base. Isn’t it worth the time and
> > effort to have binaries available for those non developers?
>
> Every night? I would say no. For
On Fri, 13 Jul 2018 18:30:13 +0300 Jonathan Aquilina
said:
> Could we enhance the scripts to make things easier to do this?
>
> If that is a yes then I’m more than willing to work on enhancing the scripts
Yes - we could. Though it would be a combination of workflow + scripts. You
want the infor
On Fri, 13 Jul 2018 20:14:31 +0300
Jonathan Aquilina wrote:
> Can Travis build rpm and deb binaries?
Of course, but I find it easier to do such via CMake's cpack. With
autotools and meson. You must make your own spec file for rpm, and
similar for deb. Plus targets for such. Why IMHO I prefer CMa
Hello.
On 13.07.2018 13:09, Jonathan Aquilina wrote:
> I think my take is more from the end user base. Isn’t it worth the time and
> effort to have binaries available for those non developers?
Every night? I would say no. For releases? Maybe.
regards
Stefan Schmidt
Can Travis build rpm and deb binaries?
Sent from my iPhone
> On 13 Jul 2018, at 19:41, Mike Blumenkrantz
> wrote:
>
> I think it should be possible to just upload a travis build somewhere
> periodically if we want to do this?
>
> On Fri, Jul 13, 2018 at 11:56 AM Stefan Schmidt
> wrote:
>
>>
I think my take is more from the end user base. Isn’t it worth the time and
effort to have binaries available for those non developers?
Sent from my iPhone
> On 13 Jul 2018, at 18:55, Stefan Schmidt wrote:
>
> Hello.
>
>> On 13.07.2018 11:51, Jonathan Aquilina wrote:
>> I think it was me not
I think it should be possible to just upload a travis build somewhere
periodically if we want to do this?
On Fri, Jul 13, 2018 at 11:56 AM Stefan Schmidt
wrote:
> Hello.
>
> On 13.07.2018 11:51, Jonathan Aquilina wrote:
> > I think it was me not being clear I think what I’m thinking is nightly
>
I think your reply is exactly why we should use the calendar; you say you
were sending mails about it and telling people for months before, and yet I
was still unaware. Or maybe I forgot. Either way, if there had been a
calendar entry then I would have known immediately.
Are you really taking that
Just use git if you are interested in getting updates that fast.
On Fri, Jul 13, 2018, 10:56 AM Stefan Schmidt
wrote:
> Hello.
>
> On 13.07.2018 11:51, Jonathan Aquilina wrote:
> > I think it was me not being clear I think what I’m thinking is nightly
> tar balls and if need be I’m willing to wo
Hello.
On 13.07.2018 11:51, Jonathan Aquilina wrote:
> I think it was me not being clear I think what I’m thinking is nightly tar
> balls and if need be I’m willing to work on pre packaged binaries for nightly
> builds
OK, very different from what I understood under a point release. Nightly
bui
I think it was me not being clear I think what I’m thinking is nightly tar
balls and if need be I’m willing to work on pre packaged binaries for nightly
builds
Sent from my iPhone
> On 13 Jul 2018, at 18:46, Stefan Schmidt wrote:
>
> Hello.
>
>> On 13.07.2018 11:27, Jonathan Aquilina wrote:
Hello.
On 13.07.2018 11:27, Jonathan Aquilina wrote:
> I was even thinking weekly point releases to get any new code or bug fixes
> out for early testing.
Hmm, not sure I get you here. What I talk about are stable updates which
would only contain fixes. No new code and definitely not used for
te
Could we enhance the scripts to make things easier to do this?
If that is a yes then I’m more than willing to work on enhancing the scripts
Sent from my iPhone
> On 13 Jul 2018, at 16:36, Mike Blumenkrantz
> wrote:
>
> Yes, I think bugfix releases should be done much more frequently. The issu
I was even thinking weekly point releases to get any new code or bug fixes out
for early testing.
Sent from my iPhone
> On 13 Jul 2018, at 16:46, Stefan Schmidt wrote:
>
> Hello.
>
>> On 13.07.2018 03:20, Jonathan Aquilina wrote:
>> Some food for thought wouldn’t it be better to do more frequ
Count me in to start a team for this
Sent from my iPhone
> On 13 Jul 2018, at 17:02, Stefan Schmidt wrote:
>
> Hello.
>
>> On 13.07.2018 03:10, Jonathan Aquilina wrote:
>> Hi Stefan,
>>
>> What know how does one need for this role?
>
> Well, there are many different parts to it.
>
> The mec
Hello.
On 13.07.2018 10:23, Mike Blumenkrantz wrote:
> Sure, I think the obvious area for automation would be in the release
> notes. Moving this to use the Enlightenment release method seems like it
> would save a huge amount of time here (ie. just running a script for ticket
> refs and using git
Hello.
On 12.07.2018 13:12, Mike Blumenkrantz wrote:
> Now that we're interacting more as a community, I think there is the
> general expectation that if you're a core developer then you should try to
> notify the project if you'll be gone for an extended period of time.
>
> I agree that there is
Sure, I think the obvious area for automation would be in the release
notes. Moving this to use the Enlightenment release method seems like it
would save a huge amount of time here (ie. just running a script for ticket
refs and using git shortlog). If we start using the right project tags for
'feat
Hello.
On 13.07.2018 09:36, Mike Blumenkrantz wrote:
> Yes, I think bugfix releases should be done much more frequently. The issue
> here is that doing releases in EFL is still very cumbersome; we need to
> greatly reduce the amount of active work that it takes to execute and ship
> a release.
Fe
Hello.
On 13.07.2018 03:10, Jonathan Aquilina wrote:
> Hi Stefan,
>
> What know how does one need for this role?
Well, there are many different parts to it.
The mechanical part of doing the tarballs is not that hard (parts are
even scripted).
The other part is to keep an eye on the bug reports
Hello.
On 13.07.2018 03:20, Jonathan Aquilina wrote:
> Some food for thought wouldn’t it be better to do more frequent point
> releases?
If you look at the releases before 1.20 you will see that we did quite a
few. I aimed for a one stable update per months schedule. Sometimes
being faster or sl
Yes, I think bugfix releases should be done much more frequently. The issue
here is that doing releases in EFL is still very cumbersome; we need to
greatly reduce the amount of active work that it takes to execute and ship
a release.
On Fri, Jul 13, 2018 at 3:21 AM Jonathan Aquilina
wrote:
> Som
Some food for thought wouldn’t it be better to do more frequent point releases?
Sent from my iPhone
> On 12 Jul 2018, at 20:12, Mike Blumenkrantz
> wrote:
>
> Now that we're interacting more as a community, I think there is the
> general expectation that if you're a core developer then you sho
Hi Stefan,
What know how does one need for this role?
Sent from my iPhone
> On 12 Jul 2018, at 17:32, Stefan Schmidt wrote:
>
> Hello.
>
>> On 10.07.2018 07:42, Mike Blumenkrantz wrote:
>> Hello,
>>
>> It seems that we have some issues lately regarding scheduling, specifically
>> personal sc
Now that we're interacting more as a community, I think there is the
general expectation that if you're a core developer then you should try to
notify the project if you'll be gone for an extended period of time.
I agree that there is a "deal with it" aspect to a community project, but I
think tha
Hello.
On 10.07.2018 07:42, Mike Blumenkrantz wrote:
> Hello,
>
> It seems that we have some issues lately regarding scheduling, specifically
> personal schedules. We (as a project) have expectations of developer
> availability, and when these expectations are changed or not met then
> things can
39 matches
Mail list logo
