On Tue, 13 Nov 2012 22:37:52 +0200 Tom Hacohen <[email protected]> wrote:
> On 13/11/12 21:30, Michael Blumenkrantz wrote: > > I appreciate your feedback. > > > > However, constantly nagging (and I mean this in the most literal sense, > > since a day has not gone by without someone hassling me over it) about > > known issues, such as the tooltip/menu comp bug, is not a great way to > > motivate or encourage any developer in the world. > > I'm not trying to encourage you to fix them. I'm just trying to make > sure we do not progress any further with those bugs still there as they > are obvious release blockers. I don't see the point of advancing into Given that I am the only person working on E17 most of the time and everyone else who could fix this is far busier with other things or on vacation, saying things like "I'm just trying to make sure we do not progress any further with those bugs still there as they are obvious release blockers" results in "I'm going to bug you about this repeatedly". > the beta stage with such release blockers still there. I only "nag" > about it after each step we take forward without fixing it. I.e Alpha1 > and Alpha2. You aren't the only one doing it, but you ARE the only one who continually fails to provide any useful information while doing it in this case. This is a growing trend within this community, and it is not productive for anyone--especially people trying to fix things. > > > > > Given that you yourself are a developer, I would appreciate it even more if > > you would try to do something more constructive with your time than writing > > mails like this, which effectively amounts to nothing more than harassing > > the only person who works regularly on E17; trying to fix some of these > > known bugs (many of which are simple one-line changes) on your own would be > > a great help, and it would take roughly the same amount of time as > > complaining on the mailing list. Imagine the changes we would see if every > > active developer picked one bug to try fixing for the release. > > You know my current state, that I'm currently completely away and > swamped with things I'm supposed to do before I move to another country > next week, so don't act so naive and suggest me to do things you know I It's not "act[ing] so naive" when I say that it actually would take you the same amount of time to fix commonly-complained-about bugs as it does to write these mails. I know that this is the case; I've fixed hundreds, possibly thousands of these over the past few months. > just can't do. I'm doing what I can to help, and in my point of view, > reminding people about big issues that should be blocking releases when > releases are made anyway are very big help. I am very appreciative of your contributions; I take issue here with your chosen method of constant "reminders", as said previously. > Also, although my limited availability and general lack of free time > I've been fixing bugs in e recently (haven't been hacking on my > favourite parts of the EFL, but focused on e instead), so I really don't > get what you are trying to say. This is the case and, as said previously, is appreciated, however, does it not bother you that the time that this discussion is occurring here is now, a month before the final release date? Why was it not the case that there was constant nagging and fixing bugs previously? The answer is obvious, but I think my point is made. > > Bottom line is: I'm just trying to make sure we don't release any beta > versions before these issues are fixed. > > -- > Tom. > > Again, "trying to make sure we don't release any beta versions before these issues are fixed." is a noble cause, but your method of attempting it is not productive. You've seen the release schedule, you know the dates, and you know the people who are involved. I would think, given that I am the so-called release manager and have proven my ability to manage bug lists, even with our failure of a trac, you would have more than zero confidence in my ability to know what bugs are outstanding and what their importance is; failing that, I should hope you have some level of faith in the community (which you are part of) to handle something as simple as reading email. That this is not the case is very troubling to me, both on a personal and professional level, considering the high and consistent level of dedication I have shown to fixing bugs on the road to release these past few months; it also does not speak well of your view of the community overall. If there's something in particular that causes you to feel this way, please explain it so that I can make necessary personal changes, or so that we can try to generate some better workflows within the community. Thanks again for your feedback ------------------------------------------------------------------------------ Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
