Hello,
Mhmm in week 1&2 no real work can be done, as the merging could be
canceled due to 2, feels like progress is on hold there a bit. I would
prefer to just "do" development there, and cleanup unfinished TODOs in 5.
Otherwise this looks good to me.
On 07/12/2018 09:02 PM, Mike
Hello,
As Mike & Stefan pointed out in the ML thread "Community Scheduling",
doing EFL releases is quite a pain from time to time, we have a constant
"last minute" discussion about what is going to be merged, and what is
not. I feel like this is stretching nerves of everyone.
However, the
I think this is a good approach for managing releases going forward. If we
have a clear idea of what large features will be added to each release
around the onset of the development window then we can more easily work
towards those goals over a given time period. I propose the following
Hello,
I've done more gross hacks to the git-phab script since no real python
developers have shown up:
https://phab.enlightenment.org/P227
This fixes adding project tags (-p option) as well as adding
reviewers/subscribers when updating patches.
Still hoping someone better at python than me
On Thu, 12 Jul 2018 20:14:47 +0200 Marcel Hollerbach said:
> Hello,
>
> As Mike & Stefan pointed out in the ML thread "Community Scheduling",
> doing EFL releases is quite a pain from time to time, we have a constant
> "last minute" discussion about what is going to be merged, and what is
>
Hello.
On 10.07.2018 07:42, Mike Blumenkrantz wrote:
> Hello,
>
> It seems that we have some issues lately regarding scheduling, specifically
> personal schedules. We (as a project) have expectations of developer
> availability, and when these expectations are changed or not met then
> things
Now that we're interacting more as a community, I think there is the
general expectation that if you're a core developer then you should try to
notify the project if you'll be gone for an extended period of time.
I agree that there is a "deal with it" aspect to a community project, but I
think
