Re: [E-devel] EFL Alpha Release: Action Required
>From what I remember, that issue was happened before. Eflete may have a logical bug. On Fri, Jul 6, 2018 at 12:57 AM, Mike Blumenkrantz < michael.blumenkra...@gmail.com> wrote: > As I've said before, the eflete issue should never have been considered an > EFL issue. If it's going to be listed as something that time needs to be > spent on then I'll debunk the possibility more formally: > > #0 0x7020ef54 in ecore_file_recursive_rm (dir=0x14d81a0 > "/home/zmike/") at lib/ecore_file/ecore_file.c:326 > #1 0x0045d293 in _exist_permission_popup_close_cb > (data=0x195ce80, > obj=0x40145654, event_info=0x10) > at ../../src/bin/ui/project_common.c:60 > #2 0x727ba9c0 in _eo_evas_smart_cb (data=0x165ad10, > event=0x7fffd030) > at lib/evas/canvas/evas_object_smart.c:78 > #3 0x7fffedef8000 in _event_callback_call (obj_id=0x40145654, > pd=0x101c5b0, desc=0x150c9f0, event_info=0x10, legacy_compare=1 '\001') at > lib/eo/eo_base_class.c:1694 > #4 0x7fffedef8341 in _efl_object_event_callback_legacy_call > (obj_id=0x40145654, pd=0x101c5b0, desc=0x150c9f0, event_info=0x10) at > lib/eo/eo_base_class.c:1767 > #5 0x7fffedef83e7 in efl_event_callback_legacy_call > (obj=0x40145654, desc=0x150c9f0, event_info=0x10) > at lib/eo/eo_base_class.c:1770 > #6 0x727a8d54 in > _efl_canvas_object_efl_object_event_callback_legacy_call > (eo_obj=0x40145654, obj=0x101c600, desc=0x150c9f0, event_info=0x10) at > lib/evas/canvas/evas_object_main.c:1231 > #7 0x7fffedef83e7 in efl_event_callback_legacy_call > (obj=0x40145654, desc=0x150c9f0, event_info=0x10) > at lib/eo/eo_base_class.c:1770 > #8 0x727bd2b4 in evas_object_smart_callback_call > (eo_obj=0x40145654, event=0x4ffd73 "POPUP_CLOSE_CB", event_info=0x10) > at lib/evas/canvas/evas_object_smart.c:1043 > #9 0x00459438 in _popup_btn_cb (data=0x10, obj=0x4015b679, > ei=0x0) at ../../src/bin/ui/popup.c:103 > #10 0x727ba9c0 in _eo_evas_smart_cb (data=0xf2e990, > event=0x7fffd320) > at lib/evas/canvas/evas_object_smart.c:78 > #11 0x7fffedef8000 in _event_callback_call (obj_id=0x4015b679, > pd=0x11b6610, desc=0x7fffee361240 <_EFL_UI_EVENT_CLICKED>, event_info=0x0, > legacy_compare=1 '\001') at lib/eo/eo_base_class.c:1694 > #12 0x7fffedef8341 in _efl_object_event_callback_legacy_call > (obj_id=0x4015b679, pd=0x11b6610, desc=0x7fffee361240 > <_EFL_UI_EVENT_CLICKED>, event_info=0x0) at lib/eo/eo_base_class.c:1767 > #13 0x7fffedef83e7 in efl_event_callback_legacy_call > (obj=0x4015b679, desc=0x7fffee361240 <_EFL_UI_EVENT_CLICKED>, > event_info=0x0) at lib/eo/eo_base_class.c:1770 > #14 0x727a8d54 in > _efl_canvas_object_efl_object_event_callback_legacy_call > (eo_obj=0x4015b679, obj=0x11b6660, desc=0x7fffee361240 > <_EFL_UI_EVENT_CLICKED>, event_info=0x0) at > lib/evas/canvas/evas_object_main.c:1231 > #15 0x7fffedef83e7 in efl_event_callback_legacy_call > (obj=0x4015b679, desc=0x7fffee361240 <_EFL_UI_EVENT_CLICKED>, > event_info=0x0) at lib/eo/eo_base_class.c:1770 > #16 0x778582d6 in _activate (obj=0x4015b679) at > lib/elementary/efl_ui_button.c:74 > #17 0x77858509 in _on_clicked_signal (data=0x4015b679, > obj=0x40122e7a, emission=0xc43d7c "elm,action,click", > source=0x7fffedcc4208 "") at lib/elementary/efl_ui_button.c:126 > #18 0x7397f2b7 in edje_match_callback_exec_check_finals > (ssp=0xccc560, matches=0xc6b7f0, signal_states=0xccc670, > source_states=0xc743c0, sig=0xc43d7c "elm,action,click", > source=0x7fffedcc4208 "", ed=0x12a5ec0, prop=0 '\000') > at lib/edje/edje_match.c:556 > #19 0x7397f7ec in edje_match_callback_exec (ssp=0xccc560, > matches=0xc6b7f0, sig=0xc43d7c "elm,action,click", source=0x7fffedcc4208 > "", ed=0x12a5ec0, prop=0 '\000') at lib/edje/edje_match.c:711 > #20 0x73988a09 in _edje_emit_cb (ed=0x12a5ec0, sig=0xc43d7c > "elm,action,click", src=0x7fffedcc4208 "", data=0x14ce7a0, prop=0 '\000') > at lib/edje/edje_program.c:1647 > #21 0x73988854 in _edje_emit_handle (ed=0x12a5ec0, sig=0xc43d7c > "elm,action,click", src=0x7fffedcc4208 "", sdata=0x14ce7a0, prop=0 '\000') > at lib/edje/edje_program.c:1589 > #22 0x73981edc in _edje_message_process (em=0x154bce0) at > lib/edje/edje_message_queue.c:783 > #23 0x739822f4 in _edje_message_queue_process () at > lib/edje/edje_message_queue.c:886 > #24 0x73980ede in _edje_job (data=0x0) at > lib/edje/edje_message_queue.c:260 > #25 0x7fffee89a51f in _ecore_job_event_handler (data=0x0, type=14, > ev=0x1a09720) at lib/ecore/ecore_job.c:98 > #26 0x7fffee8a0edd in > _ecore_event_message_handler_efl_loop_message_handler_message_call > (obj=0x4000141f, pd=0x79bb50, message=0x400c8bde) at > lib/ecore/ecore_event_message_handler.c:359 > #27 0x7fffee8ab5b1 in efl_loop_message_handler_message_call > (obj=0x4000141f, message=0x400c8bde) > at
Re: [E-devel] EFL Alpha Release: Action Required
As I've said before, the eflete issue should never have been considered an EFL issue. If it's going to be listed as something that time needs to be spent on then I'll debunk the possibility more formally: #0 0x7020ef54 in ecore_file_recursive_rm (dir=0x14d81a0 "/home/zmike/") at lib/ecore_file/ecore_file.c:326 #1 0x0045d293 in _exist_permission_popup_close_cb (data=0x195ce80, obj=0x40145654, event_info=0x10) at ../../src/bin/ui/project_common.c:60 #2 0x727ba9c0 in _eo_evas_smart_cb (data=0x165ad10, event=0x7fffd030) at lib/evas/canvas/evas_object_smart.c:78 #3 0x7fffedef8000 in _event_callback_call (obj_id=0x40145654, pd=0x101c5b0, desc=0x150c9f0, event_info=0x10, legacy_compare=1 '\001') at lib/eo/eo_base_class.c:1694 #4 0x7fffedef8341 in _efl_object_event_callback_legacy_call (obj_id=0x40145654, pd=0x101c5b0, desc=0x150c9f0, event_info=0x10) at lib/eo/eo_base_class.c:1767 #5 0x7fffedef83e7 in efl_event_callback_legacy_call (obj=0x40145654, desc=0x150c9f0, event_info=0x10) at lib/eo/eo_base_class.c:1770 #6 0x727a8d54 in _efl_canvas_object_efl_object_event_callback_legacy_call (eo_obj=0x40145654, obj=0x101c600, desc=0x150c9f0, event_info=0x10) at lib/evas/canvas/evas_object_main.c:1231 #7 0x7fffedef83e7 in efl_event_callback_legacy_call (obj=0x40145654, desc=0x150c9f0, event_info=0x10) at lib/eo/eo_base_class.c:1770 #8 0x727bd2b4 in evas_object_smart_callback_call (eo_obj=0x40145654, event=0x4ffd73 "POPUP_CLOSE_CB", event_info=0x10) at lib/evas/canvas/evas_object_smart.c:1043 #9 0x00459438 in _popup_btn_cb (data=0x10, obj=0x4015b679, ei=0x0) at ../../src/bin/ui/popup.c:103 #10 0x727ba9c0 in _eo_evas_smart_cb (data=0xf2e990, event=0x7fffd320) at lib/evas/canvas/evas_object_smart.c:78 #11 0x7fffedef8000 in _event_callback_call (obj_id=0x4015b679, pd=0x11b6610, desc=0x7fffee361240 <_EFL_UI_EVENT_CLICKED>, event_info=0x0, legacy_compare=1 '\001') at lib/eo/eo_base_class.c:1694 #12 0x7fffedef8341 in _efl_object_event_callback_legacy_call (obj_id=0x4015b679, pd=0x11b6610, desc=0x7fffee361240 <_EFL_UI_EVENT_CLICKED>, event_info=0x0) at lib/eo/eo_base_class.c:1767 #13 0x7fffedef83e7 in efl_event_callback_legacy_call (obj=0x4015b679, desc=0x7fffee361240 <_EFL_UI_EVENT_CLICKED>, event_info=0x0) at lib/eo/eo_base_class.c:1770 #14 0x727a8d54 in _efl_canvas_object_efl_object_event_callback_legacy_call (eo_obj=0x4015b679, obj=0x11b6660, desc=0x7fffee361240 <_EFL_UI_EVENT_CLICKED>, event_info=0x0) at lib/evas/canvas/evas_object_main.c:1231 #15 0x7fffedef83e7 in efl_event_callback_legacy_call (obj=0x4015b679, desc=0x7fffee361240 <_EFL_UI_EVENT_CLICKED>, event_info=0x0) at lib/eo/eo_base_class.c:1770 #16 0x778582d6 in _activate (obj=0x4015b679) at lib/elementary/efl_ui_button.c:74 #17 0x77858509 in _on_clicked_signal (data=0x4015b679, obj=0x40122e7a, emission=0xc43d7c "elm,action,click", source=0x7fffedcc4208 "") at lib/elementary/efl_ui_button.c:126 #18 0x7397f2b7 in edje_match_callback_exec_check_finals (ssp=0xccc560, matches=0xc6b7f0, signal_states=0xccc670, source_states=0xc743c0, sig=0xc43d7c "elm,action,click", source=0x7fffedcc4208 "", ed=0x12a5ec0, prop=0 '\000') at lib/edje/edje_match.c:556 #19 0x7397f7ec in edje_match_callback_exec (ssp=0xccc560, matches=0xc6b7f0, sig=0xc43d7c "elm,action,click", source=0x7fffedcc4208 "", ed=0x12a5ec0, prop=0 '\000') at lib/edje/edje_match.c:711 #20 0x73988a09 in _edje_emit_cb (ed=0x12a5ec0, sig=0xc43d7c "elm,action,click", src=0x7fffedcc4208 "", data=0x14ce7a0, prop=0 '\000') at lib/edje/edje_program.c:1647 #21 0x73988854 in _edje_emit_handle (ed=0x12a5ec0, sig=0xc43d7c "elm,action,click", src=0x7fffedcc4208 "", sdata=0x14ce7a0, prop=0 '\000') at lib/edje/edje_program.c:1589 #22 0x73981edc in _edje_message_process (em=0x154bce0) at lib/edje/edje_message_queue.c:783 #23 0x739822f4 in _edje_message_queue_process () at lib/edje/edje_message_queue.c:886 #24 0x73980ede in _edje_job (data=0x0) at lib/edje/edje_message_queue.c:260 #25 0x7fffee89a51f in _ecore_job_event_handler (data=0x0, type=14, ev=0x1a09720) at lib/ecore/ecore_job.c:98 #26 0x7fffee8a0edd in _ecore_event_message_handler_efl_loop_message_handler_message_call (obj=0x4000141f, pd=0x79bb50, message=0x400c8bde) at lib/ecore/ecore_event_message_handler.c:359 #27 0x7fffee8ab5b1 in efl_loop_message_handler_message_call (obj=0x4000141f, message=0x400c8bde) at lib/ecore/efl_loop_message_handler.eo.c:14 #28 0x7fffee8a6229 in _efl_loop_message_process (obj=0x401a, pd=0x791a60) at lib/ecore/efl_loop.c:633 #29 0x7fffee8a641a in efl_loop_message_process (obj=0x401a) at lib/ecore/efl_loop.c:663 #30 0x7fffee89ea06 in _ecore_main_loop_iterate_internal (obj=0x401a, pd=0x791a60, once_only=0) at
Re: [E-devel] EFL Alpha Release: Action Required
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 resolved over the next 24h >> as patches continue to land from the review queue. If people continue to >> work on the high priority tickets which are tagged with the 1.21 milestone >> then it should be possible for Stefan to begin executing an alpha release >> very soon after he returns next week. > > I am back no and catched up on mails. > > Will go through the phab queries and phab in general tomorrow to get a > better understanding where we stand and when we can start the alpha. So here is how I see the situation regarding the release status. Following the pre-defined queries Mike uses in the phab weekly mails I can see 4 showstopper issues (2 of them them to have been dealt with already), 10 issues raised as prio high and 4 issues tagged as regressions. This looks like a good enough starting point to me to get an alpha out and getting the remaining bugs fixed. If I compare this other releases I managed we started the alpha actually in a worse state. (If we would start the alpha with zero bugs we would not need one anyway. :-) My proposal from here would be the following: o I tag the alpha release tomorrow and prepare and upload tarballs o We asked packagers to try out these tarballs to get early feedback from them o We ask application maintainers to test their app against the alpha release and report bugs so we can still fix them (based on Hermet's suggestion) o I run abi-checker over the alpha release to see if it detects abi/api breaks we need to take care of o I will have a look if I can figure out whats wrong with our coverity builds. This is going on for a while, not sure I can promise that I will get this fixed in time. o We need to spent some extra time to make sure the home-dir-deleted-by-eflete bug is actually an application bug and nothing present in efl. The following are the issues I consider for the release right now. If you have one that is not listed here but should, please make sure to update the tags accordingly so its shows up in the queries. For showstopper and high prio issues: https://phab.enlightenment.org/maniphest/query/_jTUZLoOpCeA/#R For regressions: https://phab.enlightenment.org/maniphest/query/oP4HVQ1SXYSe/#R If you disagree with any of this speak up NOW. :-) 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 ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] EFL Alpha Release: Action Required
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 resolved over the next 24h > as patches continue to land from the review queue. If people continue to > work on the high priority tickets which are tagged with the 1.21 milestone > then it should be possible for Stefan to begin executing an alpha release > very soon after he returns next week. I am back no and catched up on mails. Will go through the phab queries and 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 -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] EFL Alpha Release: Action Required
See the weekly phab report mails which lists ticket/patch counts for high priority items. A number of the highest priority tickets will be resolved over the next 24h as patches continue to land from the review queue. If people continue to work on the high priority tickets which are tagged with the 1.21 milestone then it should be possible for Stefan to begin executing an alpha release very soon after he returns next week. On Wed, Jun 27, 2018 at 10:37 AM Stephen Houston wrote: > Good Morning -- > > I just wanted to get an update on where we are with this and what is still > prioritized to get an alpha out? > > Stephen > > On Thu, Jun 14, 2018 at 8:19 AM Mike Blumenkrantz < > michael.blumenkra...@gmail.com> wrote: > > > Update: this is the query which should now be used for finding high > > priority tickets, as it excludes tickets which are not slated for review > in > > 1.21: > > https://phab.enlightenment.org/maniphest/query/hpAKElh.jGsu/#R > > > > If any tickets on this list do not seem to be within the scope of a > release > > which should happen within the next month then the 1.21 milestone tag > > should be removed. > > > > On Mon, Jun 11, 2018 at 1:34 PM Mike Blumenkrantz < > > michael.blumenkra...@gmail.com> wrote: > > > > > Hi, > > > > > > I'd like to attempt an alpha release by end of next week (22 June 2018) > > at > > > latest. The following action should be taken by all active > contributors: > > > > > > * Examine the list of high priority tickets and see if there is > anything > > > you can help with > > > https://phab.enlightenment.org/maniphest/query/C.4F6YJs0qVJ/#R > > > > > > * Examine the list of incoming tickets and see if there is anything you > > > can help with or triage > > > https://phab.enlightenment.org/maniphest/query/.A.JB1lE_L6b/#R > > > > > > * Check tickets assigned to you to see if there are any tickets which > > > should be triaged to a different priority > > > > > > Ideally we should have a good idea of where things stand within a few > > days > > > so we can determine what needs to be fixed before an alpha goes out. > > > > > > Regards, > > > Mike > > > > > > > > -- > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > ___ > > enlightenment-devel mailing list > > enlightenment-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > > > > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > ___ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] EFL Alpha Release: Action Required
Good Morning -- I just wanted to get an update on where we are with this and what is still prioritized to get an alpha out? Stephen On Thu, Jun 14, 2018 at 8:19 AM Mike Blumenkrantz < michael.blumenkra...@gmail.com> wrote: > Update: this is the query which should now be used for finding high > priority tickets, as it excludes tickets which are not slated for review in > 1.21: > https://phab.enlightenment.org/maniphest/query/hpAKElh.jGsu/#R > > If any tickets on this list do not seem to be within the scope of a release > which should happen within the next month then the 1.21 milestone tag > should be removed. > > On Mon, Jun 11, 2018 at 1:34 PM Mike Blumenkrantz < > michael.blumenkra...@gmail.com> wrote: > > > Hi, > > > > I'd like to attempt an alpha release by end of next week (22 June 2018) > at > > latest. The following action should be taken by all active contributors: > > > > * Examine the list of high priority tickets and see if there is anything > > you can help with > > https://phab.enlightenment.org/maniphest/query/C.4F6YJs0qVJ/#R > > > > * Examine the list of incoming tickets and see if there is anything you > > can help with or triage > > https://phab.enlightenment.org/maniphest/query/.A.JB1lE_L6b/#R > > > > * Check tickets assigned to you to see if there are any tickets which > > should be triaged to a different priority > > > > Ideally we should have a good idea of where things stand within a few > days > > so we can determine what needs to be fixed before an alpha goes out. > > > > Regards, > > Mike > > > > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > ___ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] EFL Alpha Release: Action Required
Update: this is the query which should now be used for finding high priority tickets, as it excludes tickets which are not slated for review in 1.21: https://phab.enlightenment.org/maniphest/query/hpAKElh.jGsu/#R If any tickets on this list do not seem to be within the scope of a release which should happen within the next month then the 1.21 milestone tag should be removed. On Mon, Jun 11, 2018 at 1:34 PM Mike Blumenkrantz < michael.blumenkra...@gmail.com> wrote: > Hi, > > I'd like to attempt an alpha release by end of next week (22 June 2018) at > latest. The following action should be taken by all active contributors: > > * Examine the list of high priority tickets and see if there is anything > you can help with > https://phab.enlightenment.org/maniphest/query/C.4F6YJs0qVJ/#R > > * Examine the list of incoming tickets and see if there is anything you > can help with or triage > https://phab.enlightenment.org/maniphest/query/.A.JB1lE_L6b/#R > > * Check tickets assigned to you to see if there are any tickets which > should be triaged to a different priority > > Ideally we should have a good idea of where things stand within a few days > so we can determine what needs to be fixed before an alpha goes out. > > Regards, > Mike > -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
[E-devel] EFL Alpha Release: Action Required
Hi, I'd like to attempt an alpha release by end of next week (22 June 2018) at latest. The following action should be taken by all active contributors: * Examine the list of high priority tickets and see if there is anything you can help with https://phab.enlightenment.org/maniphest/query/C.4F6YJs0qVJ/#R * Examine the list of incoming tickets and see if there is anything you can help with or triage https://phab.enlightenment.org/maniphest/query/.A.JB1lE_L6b/#R * Check tickets assigned to you to see if there are any tickets which should be triaged to a different priority Ideally we should have a good idea of where things stand within a few days so we can determine what needs to be fixed before an alpha goes out. Regards, Mike -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
