Re: [E-devel] Next Release

[Stefan Schmidt]

Hello Vincent.

On 09.01.19 18:24, Vincent Torri wrote:
> Hello
> 
>> The second big step towards a release is to go through all of the issue
>> report we have open and see if they have categories assigned. Making
>> sure to mark the important ones as showstopper (but not 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 on as normal.

regards
Stefan Schmidt


___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Re: [E-devel] Next Release

[Mike Blumenkrantz]

No

On Wed, Jan 9, 2019 at 12:25 PM Vincent Torri 
wrote:

> Hello
>
> > The second big step towards a release is to go through all of the issue
> > report we have open and see if they have categories assigned. Making
> > sure to mark the important ones as showstopper (but not every pet peave
> > bug should be listed there).
>
> is it too late to add an API ?
>
> Vincent
>
>
> ___
> enlightenment-devel mailing list
> enlightenment-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
>

___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Re: [E-devel] Next Release

[Vincent Torri]

Hello

> The second big step towards a release is to go through all of the issue
> report we have open and see if they have categories assigned. Making
> sure to mark the important ones as showstopper (but not every pet peave
> bug should be listed there).

is it too late to add an API ?

Vincent


___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Re: [E-devel] Next Release

[Stefan Schmidt]

Hello Jonathon.

On 02.01.19 10:38, Jonathan Aquilina wrote:
> Hi All,
> 
> I have a quick question who is taking care of the next release since Stefan 
> has stepped down? I am willing to setup if necessary. Do we have a time line 
> for the next release?

Sorry for the delay. I was on vacation until this week.

A few people offered to help with a release but none stepped up to take
the full lead on the next one. Maybe its easier if I will be part of the
team so I can transfer the knowledge more smoothly instead of dropping
things?

With a team of other willing to work towards regular releases I am ok to
spend some time on working on this as well.

To get time based releases back into our DNA I think that we should get
one out again soon to get into the habit again of doing it. It should
not wait on specific features and we need to thing about the time
between releases after it again (one every 3 months seems to much. Maybe
every 4 or 5 months? we need to discuss this).

I am going to put together a release schedule proposal and sent it to
the list as first step.

In terms of splitting the load I would appreciate it if you could get
yourself familiar with my notes on how I did the releases.

https://phab.enlightenment.org/w/release_procedure/

Read through it and try to generate a tarball locally to see if that
works for you. If you find unclear parts feel free to correct the wiki
or ask. More than likely there are parts in it that make sense to me but
nobody else. :-)

The second big step towards a release is to go through all of the issue
report we have open and see if they have categories assigned. Making
sure to mark the important ones as showstopper (but not every pet peave
bug should be listed there).

Once we have this we can talk how to prepare the work items mails I have
been sending out on a regular basis and how people can help with this.

As a sidenote: this would be our last autotools based release. That
means the official release tarballs will be generated with the autotools
build system. In parallel we will work on getting a tarball 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
Stefan Schmidt


___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Re: [E-devel] Next release

[The Rasterman]

On Fri, 3 Jun 2016 16:24:55 -0700 Cedric BAIL  said:

> Hello,
> 
> I just would like to start a thread regarding what is still pending
> for next release and what we should do about it. First let's start
> with what is not ready :
> - Most of the elementary widgets have not been renamed correctly to be
> in efl.ui namespace.
> - Edje and Elm.Layout have not been refactorized and properly
> inherited from each other.
> - Text interface is not there (this impact also entry, label and edje).
> - Genlist is also not there.
> - All eo object still needs a proper cleanup and use of own().
> - Uri manager is not there.
> - Color/Color_Class is not there.
> - Efl photocam is not there.
> - Efl video is not there.
> - Efl.Ui.Window is not there.
> - Efl.Ui.Focus cleanup is not there.
> 
> Sone of the above have patch in review process that may land before
> Monday morning, but I prefer to just give the current status as I may
> not have time this weekend as I am moving. Also most of the API that
> have landed so far have not been tested in any real application and we
> don't really if they do fit their purpose (making life easier).
> 
> It is obvious to me, and I am pretty to sure to everyone involved in
> the development of 1.18 that we can not do an alpha while some of the
> biggest change are not there yet. Now the question is should we delay
> the alpha ? Or should we make the alpha a technical preview followed
> by an alpha later on ? Should we just move on and delay the above
> change for 1.19, in which case all the new API need to remain BETA.
> Also if we do delay, how much longer is needed for a release ? Isn't
> it going to drag on ?
> 
> Oh and did I miss anything in the above list ?

no release until promises are shippable. they are not. they need the same
safety that eo objects have as now promises are objects needing tracking just
like eo objects.


-- 
- Codito, ergo sum - "I code, therefore I am" --
The Rasterman (Carsten Haitzler)ras...@rasterman.com


--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Re: [E-devel] Next release

[Stefan Schmidt]

Hello.

On 07/06/16 20:19, Davide Andreoli wrote:
> 2016-06-07 17:20 GMT+02:00 Stefan Schmidt :
>
>> Hello.
>>
>> On 05/06/16 14:27, Tom Hacohen wrote:
>>> On 05/06/16 10:47, Tom Hacohen wrote:
 On 04/06/16 00:24, Cedric BAIL wrote:
> Hello,
>
> I just would like to start a thread regarding what is still pending
> for next release and what we should do about it. First let's start
> with what is not ready :
> - Most of the elementary widgets have not been renamed correctly to be
> in efl.ui namespace.
> - Edje and Elm.Layout have not been refactorized and properly
> inherited from each other.
> - Text interface is not there (this impact also entry, label and edje).
> - Genlist is also not there.
> - All eo object still needs a proper cleanup and use of own().
> - Uri manager is not there.
> - Color/Color_Class is not there.
> - Efl photocam is not there.
> - Efl video is not there.
> - Efl.Ui.Window is not there.
> - Efl.Ui.Focus cleanup is not there.
>
> Sone of the above have patch in review process that may land before
> Monday morning, but I prefer to just give the current status as I may
> not have time this weekend as I am moving. Also most of the API that
> have landed so far have not been tested in any real application and we
> don't really if they do fit their purpose (making life easier).
>
> It is obvious to me, and I am pretty to sure to everyone involved in
> the development of 1.18 that we can not do an alpha while some of the
> biggest change are not there yet. Now the question is should we delay
> the alpha ? Or should we make the alpha a technical preview followed
> by an alpha later on ? Should we just move on and delay the above
> change for 1.19, in which case all the new API need to remain BETA.
> Also if we do delay, how much longer is needed for a release ? Isn't
> it going to drag on ?
>
> Oh and did I miss anything in the above list ?
>
 Also:

 eo->efl renaming, not a biggie, but needs to be done.
 As for text, we hope to be done with it by next Tuesday.

 I'll let you know if anything else comes to mind.
>>> Another thing that is kinda related to the first item on your list: we
>>> need to make sure to remove all of the evas/edje/elm whatever references
>>> in our eo files and class names. For example, Efl.Canvas.Text still
>>> inherits from Evas.Object, which is bad.
>> All of the above are exception for the current freeze. Plus the eolian
>> work from Daniel which I was told will not effect our C API at all.
>>
>> While I find this unsettling and unfair to have a freeze for some parts
>> and not for other I hope people can life with it this time. The problem
>> is that the interface work is done far enough that we can't really back
>> it out anymore. :/
>>
>> Please guys keep me updated on what is done from this list and what
>> still missing. Moved the alpha from this week to next and will hopefully
>> get a snapshot out this week to get at least some people test all the
>> repo merges we did from a packager and user perspective.
>>
> I still need to add some more missing FDO icons in the next 2 weeks,
> I hope this will not be considered as new features.

If it is only image files thats fine.

regards
Stefan Schmidt

--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Re: [E-devel] Next release

[Davide Andreoli]

2016-06-07 17:20 GMT+02:00 Stefan Schmidt :

> Hello.
>
> On 05/06/16 14:27, Tom Hacohen wrote:
> > On 05/06/16 10:47, Tom Hacohen wrote:
> >> On 04/06/16 00:24, Cedric BAIL wrote:
> >>> Hello,
> >>>
> >>> I just would like to start a thread regarding what is still pending
> >>> for next release and what we should do about it. First let's start
> >>> with what is not ready :
> >>> - Most of the elementary widgets have not been renamed correctly to be
> >>> in efl.ui namespace.
> >>> - Edje and Elm.Layout have not been refactorized and properly
> >>> inherited from each other.
> >>> - Text interface is not there (this impact also entry, label and edje).
> >>> - Genlist is also not there.
> >>> - All eo object still needs a proper cleanup and use of own().
> >>> - Uri manager is not there.
> >>> - Color/Color_Class is not there.
> >>> - Efl photocam is not there.
> >>> - Efl video is not there.
> >>> - Efl.Ui.Window is not there.
> >>> - Efl.Ui.Focus cleanup is not there.
> >>>
> >>> Sone of the above have patch in review process that may land before
> >>> Monday morning, but I prefer to just give the current status as I may
> >>> not have time this weekend as I am moving. Also most of the API that
> >>> have landed so far have not been tested in any real application and we
> >>> don't really if they do fit their purpose (making life easier).
> >>>
> >>> It is obvious to me, and I am pretty to sure to everyone involved in
> >>> the development of 1.18 that we can not do an alpha while some of the
> >>> biggest change are not there yet. Now the question is should we delay
> >>> the alpha ? Or should we make the alpha a technical preview followed
> >>> by an alpha later on ? Should we just move on and delay the above
> >>> change for 1.19, in which case all the new API need to remain BETA.
> >>> Also if we do delay, how much longer is needed for a release ? Isn't
> >>> it going to drag on ?
> >>>
> >>> Oh and did I miss anything in the above list ?
> >>>
> >> Also:
> >>
> >> eo->efl renaming, not a biggie, but needs to be done.
> >> As for text, we hope to be done with it by next Tuesday.
> >>
> >> I'll let you know if anything else comes to mind.
> > Another thing that is kinda related to the first item on your list: we
> > need to make sure to remove all of the evas/edje/elm whatever references
> > in our eo files and class names. For example, Efl.Canvas.Text still
> > inherits from Evas.Object, which is bad.
>
> All of the above are exception for the current freeze. Plus the eolian
> work from Daniel which I was told will not effect our C API at all.
>
> While I find this unsettling and unfair to have a freeze for some parts
> and not for other I hope people can life with it this time. The problem
> is that the interface work is done far enough that we can't really back
> it out anymore. :/
>
> Please guys keep me updated on what is done from this list and what
> still missing. Moved the alpha from this week to next and will hopefully
> get a snapshot out this week to get at least some people test all the
> repo merges we did from a packager and user perspective.
>

I still need to add some more missing FDO icons in the next 2 weeks,
I hope this will not be considered as new features.



>
> regards
> Stefan Schmidt
>
>
> --
> What NetFlow Analyzer can do for you? Monitors network bandwidth and
> traffic
> patterns at an interface-level. Reveals which users, apps, and protocols
> are
> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> J-Flow, sFlow and other flows. Make informed decisions using capacity
> planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
> ___
> enlightenment-devel mailing list
> enlightenment-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
>
--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Re: [E-devel] Next release

[Stefan Schmidt]

Hello.

On 05/06/16 14:27, Tom Hacohen wrote:
> On 05/06/16 10:47, Tom Hacohen wrote:
>> On 04/06/16 00:24, Cedric BAIL wrote:
>>> Hello,
>>>
>>> I just would like to start a thread regarding what is still pending
>>> for next release and what we should do about it. First let's start
>>> with what is not ready :
>>> - Most of the elementary widgets have not been renamed correctly to be
>>> in efl.ui namespace.
>>> - Edje and Elm.Layout have not been refactorized and properly
>>> inherited from each other.
>>> - Text interface is not there (this impact also entry, label and edje).
>>> - Genlist is also not there.
>>> - All eo object still needs a proper cleanup and use of own().
>>> - Uri manager is not there.
>>> - Color/Color_Class is not there.
>>> - Efl photocam is not there.
>>> - Efl video is not there.
>>> - Efl.Ui.Window is not there.
>>> - Efl.Ui.Focus cleanup is not there.
>>>
>>> Sone of the above have patch in review process that may land before
>>> Monday morning, but I prefer to just give the current status as I may
>>> not have time this weekend as I am moving. Also most of the API that
>>> have landed so far have not been tested in any real application and we
>>> don't really if they do fit their purpose (making life easier).
>>>
>>> It is obvious to me, and I am pretty to sure to everyone involved in
>>> the development of 1.18 that we can not do an alpha while some of the
>>> biggest change are not there yet. Now the question is should we delay
>>> the alpha ? Or should we make the alpha a technical preview followed
>>> by an alpha later on ? Should we just move on and delay the above
>>> change for 1.19, in which case all the new API need to remain BETA.
>>> Also if we do delay, how much longer is needed for a release ? Isn't
>>> it going to drag on ?
>>>
>>> Oh and did I miss anything in the above list ?
>>>
>> Also:
>>
>> eo->efl renaming, not a biggie, but needs to be done.
>> As for text, we hope to be done with it by next Tuesday.
>>
>> I'll let you know if anything else comes to mind.
> Another thing that is kinda related to the first item on your list: we
> need to make sure to remove all of the evas/edje/elm whatever references
> in our eo files and class names. For example, Efl.Canvas.Text still
> inherits from Evas.Object, which is bad.

All of the above are exception for the current freeze. Plus the eolian 
work from Daniel which I was told will not effect our C API at all.

While I find this unsettling and unfair to have a freeze for some parts 
and not for other I hope people can life with it this time. The problem 
is that the interface work is done far enough that we can't really back 
it out anymore. :/

Please guys keep me updated on what is done from this list and what 
still missing. Moved the alpha from this week to next and will hopefully 
get a snapshot out this week to get at least some people test all the 
repo merges we did from a packager and user perspective.

regards
Stefan Schmidt

--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Re: [E-devel] Next release

[Stefan Schmidt]

Hello.

On 05/06/16 02:04, Simon Lees wrote:
>
> On 06/04/2016 08:34 PM, Jean Guyomarc'h wrote:
>> Hi,
>>
>> on the Mac OS X side, there is a couple of critical bugs to be fixed.
>> Hopefully they will be gone at the end of the week-end.
>> For the record:
>> - https://phab.enlightenment.org/T3789
>> - https://phab.enlightenment.org/T3648
>>
>> As discussed in the previous thread with Stefan, Ecore_Cocoa could also
>> be marked as stable.
>>
>> So... I don't think we should rush the release or even a preview/alpha.
>> I know we will want to release at some point, in a not so far future, but
>> how about a little more of "it will be released when it will be ready"?
>>
>  From the point of a distro maintainer, i'm quite happy with a tech
> preview / alpha going out with known issues because it gives a chance
> for extended testing and finding other issues.

Right now I plan to fix make dist and the example build problems you 
reported this week and get a snapshot tarball out. An alpha would be 
next week if we can get our stuff together.

The snapshot and alpha are really for testing how many problems we 
overlooked when merging elm and the loaders and players repos. They will 
not contain the full new interfaces API yet and there will still be 
changes with this API. Which I hope we get sorted out so we can do a 
beta release.

I know it is kind of unsettling that I do not put out hard deadlines 
right now but this release is so massive that it is way harder to 
estimate, track and get ready compared to the ones before.

regards
Stefan Schmidt

--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Re: [E-devel] Next release

[Tom Hacohen]

On 05/06/16 10:47, Tom Hacohen wrote:
> On 04/06/16 00:24, Cedric BAIL wrote:
>> Hello,
>>
>> I just would like to start a thread regarding what is still pending
>> for next release and what we should do about it. First let's start
>> with what is not ready :
>> - Most of the elementary widgets have not been renamed correctly to be
>> in efl.ui namespace.
>> - Edje and Elm.Layout have not been refactorized and properly
>> inherited from each other.
>> - Text interface is not there (this impact also entry, label and edje).
>> - Genlist is also not there.
>> - All eo object still needs a proper cleanup and use of own().
>> - Uri manager is not there.
>> - Color/Color_Class is not there.
>> - Efl photocam is not there.
>> - Efl video is not there.
>> - Efl.Ui.Window is not there.
>> - Efl.Ui.Focus cleanup is not there.
>>
>> Sone of the above have patch in review process that may land before
>> Monday morning, but I prefer to just give the current status as I may
>> not have time this weekend as I am moving. Also most of the API that
>> have landed so far have not been tested in any real application and we
>> don't really if they do fit their purpose (making life easier).
>>
>> It is obvious to me, and I am pretty to sure to everyone involved in
>> the development of 1.18 that we can not do an alpha while some of the
>> biggest change are not there yet. Now the question is should we delay
>> the alpha ? Or should we make the alpha a technical preview followed
>> by an alpha later on ? Should we just move on and delay the above
>> change for 1.19, in which case all the new API need to remain BETA.
>> Also if we do delay, how much longer is needed for a release ? Isn't
>> it going to drag on ?
>>
>> Oh and did I miss anything in the above list ?
>>
>
> Also:
>
> eo->efl renaming, not a biggie, but needs to be done.
> As for text, we hope to be done with it by next Tuesday.
>
> I'll let you know if anything else comes to mind.

Another thing that is kinda related to the first item on your list: we 
need to make sure to remove all of the evas/edje/elm whatever references 
in our eo files and class names. For example, Efl.Canvas.Text still 
inherits from Evas.Object, which is bad.

--
Tom.


--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Re: [E-devel] Next release

[Tom Hacohen]

On 04/06/16 00:24, Cedric BAIL wrote:
> Hello,
>
> I just would like to start a thread regarding what is still pending
> for next release and what we should do about it. First let's start
> with what is not ready :
> - Most of the elementary widgets have not been renamed correctly to be
> in efl.ui namespace.
> - Edje and Elm.Layout have not been refactorized and properly
> inherited from each other.
> - Text interface is not there (this impact also entry, label and edje).
> - Genlist is also not there.
> - All eo object still needs a proper cleanup and use of own().
> - Uri manager is not there.
> - Color/Color_Class is not there.
> - Efl photocam is not there.
> - Efl video is not there.
> - Efl.Ui.Window is not there.
> - Efl.Ui.Focus cleanup is not there.
>
> Sone of the above have patch in review process that may land before
> Monday morning, but I prefer to just give the current status as I may
> not have time this weekend as I am moving. Also most of the API that
> have landed so far have not been tested in any real application and we
> don't really if they do fit their purpose (making life easier).
>
> It is obvious to me, and I am pretty to sure to everyone involved in
> the development of 1.18 that we can not do an alpha while some of the
> biggest change are not there yet. Now the question is should we delay
> the alpha ? Or should we make the alpha a technical preview followed
> by an alpha later on ? Should we just move on and delay the above
> change for 1.19, in which case all the new API need to remain BETA.
> Also if we do delay, how much longer is needed for a release ? Isn't
> it going to drag on ?
>
> Oh and did I miss anything in the above list ?
>

Also:

eo->efl renaming, not a biggie, but needs to be done.
As for text, we hope to be done with it by next Tuesday.

I'll let you know if anything else comes to mind.

--
Tom.

--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Re: [E-devel] Next release

[Simon Lees]

On 06/04/2016 08:34 PM, Jean Guyomarc'h wrote:
> Hi,
> 
> on the Mac OS X side, there is a couple of critical bugs to be fixed.
> Hopefully they will be gone at the end of the week-end.
> For the record:
> - https://phab.enlightenment.org/T3789
> - https://phab.enlightenment.org/T3648
> 
> As discussed in the previous thread with Stefan, Ecore_Cocoa could also
> be marked as stable.
> 
> So... I don't think we should rush the release or even a preview/alpha.
> I know we will want to release at some point, in a not so far future, but
> how about a little more of "it will be released when it will be ready"?
> 

From the point of a distro maintainer, i'm quite happy with a tech
preview / alpha going out with known issues because it gives a chance
for extended testing and finding other issues. But by the time its at
Beta/RC stage everything critical should be fixed and there should just
be minor changes left. Traditionally in the efl world the first alpha's
seem to come around the feature freeze time in this release we were
going to do a tech preview to give packagers extra time to adjust to the
fact elementary and efl were merged. There hasn't been any point in
doing such a release yet as things like elementary examples arn't
building from the release tarball currently, also once the discussion
began on merging the generic loaders it also made more sense to hold
until that was done.

Cheers

-- 

Simon Lees (Simotek)http://simotek.net

Emergency Update Team   keybase.io/simotek
SUSE LinuxAdeliade Australia, UTC+9:30
GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B



signature.asc
Description: OpenPGP digital signature
--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Re: [E-devel] Next release

[Jean Guyomarc'h]

Hi,

on the Mac OS X side, there is a couple of critical bugs to be fixed.
Hopefully they will be gone at the end of the week-end.
For the record:
- https://phab.enlightenment.org/T3789
- https://phab.enlightenment.org/T3648

As discussed in the previous thread with Stefan, Ecore_Cocoa could also
be marked as stable.

So... I don't think we should rush the release or even a preview/alpha.
I know we will want to release at some point, in a not so far future, but
how about a little more of "it will be released when it will be ready"?

Best regards,
Jean

--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Re: [E-devel] Next release

[David Seikel]

With Mike's health problems as well, it's sounding like the entire
thing (EFL and Enlightenment) might need to just slow down for a bit.

On Fri, 3 Jun 2016 16:24:55 -0700 Cedric BAIL 
wrote:

> Hello,
> 
> I just would like to start a thread regarding what is still pending
> for next release and what we should do about it. First let's start
> with what is not ready :
> - Most of the elementary widgets have not been renamed correctly to be
> in efl.ui namespace.
> - Edje and Elm.Layout have not been refactorized and properly
> inherited from each other.
> - Text interface is not there (this impact also entry, label and
> edje).
> - Genlist is also not there.
> - All eo object still needs a proper cleanup and use of own().
> - Uri manager is not there.
> - Color/Color_Class is not there.
> - Efl photocam is not there.
> - Efl video is not there.
> - Efl.Ui.Window is not there.
> - Efl.Ui.Focus cleanup is not there.
> 
> Sone of the above have patch in review process that may land before
> Monday morning, but I prefer to just give the current status as I may
> not have time this weekend as I am moving. Also most of the API that
> have landed so far have not been tested in any real application and we
> don't really if they do fit their purpose (making life easier).

My SledjHamr project is one of the real applications that would be
using a lot of the Ecore_Con, Elm, Eo, Evas_3D, and threading stuff.
It's still not fully working right, but at least builds and doesn't
crash anymore.  Some of the current bugs might be related to the focus
and genlist stuff not being there.  Video is due to be added to this
project later (I want to hook up video to the terrain heightfield, so
people can create earthquakes).

My new Conky experiments will use Lua and Edje stuff, and might
eventually use whatever EFL has for hardware monitoring these days.
That will need the color and text stuff, so that's on hold for now.

> It is obvious to me, and I am pretty to sure to everyone involved in
> the development of 1.18 that we can not do an alpha while some of the
> biggest change are not there yet. Now the question is should we delay
> the alpha ? Or should we make the alpha a technical preview followed
> by an alpha later on ? Should we just move on and delay the above
> change for 1.19, in which case all the new API need to remain BETA.
> Also if we do delay, how much longer is needed for a release ? Isn't
> it going to drag on ?
> 
> Oh and did I miss anything in the above list ?

I tired to compile EFL yesterday, had issues with Lua and EIO.  The Lua
issue is likely a problem at my end, but the EIO issue looked like a
problem at your end.  I might poke at that more later today.

-- 
A big old stinking pile of genius that no one wants
coz there are too many silver coated monkeys in the world.


signature.asc
Description: PGP signature
--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Re: [E-devel] Next release

[Simon Lees]

On 06/04/2016 08:54 AM, Cedric BAIL wrote:
> Hello,
> 
> I just would like to start a thread regarding what is still pending
> for next release and what we should do about it. First let's start
> with what is not ready :
> - Most of the elementary widgets have not been renamed correctly to be
> in efl.ui namespace.
> - Edje and Elm.Layout have not been refactorized and properly
> inherited from each other.
> - Text interface is not there (this impact also entry, label and edje).
> - Genlist is also not there.
> - All eo object still needs a proper cleanup and use of own().
> - Uri manager is not there.
> - Color/Color_Class is not there.
> - Efl photocam is not there.
> - Efl video is not there.
> - Efl.Ui.Window is not there.
> - Efl.Ui.Focus cleanup is not there.
> 
> Sone of the above have patch in review process that may land before
> Monday morning, but I prefer to just give the current status as I may
> not have time this weekend as I am moving. Also most of the API that
> have landed so far have not been tested in any real application and we
> don't really if they do fit their purpose (making life easier).
> 
> It is obvious to me, and I am pretty to sure to everyone involved in
> the development of 1.18 that we can not do an alpha while some of the
> biggest change are not there yet. Now the question is should we delay
> the alpha ? Or should we make the alpha a technical preview followed
> by an alpha later on ? Should we just move on and delay the above
> change for 1.19, in which case all the new API need to remain BETA.
> Also if we do delay, how much longer is needed for a release ? Isn't
> it going to drag on ?
> 
> Oh and did I miss anything in the above list ?
> 
The technical Preview hasn't even been possible till now as building
elementary examples from a make dist tar fails for a number of reasons,
there is also no point in doing a alpha with known issues building it.
I'm yet to build with evas_generic_loaders / emotion generic players to
test that they build either, its probably worth someone building a dist
tar then actually compiling the contents before the alpha (I'll get to
that this weekend or next week).

Cheers

-- 

Simon Lees (Simotek)http://simotek.net

Emergency Update Team   keybase.io/simotek
SUSE LinuxAdeliade Australia, UTC+9:30
GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B



signature.asc
Description: OpenPGP digital signature
--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel