Give a guy some love! (or at least some attention)
Even if you think the patch at http://drupal.org/node/37283 sucks, I want to know!
Steve Dondley wrote:
Even if you think the patch at http://drupal.org/node/37283 sucks, I want to know!
please don't beg for attention to your issue on this mail list. if you are not getting anyone to review your patch, you might email some key contributors privately. or ask in IRC. we moved issue posting away from this list for a reason.
Moshe Weitzman wrote:
Steve Dondley wrote:
Even if you think the patch at http://drupal.org/node/37283 sucks, I want to know!
please don't beg for attention to your issue on this mail list. if you are not getting anyone to review your patch, you might email some key contributors privately. or ask in IRC. we moved issue posting away from this list for a reason.
While that change was well intended please don't pretend it did not have negative consequences. It seems like 4.7 will never get to a stable point to freeze and RC. When I picked up 4.7 a few weeks ago to evaluate for use (which seemed reasonable since I had read about a code freeze several weeks prior to that) it was pretty much non functional. Fundamental bugs in new forms API code (http://drupal.org/node/35570, http://drupal.org/node/35225, http://drupal.org/node/35594) have sat idle for 3 weeks and others where independently fixed after I delivered patches that did not know about the issues I'd filed (or at least they did not update my issues). That is not the behavior of a healthy system. When I was actively working on items for the 4.5 release it was never this bad. Craig
Craig Courtney wrote:
Moshe Weitzman wrote:
please don't beg for attention to your issue on this mail list. if you are not getting anyone to review your patch, you might email some key contributors privately. or ask in IRC. we moved issue posting away from this list for a reason.
While that change was well intended please don't pretend it did not have negative consequences. It seems like 4.7 will never get to a stable point to freeze and RC. When I picked up 4.7 a few weeks ago to evaluate for use (which seemed reasonable since I had read about a code freeze several weeks prior to that) it was pretty much non functional. Fundamental bugs in new forms API code (http://drupal.org/node/35570, http://drupal.org/node/35225, http://drupal.org/node/35594) have sat idle for 3 weeks and others where independently fixed after I delivered patches that did not know about the issues I'd filed (or at least they did not update my issues).
We can only suggest that people subscribe to the issue tracker either by mail or rss. We cannot fore them (at least for rss ;).
That is not the behavior of a healthy system. When I was actively working on items for the 4.5 release it was never this bad.
4.5 didn't have that big changes as late in the game. And yes, it was neccessary to add these changes even this late. Cheers, Gerhard
participants (4)
-
Craig Courtney -
Gerhard Killesreiter -
Moshe Weitzman -
Steve Dondley