Magento

I’ve been looking through the list of Resolved bugs in the last few days, and most of them have been set to resolved without any comments from Magento/Varien staff as to what was done to resolve the bug.  Only a small handful of the 1.1.3 Resolved bugs had any kind of Magento Team response. 

Was it fixed?  Ignored?  Duplicate of another bug?  Duplicate of one in their internal bug system?  Is 1.1.4 coming out in the next few days and you’re cleaning house before the next release?

In the blog/video from last week, I thought it was mentioned that there was going to be an attempt to improve communication when closing the tickets.  I know it’s only been a little over a week, but not knowing what’s going on with the software that your business relies on [or will rely on shortly because of some of these bugs] is frustrating ..

Magento Team:  Can we please get some more communication when closing the tickets?

@bmartus - In the next few days an issue resolution roadmap will be available through the community site. The roadmap will list the issues that are pending and expected release which they will be resolved. I’ve attached a sample of what we are working on internally. Please note that release dates will not be published (as per our policy) and the roadmap will be subject to change based on priorities.

Click thumbnail to see full-size image

I’ll second Brandon’s request.

My last bug (6536) and another similar report (6624) were simply marked as “resolved” today with no comment from a Magento team member.  At least a “fixed for 1.1.4” message would be nice, a short explanation of how the fix is implemented would be nicer.

AntonOlsen - 27 August 2008 02:11 PM

I’ll second Brandon’s request.

My last bug (6536) and another similar report (6624) were simply marked as “resolved” today with no comment from a Magento team member.  At least a “fixed for 1.1.4” message would be nice, a short explanation of how the fix is implemented would be nicer.

At least you know yours are being read.  My issue [ http://www.magentocommerce.com/bug-tracking/issue/?issue=2940 ] is still unread, and the situation is progressively getting worse!

@redpen: I know Varien is aware of this. I’ve seen clients’ databases that are over 1GB in size from just the log tables. The solution is to empty those tables out periodically until this is something you can do through Magento. I suspect 1.1.4 will have this feature in it. This issue not only stops you from making backups, but it drastically slows down the performance of your site.

ive submitted a few bug in the past, that have been fixed.

It would be nice to have an emailed ping to the bug poster when its fixed

Ive used bugzilla in other companies, and it was always nice to get updates and status emails on bug progress.

brendan

Crucial - 01 September 2008 11:42 AM

@redpen: I know Varien is aware of this. I’ve seen clients’ databases that are over 1GB in size from just the log tables. The solution is to empty those tables out periodically until this is something you can do through Magento. I suspect 1.1.4 will have this feature in it. This issue not only stops you from making backups, but it drastically slows down the performance of your site.

Hi Crucial, thanks for the reply.  I’ve sent you a PM.