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
Is the changes to the makefile correct?
maybe is a mistake?
2018-06-07 11:04 GMT+02:00 Alastair Poole :
> netstar pushed a commit to branch master.
>
> http://git.enlightenment.org/apps/evisum.git/commit/?id=
> 1f189a10b626efc8f2847f0177729d960438cba0
>
> commit 1f189a10b626efc8f2847f0177729d960
This seems like something which would help people more easily find issues
that they can contribute to. Perhaps a 5th workboard for something like
'main loop' could also be added?
On Fri, Jun 8, 2018 at 11:32 AM Marcel Hollerbach wrote:
> Hello,
>
> as Mike said, here my proposal for handling bug
Marcel this is what I have been wanting to see for some time. I want to
contribute but given not knowing the code base this made it a rather daunting
task for me. I hope this system is something that will stick and see new
contributors joining.
Sent from my iPhone
> On 08 Jun 2018, at 17:31, M
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
Hello,
as Mike said, here my proposal for handling bugs for the upcoming release:
i) Every bug will get a difficulty assigned either Easy, Difficult, or
Impossible, this is to ensure that new people, and people that don't
know the subsystem or context very well can also help bugfixing.
ii) I
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
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 already
in bug fixing mode.
After speaking a bit with bu
20 matches
Mail list logo
