Hello.
On 28.02.19 17:45, Stefan Schmidt wrote:
>
> 2) Running Coverity to have some additional static analysis on the code
> to see if it finds any critical issues we should fix before the release.
I submitted a build from the alpha1 tag and it got analyzed over night.
In total we
tools build system completely from master after this
release is out. It will only remain in the efl-1.22 stable branch at
that point. Don't stay behind and make sure your use cases are covered
with meson.
regards
Stefan Schmidt
___
enlightenment-dev
Stefan Schmidt
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
fixes from this point
2019-03-14 Beta2 release tarball
2019-03-21 EFL 1.22 is out
regards
Stefan Schmidt
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Hello.
On 16.02.19 00:37, Simon Lees wrote:
>
>
> On 16/02/2019 02:07, Stefan Schmidt wrote:
>> Hello.
>>
>> We pushed back on the initial schedule to not get everyone caught by
>> surprise of a freeze.
>>
>> We had some extra weeks now and I wond
there are we trigger the process to do a new release.
In practice that would mean we do it really "on-demand", as in, some fix
was seen worthwhile backporting. I would imagine that will give us
weekly updates for the first few weeks after a major release and after
that only occasionally
Hello.
On 16.02.19 05:03, Jonathan Aquilina wrote:
> Hi Stefan,
>
> I thought you were making a few changes to it given we are doing 5 month
> major releases and then weekly point releases.
There is nothing in the script that would encode the release schedule.
regards
St
t here. It will be the same release
script I used all the time. I pointed you several times to it. Last time
when we had or IRC chat.
regards
Stefan Schmidt
> -Original Message-----
> From: Stefan Schmidt
> Sent: 15 February 2019 16:37
> To: enlightenment-devel@lists.sourceforge.
1.22.x releases for maintenance.
If this schedule does not work for you for a good reason speak up now.
regards
Stefan Schmidt
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo
=21&min=0&sec=0&p1=37
22:00 CET timezone.
regards
Stefan Schmidt
> Regards,
> Jonathan
>
> On 08/02/2019, 09:34, "Stefan Schmidt" wrote:
>
> Hello.
>
> On 06.02.19 15:33, Jonathan Aquilina wrote:
> > I just landed a new job
ou want to have the discussion?
regards
Stefan Schmidt
> -Original Message-----
> From: Stefan Schmidt
> Sent: 06 February 2019 14:04
> To: Enlightenment developer list ;
> Jonathan Aquilina
> Subject: Re: [E-devel] Azure Devop's CI
>
> Hello Jonathan.
>
enough to spend time on it.
>
> I think best place to get this rolling would be to do a conference call or a
> chat on slack.
Slack or IRC. What day and time would you prefer?
regards
Stefan Schmidt
> -Original Message-----
> From: Stefan Schmidt
> Sent: 06
hould be possible to bring over.
regards
Stefan Schmidt
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
ve
the time and the bandwidth to do this.
regards
Stefan Schmidt
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
are many things that are not clear to anyone but me.
Feel free to edit the wiki and ask me.
If you could get yourself comfortable with the steps involved that would
already be a help. For example try to produce some release tarballs on
your local machine and see if you run into troubles.
regards
Hello.
On 10.01.19 10:24, Simon Lees wrote:
>
>
> On 10/01/2019 01:51, Stefan Schmidt wrote:
>> Hello.
>>
>> Its almost 5 months since we released 1.21 and I stepped down.
>>
>> When talking with people I got help offers on the release handling but
>&
Hello.
On 09.01.19 16:21, Stefan Schmidt wrote:
> Hello.
>
> Its almost 5 months since we released 1.21 and I stepped down.
>
> When talking with people I got help offers on the release handling but
> no-one stepped up to fully take a lead on this. I start to get the
> fe
t every pet peave
>> bug should be listed there).
>
> is it too late to add an API ?
To be a bit more verbose than Mike :-)
Feel free to add a new API. We are just talking about getting a new
release out and the schedule is only proposed , too.
Right now development goes o
rball generated
with meson out to allow packagers and testers to get used to it and
report problems to us. Once 1.22 is out we would go ahead and remove
autotools support from the tree to focus on meson only forward and
reduce the maintenance burden we currently have with two build systems.
regards
2019-01-23 Merge window is over. Freeze in place.
* Only bug fixes from this point
* Alpha release tarball
* One month stabilization phase starts
2019-01-30 Beta1 release tarball
* Only critical fixes from this point
2019-02-06 Beta2 release tarball
2019-02-13 EFL 1.22 is out
regards
Stefan Schmidt
Hello.
On 29/09/2018 08:19, Davide Andreoli wrote:
> Il giorno mer 26 set 2018 alle ore 10:17 Stefan Schmidt
> mailto:ste...@datenfreihafen.org>> ha scritto:
>
> Hello Dave.
>
> I have recently disabled all builds on Jenkins. The only job I left
> enabl
Travis for it (if I missed it I am happy to get pointed
to it). It basically means we would move our CI over to Gitlab and all
builds run on our infra (cloud/or hardware). That could easily bring
back the overloading problems we had on e5. I am very hesitant in buying
into u
fair to start having a vote on community
desires. That should show a bit better what the people here want.
If there will be a sustainable plan to get to that goal has to be seen.
One have to start somewhere though and this thread has gone in many
direction without a clear direc
something you are still actively using? Something that produces tarballs
or artifacts you need?
If it is something actively used and needed we need to find a new home
for it. If it is just a left over we can simply drop it.
regards
Stefan Schmidt
right now. Master and e5-build-gentoo-x86_64-1
VM's are still needed for base_pyefl (please keep the files on disk if I
need a reference at some point).
With all the Jenkins VM's out of the way I hope a the work on the infra
is easier to get d
Hello.
On 09/14/2018 09:48 AM, Carsten Haitzler (The Rasterman) wrote:
> On Wed, 12 Sep 2018 12:44:52 +0200 Stefan Schmidt
> said:
>> This is the core problem. OSUOL has indeed doing a great job for us over
>> the years for hosting and connectivity. But they can only be as g
Our first update on the 1.21 release series.
Fixes:
* ecore_wl2_dmabuf: Link with ecore_wl2 (T7327)
* ecore_wl2_dmabuf: Depend on ecore_wl2 (T7327)
* efl selection manager - avoid multiple selection get callbacks for req
http://download.enlightenment.org/rel/libs/efl/efl-1.21.1.tar.xz
Stefan Schmidt
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Hello.
On 09/12/2018 10:24 AM, Carsten Haitzler (The Rasterman) wrote:
> On Thu, 30 Aug 2018 19:49:29 +0930 Simon Lees said:
>
>>
>>
>> On 30/08/2018 18:57, Stefan Schmidt wrote:
>>> Hello.
>>>
>>> On 08/10/2018 08:09 PM, Mike Blumenkrantz wro
Hello.
People asked and fixes pilled up. Time for a 1.21.1 release.
If you have fixes in master which should get backported please do it now.
I will put together some pre-release tarballs on Wednesday morning.
regards
Stefan Schmidt
ld be you or your intern,
but I never heard a confirmation on this. If any of the supporters in
this thread want to step up and driving this now would be a good time.
regards
Stefan Schmidt
On 09/04/2018 05:45 PM, Mike Blumenkrantz wrote:
> I've uploaded the script from my intern
ust hacked on it. To the best of my knowledge we have nobody
with a ruby background here though. We could hope that we never come
into the situation that we would need to modify it, but its a risk we
need to keep in mind.
regards
Stefan Schmidt
service being paid out from there would be the right
way. We can acknowledge the sponsorship on our sponsors page.
regards
Stefan Schmidt
--
Check out the vibrant tech community on one of the world's most
engaging tech sit
oposal in a separate mail.
regards
Stefan Schmidt
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_
Hello.
On 08/21/2018 05:00 PM, Stefan Schmidt wrote:
> Hello.
>
> On 08/20/2018 12:09 PM, Stefan Schmidt wrote:
>> Hello.
>>
>> On 08/18/2018 07:27 PM, Ross Vandegrift wrote:
>>> Hello,
>>>
>>> The EFL tarballs are missing some files und
Hello.
On 08/21/2018 04:27 PM, Christophe Sadoine wrote:
> On Sat, 18 Aug 2018 at 08:29, Stefan Schmidt
> wrote:
>>
>> After 12 months of development work we are proud to announce the release of
>> version 1.21 of the Enlightenment Foundation Libraries. In these 12
&g
Hello.
On 08/20/2018 12:09 PM, Stefan Schmidt wrote:
> Hello.
>
> On 08/18/2018 07:27 PM, Ross Vandegrift wrote:
>> Hello,
>>
>> The EFL tarballs are missing some files under src/examples. Is this on
>> purpose? Makefile.in/gitignore differences seem normal,
ill investigate once I have the make
doc issue sorted.
regards
Stefan Schmidt
> Diff of "cd src/examples; find" is below for 1.21.0-beta2, though I noticed
> this by looking at 1.20.7.
>
> Thanks,
> Ross
>
> --- efl-1.21.0-beta2-gittag 2018-08-18 10:23:15.880572641
Hello.
On 08/20/2018 09:41 AM, Simon Lees wrote:
>
>
> On 18/08/2018 08:48, Stefan Schmidt wrote:
>> After 12 months of development work we are proud to announce the release of
>> version 1.21 of the Enlightenment Foundation Libraries. In these 12
>> months we got
>
it and assigned it Derek to have a look. We will make sure
this gets backported and lands into a 1.21.1 release.
https://phab.enlightenment.org/T7327
regards
Stefan Schmidt
> Here's the failure:
> /bin/bash ../libtool --tag=CC --tag=disable-static --mode=link gcc -g -O2
> -fde
After 12 months of development work we are proud to announce the release of
version 1.21 of the Enlightenment Foundation Libraries. In these 12
months we got
almost 5000 commits from 96 authors. Great job everyone! Some highlights
are listed below.
== Download ==
http://download.enlightenment.org
This second, and hopefully last, beta release for 1.21 brings a number
of fixes over the first beta release.
The number of known issues shrunk to just a few left overs we are
working on right now. We appreciate any tester of this to let us know
about problems. This goes for packaging, testing with
Hello.
Many of these problems are no fixed and we are waiting on just a few to
be tested and reviewed. I plan to have a beta2 later today or tomorrow
and hopefully a final release next week with the remaining bugs fixed.
On 07/30/2018 12:16 PM, Stefan Schmidt wrote:
> Hello.
>
> This m
showstopper issues
https://phab.enlightenment.org/maniphest/query/.A.JB1lE_L6b/#R
11) Release notes need to be written
Did I miss anything? Something already fixed?
regards
Stefan Schmidt
--
Check out the vibrant tech
Hello.
On 07/25/2018 08:37 AM, Stefan Schmidt wrote:
> Hello.
>
> On 24.07.2018 11:21, Marcel Hollerbach wrote:
>>
>> What I see as a bug is the fact that ELM_CNP_EVENT_SELECTION_CHANGED was
>> removed ?
>
> Which commit did remove it? Does it mention any rea
This first beta release for 1.21 brings a number of fixes over the alpha
release. A working wayland build from the tarballs for example. We still
have some open issues before we can go further with the release. We
appreciate any tester of this to let us know about problems. This goes
for packaging,
ng up to
> date?
https://www.enlightenment.org/docs/distros/osx-start.md
https://git.enlightenment.org/core/efl.git/tree/.ci/ci-osx-deps.sh
https://git.enlightenment.org/core/efl.git/tree/.ci/ci-osx-build.sh
This is what I used when setting up the osx builds on Travis. Likely
there are more details to
Hello.
On 24.07.2018 11:21, Marcel Hollerbach wrote:
>
> What I see as a bug is the fact that ELM_CNP_EVENT_SELECTION_CHANGED was
> removed ?
Which commit did remove it? Does it mention any reason on it?
Something we need to follow up on.
regards
Stefa
ome light one what happened to
edje_object_color_class_description_get ?
We are looking into API breaks for the 1.21 release and wonder what
happened with this function.
regards
Stefan Schmidt
> On Tue, Jul 24, 2018 at 5:28 AM Stefan Schmidt
> wrote:
>
>> Hello.
>>
>&
ign that can build efl over ssh and we can see how it would
integrate with phab once that is done.
regards
Stefan Schmidt
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashd
Hello.
On 24.07.2018 22:18, jaquil...@eagleeyet.net wrote:
> Leave setup and administration to me.
>
> Is this a green light on this?
I never blocked it. From my side its fine if you want to do this.
regards
Stefa
nything like this though the system should be already
installed with all the efl dependencies and a buld of efl should work
over ssh. If you also want to use this server for debugging I would
argue that you need two different user for the CI and the debugging jobs.
regards
St
ian, etc)
There is no easy filter to get through the list. Some is knowledge
archived over time and some is actually looking at the current code and
figure things out.
regards
Stefan Schmidt
--
Check out the vibrant t
On 24.07.2018 11:19, Carsten Haitzler wrote:
> On Tue, 24 Jul 2018 09:28:05 +0200 Stefan Schmidt
> said:
>
>> Hello.
>>
>> On 23.07.2018 11:11, Carsten Haitzler (The Rasterman) wrote:
>>> On Mon, 23 Jul 2018 09:42:43 +0200 Stefan Schmidt
>>> sai
Hello.
On 24.07.2018 10:46, Stefan Schmidt wrote:
> Hello.
>
> One of the big missing steps towards a 1.21 release is to make sure we
> are not breaking ABI or API from older releases. If you want to help
> with the release please spare an hour and look over the report from ABI
&
APIs.
https://abi-laboratory.pro/index.php?view=objects_report&l=efl&v1=1.20.7&v2=1.21.0-alpha1
regards
Stefan Schmidt
--
Check out the vibrant tech community on one of the world's most
engaging tech si
Hello.
On 23.07.2018 11:11, Carsten Haitzler (The Rasterman) wrote:
> On Mon, 23 Jul 2018 09:42:43 +0200 Stefan Schmidt
> said:
>
>> Hello.
>>
>> On 23.07.2018 06:59, jaquil...@eagleeyet.net wrote:
>>> Hi Guys,
>>>
>>> I am willing to work o
#x27;s harbourmaster.
regards
Stefan Schmidt
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
en
> What do you guys think?
You know that we already have CI testing on OSX via TravisCI?
What would this do better than the current CI setup we have?
https://travis-ci.org/Enlightenment/efl (look at the build job with an
apple as lo
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 S
. Nightly
builds make it clear.
I really see no need for this. People that update often will use git
imho and not use nighlies for this. I am pretty much biased here as I am
a developer using git anyway and not a user, though.
regards
Stefa
Hello.
On 13.07.2018 10:57, Boris Faure wrote:
> On 18-07-13 10:42, Stefan Schmidt wrote:
>> Hello.
>>
>> On 23.05.2018 12:24, Boris Faure wrote:
>>> I was looking at coverity on Terminology and it is currently not
>>> analyzing any build since 2018-04-15.
ed for
testing at the users systems. These should only ship with verified fixes.
regards
Stefan Schmidt
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.li
anual build I did.
Anything special you did to get this working locally for you? What is
your coverity tools version?
regards
Stefan Schmidt
--
Check out the vibrant tech community on one of the world&#x
orked on during a given release.
regards
Stefan Schmidt
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
__
on alone.
> Regardless of whether you follow through with your plan to step down from
> managing releases, I just want to say thanks for all the time and effort
> you've put into managing releases over
e automation on this.
regards
Stefan Schmidt
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
his could be split of to people
without a core developer background easily.
regards
Stefan Schmidt
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm
ter or slower depending on how critical the backports have been.
With 1.20 and now 1.21 the schedules are all messed up. I would agree
that coming back to more frequent stable updates make sense.
regards
Stefan Schmidt
--
.enlightenment.org/core/efl.git/tree/.travis.yml#n62
docker run -v `pwd`:/src -w /src stefanschmidt1/ci-support-files:$DISTRO
/src/.ci/ci-linux-build.sh $CI_BUILD_TYPE
regards
Stefan Schmidt
--
Check out the vibrant
Hello.
On 10.07.2018 10:43, Derek Foreman wrote:
> I've created a phab ticket for this at T7120 and am testing a fix for it
> now.
This has landed and will be used for the next tarballs I generate which
should get this fixed. Thanks for the reports.
regards
Ste
step down from the release
manager role. I tried to form a release team for many years so far but
failed in getting anyone interested. By stepping down I kind of forcing
this change, hopefully for the better.
regards
Stefan Schmidt
--
This alpha release for 1.21 starts the freeze period and stabilization
phase for the 1.21 release cycle. There are still problems to fix and we
appreciate any tester of this to let us know about problems seen. This
goes for packaging, testing with efl based applications, integration
into your syste
hello.
On 04.07.2018 20:09, Stefan Schmidt wrote:
> Hello.
>
> On 27.06.2018 20:17, Mike Blumenkrantz wrote:
>> See the weekly phab report mails which lists ticket/patch counts for high
>> priority items.
>>
>> A number of the highest priority tickets will be
phab in general tomorrow to get a
better understanding where we stand and when we can start the alpha.
Thanks to everyone who organised the bug tracker and fixed bugs while I
was away!
regards
Stefan Schmidt
--
Ch
contrast to
the first statement where I have to put everything on hold until the
whole patch queue is fully reviewed. Its that part I find unrealistic.
regards
Stefan Schmidt
--
Check out the vibrant tech community o
asically the same
as holding it up for a feature to be merged. Both require developer time
that might or might not be available at the time for the release.
regards
Stefan Schmidt
--
Check out the vibrant tech community on one
v branch build on it before you consider
merging it into master.
regards
Stefan Schmidt
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http:
Hello
On 18.05.2018 06:45, Carsten Haitzler (The Rasterman) wrote:
> On Thu, 17 May 2018 13:14:48 +0200 Stefan Schmidt
> said:
>
>> Hello.
>>
>> Another update on this.
>>
>> On 08.05.2018 21:41, Stefan Schmidt wrote:
>>>
>>> On 04/27/201
w. We could
move it to a separate channel (like we have with e-commits), but this
also means less visibility to the reports.
regards
Stefan Schmidt
--
Check out the vibrant tech community on one of the world's most
eng
Hello.
Another update on this.
On 08.05.2018 21:41, Stefan Schmidt wrote:
>
> On 04/27/2018 01:38 PM, Stefan Schmidt wrote:
>
> There sadly has not been as much progress as hoped for.
> I still wait for the following items:
>
> o Cedric's last branch to be merged
ated schedule is really mood. If we do not meeting
content which is worthwhile nobody will show up no matter how convenient the
time is for them.
Marcel took the step to setup time, agenda, etc for this meeting. Let's honor
this and see during the meeting if the time needs
t; I will keep in mind your advice. Thank you.
>
Thanks for getting this fixed quickly.
regards
Stefan Schmidt
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Sla
x27;!strcmp(type, "Elm_Slider")' failed
I would the author as well as the reviewer/committer to run the test
suite with such a big re-factor change. Having the cxx bindings disabled
locally for you is also not the best idea when testing things.
regards
Stefan Schmidt
--
Hello.
On 04/27/2018 01:38 PM, Stefan Schmidt wrote:
> Hello.
>
>
> Its been a while. About to get our act together and get everything in place
> so we can start the 1.21 stabilization phase.
>
> We had this brought up at the two IRC meetings we had and I wanted to reach
on instead of having to spent time to find out
why its broken again.
I think the revert is fine in this case. Not picking on you, it was just the
first revert I saw after thinking on this a bit more.
regards
Stefan Schmidt
tting me know.
I added this to the list of items that need to land before we start the
stabilization.
regards
Stefan Schmidt
--
Check out the vibrant tech community on one of the world's most
engagi
nge of release manager duties. This
>should a) help to reduce the pain doing it and b) spread the
knowledge throughout the developer team.
regards
Stefan Schmidt
--
Check out the vibrant tech community on one
Hello.
On 04/26/2018 12:41 PM, Taehyub Kim wrote:
> jaehyun pushed a commit to branch master.
>
> http://git.enlightenment.org/core/efl.git/commit/?id=6e49db0739c38a378c48c6c880f5b41c986ee1e9
>
> commit 6e49db0739c38a378c48c6c880f5b41c986ee1e9
> Author: Taehyub Kim
> Date: Thu Apr 26 19:27:43
er workflow for this would be:
Do your work in a branch -> push this branch to your devs/ namespace to the
server -> Check result on Travis build -> if all is fine push
for review or merge into master
regards
Stefan Schmidt
---
ve a new run of the scanner. I
just wanted to get it out in case other people wanted to
have a look what it can offer and maybe fix some real problems found.
regards
Stefan Schmidt
--
Check out the vibrant tech communit
Hello.
On 04/20/2018 07:22 AM, Christophe Sadoine wrote:
> 2018年4月19日(木) 6:16 Christophe Sadoine :
>
>> On 18 April 2018 at 18:12, Stefan Schmidt wrote:
>>> This ticket has items on:
>>>
>>> o How to handle EFL proposals
>>> o Project and or re
Hello.
On 04/18/2018 10:57 AM, Carsten Haitzler (The Rasterman) wrote:
> On Wed, 18 Apr 2018 10:32:46 +0200 Stefan Schmidt
> said:
>
>> Hello.
>>
>>
>> On 04/18/2018 09:59 AM, Carsten Haitzler (The Rasterman) wrote:
>>> specifically:
>>>
>
this ticket as the agenda for the meeting or only
the discussion on timed vs feature release and project roadmap?
Having a clear agenda for the meeting should help us to stay focused and maybe
even come to some conclusio
handled per patch.
regards
Stefan Schmidt
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
enlig
enu:
> free(dbus_menu);
>
You commit message does only mention adding the const qualifier but nothing
about this iterator free you remove.
Are you sure this is right or has this been committed accidentally?
regards
Stefan Schmidt
ays where I asked someone to stop using it.
If this is a misconfiguration, please fix it.
If someone really wants to bring in a DCO and start using SOB's with a real
meaning, bring it up here so we can discuss it.
regards
Stefan Schmidt
--
u renamed the files but did not rename the filennames in the Makefile.
This broke the build of the examples.
If you are pushing such a big patch I would expect you to run make examples if
you changed something there to make at least sure it compiles.
I am fixing this right now.
regards
Stefan Schm
+++--
> src/lib/elementary/efl_ui_dnd.c | 1 +
> src/lib/evas/canvas/evas_object_inform.c | 3 ++-
> 4 files changed, 14 insertions(+), 3 deletions(-)
>
These are 4 different problems you are fixing in 4 different library parts.
It would be appreciated if you could have separate
cate of origin to find out what SOB is
used for).
And clearly this this SOB was manually added, git would have formatted it
differently. :-)
regards
Stefan Schmidt
--
Check out the vibrant tech community on one o
201 - 300 of 3266 matches
Mail list logo
