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
This process is now complete. Most tickets have been migrated to a
subproject of the 'efl' project in order to improve the workflow of
managing tickets.
Big thanks to everyone who pitched in to help move 700+ tickets in only a
couple hours!
On Mon, Jun 11, 2018 at 9:48 AM Mike Blumenkrantz <
Hi,
In accordance with various discussions on IRC and some tangential
discussion in the [release handling] thread, subprojects for efl have been
created: https://phab.enlightenment.org/project/subprojects/2/
We're currently working to tag all existing tickets (moved to
Let's split this into a separate thread from now on...
On Mon, Jun 11, 2018 at 9:39 AM Marcel Hollerbach wrote:
> Okay, after another discussion on ml, we start with those groups:
>
> - data types: Everything related to defined data types and the functions
> therefore, (includes Eos base
Okay, after another discussion on ml, we start with those groups:
- data types: Everything related to defined data types and the functions
therefore, (includes Eos base object)
- main loop: loop, idlers, jobs,
- rendering: engine related things
- layout: edje objects, boxes, tables,
As said in discussion on IRC, grouping by library does nothing to reduce
the bucket size here, so this is a false premise. Grouping by overall
functional component, as proposed by Hermet, will provide better workflows,
and we can create sub-projects for these components (effectively sub
Will do - thanks!
On Mon, Jun 11, 2018 at 11:59 AM, Mike Blumenkrantz
wrote:
> Ask Xavi on IRC
>
> On Mon, Jun 11, 2018 at 6:56 AM Al Poole wrote:
>
>> Absolutely.
>>
>> Am not really sure where to start there. I've all the instructions etc
>> ready, but it's definitely better if we host it.
>>
Ask Xavi on IRC
On Mon, Jun 11, 2018 at 6:56 AM Al Poole wrote:
> Absolutely.
>
> Am not really sure where to start there. I've all the instructions etc
> ready, but it's definitely better if we host it.
>
> Can you advise?
>
> On Mon, Jun 11, 2018 at 11:18 AM, Mike Blumenkrantz
> wrote:
> >
Absolutely.
Am not really sure where to start there. I've all the instructions etc
ready, but it's definitely better if we host it.
Can you advise?
On Mon, Jun 11, 2018 at 11:18 AM, Mike Blumenkrantz
wrote:
> Neat, do you have any plans to update the documentation for BSD on the site?
>
> On
Neat, do you have any plans to update the documentation for BSD on the site?
On Sat, Jun 9, 2018 at 3:27 PM Al Poole wrote:
> Hi all,
>
> Always talked about doing an OpenBSD installer with the EFL/E stack.
>
> So I did one, and it works!
>
> If you're interested:
>
>
Mike came up with the idea of sub projects, which sounds very good to me.
On 06/11/2018 10:17 AM, Hermet Park wrote:
Imho, base infrastructure (eo/eina/efl) / rendering (evas, ector) / layout
(edje, eet) / core system (ecore family) / window system / widgets (elm) /
sys-helpers (efreet,
I'm not sure we have a schedule (or can abide by it if one exists)?
I think perhaps we should try for an alpha release within the next 1-2
weeks to get some broader testing, but a separate mail thread can be
created to discuss this...
On Mon, Jun 11, 2018 at 12:11 AM Hermet Park wrote:
> +1,
Imho, base infrastructure (eo/eina/efl) / rendering (evas, ector) / layout
(edje, eet) / core system (ecore family) / window system / widgets (elm) /
sys-helpers (efreet, eldbus, eeze... ) is enough ...
But, your proposal is not arguable neither. I agree on it.
The problem is, sometimes issues
Okay, we need to step back with this a bit.
The problem is, workboards are quite unmanagable, and clearly not made
for the amount of tickets we are having.
So here a new proposal:
I create the following projects:
efl-ecore (additionally: elput & ecore_*)
efl-eina (additionally: evil emile)
14 matches
Mail list logo
