Hi
On 11/01/2019 05:15, Stephen Houston wrote:
> Let me follow that up by saying - That is my opinion on what Enlightenment
> needs in a release manager - and of course a release manager can be
> different things and done different ways. Further I didn't mean it in any
> way to be an indictment o
Let me follow that up by saying - That is my opinion on what Enlightenment
needs in a release manager - and of course a release manager can be
different things and done different ways. Further I didn't mean it in any
way to be an indictment of you Simon, you do a good job with the release
procedur
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 sho
Part of being release manager is that you determine what the schedule
should be, what needs to be done, what features to focus on, roadmap it,
etc... Not a sit around until the devs determine in agreement (unlikely)
that it's time for a release and then just handle the tarballs, upload, and
news.
Hi all,
On 10/01/2019 05:45, Mike Blumenkrantz wrote:
> Hi all,
>
> As everyone has likely noticed by now, I haven't been doing much work
> lately related to Enlightenment or its releases. There are a number of
> factors at play related to this, but the result is that it seems unlikely
> I'll be
On 10/01/2019 01:51, Stefan Schmidt wrote:
> Hello.
>
> Its almost 5 months since we released 1.21 and I stepped down.
>
> When talking with people I got help offers on the release handling but
> no-one stepped up to fully take a lead on this. I start to get the
> feeling that this might need