I'm not worried about time based so much as a general todo, for example:
(this is just an example and not an actual opinion on .23)
1. Clean up bugs in new gadgets
2. Make gadget bar/gadget sites more intuitive
3. Remove old gadcon/shelves
4. Make sure supporting documentation is in place for new
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
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
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
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 doing anything related to this project for the foreseeable future
