On Fri, 8 Jun 2018 11:17:19 -0400 Mike Blumenkrantz
said:
thanks for doing this. i would have done this prior to my holiday but efl was
in a very broken state and it seems most people were more interested in blaming
me for trying to get it into a state to freeze than to bother with it. i gave
up
On Fri, 8 Jun 2018 13:35:56 -0400 Mike Blumenkrantz
said:
> I'm opposed to having a blanket policy that there can be no new features at
> all added during a freeze.
the policy has always been just this - but like everything there is some grey.
if a new feature is needed to fix a bug then it's a
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, bt
+1, btw, I didn't catch the freeze period. What is the next release date we
are expecting to ? it just depends on all fixes bugs listed up?
On Sat, Jun 9, 2018 at 3:40 AM, Mike Blumenkrantz <
michael.blumenkra...@gmail.com> wrote:
> Sure, I agree with what you are saying but this is still a bit s
Sure, I agree with what you are saying but this is still a bit subjective
and so I don't think there is a need to attempt to codify that in the form
of a policy. Even if a major feature is merged during a freeze which seems
unnecessary (e.g., adding some giant new widget) then it's quite easy for
t
On Fri, Jun 8, 2018 at 2:35 PM, Mike Blumenkrantz
wrote:
> I'm opposed to having a blanket policy that there can be no new features at
> all added during a freeze.
>
> As an example, https://phab.enlightenment.org/D6247 is a feature which is
> required in order to improve test reliability--somethi
I would also like to point out here to anybody reading -- We have a parent
ticket going where we have subtasks for all phab tickets which relates to
breaks in the legacy code base, as these MUST be fixed for release. Here
is a link to the ticket: https://phab.enlightenment.org/T6926
If any of you
On 06/08/2018 01:51 PM, Mike Blumenkrantz wrote:
I think it's valuable to bring up possible points of confusion like this
when they exist, so thanks for bringing it up. There's no harm in asking
questions or requesting more details!
If everyone is in agreement with this proposal, I think it migh
I think it's valuable to bring up possible points of confusion like this
when they exist, so thanks for bringing it up. There's no harm in asking
questions or requesting more details!
If everyone is in agreement with this proposal, I think it might be a good
idea to document it somewhere (
https:/
On 06/08/2018 12:57 PM, Derek Foreman wrote:
On 2018-06-08 11:44 AM, Christopher Michael wrote:
On 06/08/2018 11:17 AM, Mike Blumenkrantz wrote:
Hello,
Stefan is off for this entire month, so let's try organizing the
release a
bit while he's gone!
We had previously agreed to start the freeze
I approve of this plan. Thank you for your initiative to start the process.
On Fri, Jun 8, 2018 at 12:36 PM Mike Blumenkrantz <
michael.blumenkra...@gmail.com> wrote:
> I'm opposed to having a blanket policy that there can be no new features at
> all added during a freeze.
>
> As an example, http
I'm opposed to having a blanket policy that there can be no new features at
all added during a freeze.
As an example, https://phab.enlightenment.org/D6247 is a feature which is
required in order to improve test reliability--something which should be at
the top of the list when working on a release
On Fri, Jun 8, 2018 at 1:44 PM, Christopher Michael
wrote:
> On 06/08/2018 11:17 AM, Mike Blumenkrantz wrote:
>>
>> Hello,
>>
>> Stefan is off for this entire month, so let's try organizing the release a
>> bit while he's gone!
[snip]
>> * During the freeze period, all newly-submitted features (
On 2018-06-08 11:44 AM, Christopher Michael wrote:
> On 06/08/2018 11:17 AM, Mike Blumenkrantz wrote:
>> Hello,
>>
>> Stefan is off for this entire month, so let's try organizing the
>> release a
>> bit while he's gone!
>>
>> We had previously agreed to start the freeze "after Cedric's branches
>>
This all sounds very positive and reasonable.
On Fri, Jun 8, 2018 at 5:44 PM, Christopher Michael
wrote:
> On 06/08/2018 11:17 AM, Mike Blumenkrantz wrote:
>>
>> Hello,
>>
>> Stefan is off for this entire month, so let's try organizing the release a
>> bit while he's gone!
>>
>> We had previously
On 06/08/2018 11:17 AM, Mike Blumenkrantz wrote:
Hello,
Stefan is off for this entire month, so let's try organizing the release a
bit while he's gone!
We had previously agreed to start the freeze "after Cedric's branches
merged". That branch was merged some time ago, and it seems we are alread
On 06/08/2018 05:22 PM, Daniel Kolesa wrote:
On Fri, Jun 8, 2018, at 17:17, Mike Blumenkrantz wrote:
Hello,
Stefan is off for this entire month, so let's try organizing the release a
bit while he's gone!
We had previously agreed to start the freeze "after Cedric's branches
merged". That bran
On 2018-06-08 10:22 AM, Daniel Kolesa wrote:
> On Fri, Jun 8, 2018, at 17:17, Mike Blumenkrantz wrote:
>> Hello,
>>
>> Stefan is off for this entire month, so let's try organizing the release a
>> bit while he's gone!
>>
>> We had previously agreed to start the freeze "after Cedric's branches
>> me
On Fri, Jun 8, 2018, at 17:17, Mike Blumenkrantz wrote:
> Hello,
>
> Stefan is off for this entire month, so let's try organizing the release a
> bit while he's gone!
>
> We had previously agreed to start the freeze "after Cedric's branches
> merged". That branch was merged some time ago, and it
Raster already did it :)
Daniel Juyung Seo (SeoZ)
On Wed, Jul 11, 2012 at 11:17 PM, Vincent Torri wrote:
> On Wed, Jul 11, 2012 at 4:08 PM, Gustavo Lima Chaves
> wrote:
>> * Carsten Haitzler [2012-07-09 18:34:31 +0900]:
>>
>>> Well i thought we'd have a weekend of peace and quiet before i sent
On 11/07/12 17:08, Gustavo Lima Chaves wrote:
> Cool. But I believe we gotta do s/@since 1.3/@since 1.7/ everywhere, don't we?
Doesn't matter... It has the same meaning since we never had or will
have 1.3-1.6, think about it. :)
--
Tom.
On Wed, Jul 11, 2012 at 4:08 PM, Gustavo Lima Chaves
wrote:
> * Carsten Haitzler [2012-07-09 18:34:31 +0900]:
>
>> Well i thought we'd have a weekend of peace and quiet before i sent this.
>>
>> EFL is now in freeze. that means no new features (unless that feature is
>> absolutely needed to solve
* Carsten Haitzler [2012-07-09 18:34:31 +0900]:
> Well i thought we'd have a weekend of peace and quiet before i sent this.
>
> EFL is now in freeze. that means no new features (unless that feature is
> absolutely needed to solve a bug) until release (planned for end of this
> month).
>
> I am i
On Tue, Jul 10, 2012 at 5:03 AM, Gustavo Sverzut Barbieri
wrote:
> On Monday, July 9, 2012, Carsten Haitzler wrote:
>
>> On Mon, 9 Jul 2012 11:24:03 +0100 Michael Blumenkrantz
>> > said:
>>
>> > I don't know, but the idea of having to go to
>> > efl/src/lib/ecore/src/lib/ecore_con/file.c makes me
On Tue, Jul 10, 2012 at 12:18 PM, Carsten Haitzler wrote:
> On Tue, 10 Jul 2012 00:03:16 -0300 Gustavo Sverzut Barbieri
> said:
>
>> On Monday, July 9, 2012, Carsten Haitzler wrote:
>>
>> > On Mon, 9 Jul 2012 11:24:03 +0100 Michael Blumenkrantz
>> > > said:
>> >
>> > > I don't know, but the idea
On Tue, Jul 10, 2012 at 12:29 PM, Carsten Haitzler wrote:
> On Tue, 10 Jul 2012 12:22:03 +0900 Cedric BAIL said:
>> On Tue, Jul 10, 2012 at 12:03 PM, Gustavo Sverzut Barbieri
>> wrote:
>> > On Monday, July 9, 2012, Carsten Haitzler wrote:
>> >> On Mon, 9 Jul 2012 11:24:03 +0100 Michael Blumenkra
On Tue, 10 Jul 2012 12:22:03 +0900 Cedric BAIL said:
> On Tue, Jul 10, 2012 at 12:03 PM, Gustavo Sverzut Barbieri
> wrote:
> > On Monday, July 9, 2012, Carsten Haitzler wrote:
> >> On Mon, 9 Jul 2012 11:24:03 +0100 Michael Blumenkrantz
> >> > said:
> >> > I don't know, but the idea of having to
On Tue, 10 Jul 2012 00:03:16 -0300 Gustavo Sverzut Barbieri
said:
> On Monday, July 9, 2012, Carsten Haitzler wrote:
>
> > On Mon, 9 Jul 2012 11:24:03 +0100 Michael Blumenkrantz
> > > said:
> >
> > > I don't know, but the idea of having to go to
> > > efl/src/lib/ecore/src/lib/ecore_con/file.c m
On Tue, Jul 10, 2012 at 12:03 PM, Gustavo Sverzut Barbieri
wrote:
> On Monday, July 9, 2012, Carsten Haitzler wrote:
>> On Mon, 9 Jul 2012 11:24:03 +0100 Michael Blumenkrantz
>> > said:
>> > I don't know, but the idea of having to go to
>> > efl/src/lib/ecore/src/lib/ecore_con/file.c makes me not
On Monday, July 9, 2012, Carsten Haitzler wrote:
> On Mon, 9 Jul 2012 11:24:03 +0100 Michael Blumenkrantz
> > said:
>
> > I don't know, but the idea of having to go to
> > efl/src/lib/ecore/src/lib/ecore_con/file.c makes me not want a single
> tree
> > at all
>
> god no. it'd be
>
> efl/src/lib/ec
On Mon, 9 Jul 2012 12:05:15 -0300 Lucas De Marchi
said:
> On Mon, Jul 9, 2012 at 6:34 AM, Carsten Haitzler wrote:
> > Well i thought we'd have a weekend of peace and quiet before i sent this.
> >
> > EFL is now in freeze. that means no new features (unless that feature is
> > absolutely needed t
On Mon, Jul 9, 2012 at 6:34 AM, Carsten Haitzler wrote:
> Well i thought we'd have a weekend of peace and quiet before i sent this.
>
> EFL is now in freeze. that means no new features (unless that feature is
> absolutely needed to solve a bug) until release (planned for end of this
> month).
We
On 09/07/12 16:14, Carsten Haitzler (The Rasterman) wrote:
> On Mon, 09 Jul 2012 13:57:40 +0300 Tom Hacohen said:
>
>> On 09/07/12 13:23, Carsten Haitzler (The Rasterman) wrote:
>>> nb - evas needs to flatten itself a bit anyway. at least all of
>>> evas/src/lib/ can flatten into a single dir.
>>
On 09/07/12 16:15, Carsten Haitzler (The Rasterman) wrote:
> On Mon, 09 Jul 2012 13:59:27 +0300 Tom Hacohen said:
>
>> On 09/07/12 13:03, Carsten Haitzler (The Rasterman) wrote:
>>> single configure for all. still producing multiple libs and pc files,
>>> headers etc.
>>>
>>
>> Ah, just a single s
On Mon, 9 Jul 2012 11:24:03 +0100 Michael Blumenkrantz
said:
> I don't know, but the idea of having to go to
> efl/src/lib/ecore/src/lib/ecore_con/file.c makes me not want a single tree
> at all
god no. it'd be
efl/src/lib/ecore_con/file.c
ecore would flatten out to its component ecore_*'s -
On Mon, 09 Jul 2012 13:57:40 +0300 Tom Hacohen said:
> On 09/07/12 13:23, Carsten Haitzler (The Rasterman) wrote:
> > nb - evas needs to flatten itself a bit anyway. at least all of
> > evas/src/lib/ can flatten into a single dir.
>
> Please don't, I love the split between canvas and engine. :)
On Mon, 09 Jul 2012 13:59:27 +0300 Tom Hacohen said:
> On 09/07/12 13:03, Carsten Haitzler (The Rasterman) wrote:
> > single configure for all. still producing multiple libs and pc files,
> > headers etc.
> >
>
> Ah, just a single source tree, got it. :) I thought you were talking
> about mergi
On 09/07/12 13:03, Carsten Haitzler (The Rasterman) wrote:
> single configure for all. still producing multiple libs and pc files, headers
> etc.
>
Ah, just a single source tree, got it. :) I thought you were talking
about merging the libs entirely.
Though, even here we can split core to 2 (base
On 09/07/12 13:23, Carsten Haitzler (The Rasterman) wrote:
> nb - evas needs to flatten itself a bit anyway. at least all of evas/src/lib/
> can flatten into a single dir.
Please don't, I love the split between canvas and engine. :)
--
Tom.
---
2012/7/9 Michael Blumenkrantz :
> I don't know, but the idea of having to go to
> efl/src/lib/ecore/src/lib/ecore_con/file.c makes me not want a single tree
> at all
Local symlinks for devs maybe?
>
> On Mon, Jul 9, 2012 at 11:18 AM, Vincent Torri wrote:
>
>> On Mon, Jul 9, 2012 at 12:08 PM, Michae
On Mon, Jul 9, 2012 at 12:24 PM, Michael Blumenkrantz
wrote:
> I don't know, but the idea of having to go to
> efl/src/lib/ecore/src/lib/ecore_con/file.c makes me not want a single tree
> at all
in the case of ecore, i would say: efl/src/lib/ecore/ecore_con,
etc... The 2nd src/lib is not needed,
I don't know, but the idea of having to go to
efl/src/lib/ecore/src/lib/ecore_con/file.c makes me not want a single tree
at all
On Mon, Jul 9, 2012 at 11:18 AM, Vincent Torri wrote:
> On Mon, Jul 9, 2012 at 12:08 PM, Michael Blumenkrantz
> wrote:
> > I don't like the dir structure. having to go
On Mon, 9 Jul 2012 12:18:07 +0200 Vincent Torri said:
> On Mon, Jul 9, 2012 at 12:08 PM, Michael Blumenkrantz
> wrote:
> > I don't like the dir structure. having to go down 10 directories just to
> > get to a .c file is not my idea of fun
>
> what would you propose ?
we could flatten it to:
e
On Mon, Jul 9, 2012 at 12:08 PM, Michael Blumenkrantz
wrote:
> I don't like the dir structure. having to go down 10 directories just to
> get to a .c file is not my idea of fun
what would you propose ?
Vincent
> On Mon, Jul 9, 2012 at 11:03 AM, Carsten Haitzler wrote:
>
>> On Mon, 09 Jul 2012 1
On Mon, 9 Jul 2012 11:08:46 +0100 Michael Blumenkrantz
said:
> I don't like the dir structure. having to go down 10 directories just to
> get to a .c file is not my idea of fun
it's 1 more dir compared to now.
> On Mon, Jul 9, 2012 at 11:03 AM, Carsten Haitzler wrote:
>
> > On Mon, 09 Jul 2012
I don't like the dir structure. having to go down 10 directories just to
get to a .c file is not my idea of fun
On Mon, Jul 9, 2012 at 11:03 AM, Carsten Haitzler wrote:
> On Mon, 09 Jul 2012 12:41:24 +0300 Tom Hacohen
> said:
>
> > On 09/07/12 12:34, Carsten Haitzler (The Rasterman) wrote:
> > >
On Mon, 09 Jul 2012 12:41:24 +0300 Tom Hacohen said:
> On 09/07/12 12:34, Carsten Haitzler (The Rasterman) wrote:
> > 3. after 1.7 release efl will start moving over to a single efl tree 1
> > library at a time, so after 1.7 releases of efl won't come in separate
> > library source trees, but as
On 09/07/12 12:34, Carsten Haitzler (The Rasterman) wrote:
> 3. after 1.7 release efl will start moving over to a single efl tree 1 library
> at a time, so after 1.7 releases of efl won't come in separate library source
> trees, but as a single tree build. this means people with svn build scripts,
48 matches
Mail list logo
