3.30.00 Progress (3.20.03 got renamed)

[AndyHCPS]

Originally Posted by John Haugeland

Epic progress. Nearly every 3.30 fix now tested.

Superb news and look forward to it *when* it is released. Appreciate all the hard work you all do

[hbidad]

hmm, good job passing the features to further revisions - that is what I call efficiently working through your queue.

Not really a big deal. Just aggravated for clicking through one the forums/roadmap for updates, come here and listen to the self back patting to find the big disappointment in the roadmap.

[Ryan Lederman]

Originally Posted by hbidad

hmm, good job passing the features to further revisions - that is what I call efficiently working through your queue.

Not really a big deal. Just aggravated for clicking through one the forums/roadmap for updates, come here and listen to the self back patting to find the big disappointment in the roadmap.

We have only deferred features that would further cause delays to this already-bloated roadmap. This release addresses *150* issues.

You must understand that there are limitations on how many issues can be addressed in a single build - at some point it becomes difficult to juggle, and the more defects, the more likely that there will be collateral damage.

In addition to this, we have customers pulling us one way to release the build yesterday (no matter what day it is), and then customers like yourself who get upset when the particular feature they would like to see doesn't get included in the build. It is impossible for us to please everyone.

We are doing our best, and working as diligently as possible to get this build to Release Candidate status.

Your feature will be implemented when it gets implemented.

[hbidad]

Ryan,

I understand Kayako is working hard at this. It's frustrating nonetheless.

What is really disturbing is the "security issues" that get swept under the rug. It's for good reasons, but seriously a year later?

"Your feature will be implemented when it gets implemented"

That's life I suppose. Moving things things further down the map is expected. Again, moving them and then praise yourself that the queue is near finished is cheating

I understand you fix a bug to introduce a few more further in the script, but was is your philosophy of "priority"?

[John Haugeland]

Originally Posted by hbidad

What is really disturbing is the "security issues" that get swept under the rug. It's for good reasons, but seriously a year later?

Have a look at that bug's history. It was incorrectly closed by a staff member who no longer works for Kayako. The second I found that defect, I contacted the customer who filed it. The security hole was closed within two days. It's not that we ignored it for a year; it's that it was mishandled, and it took a year to discover it.

I agree, it's disturbing that that was open that long. Things, however, are different than they were a year ago. That will not happen again. In fact, I've been auditing the other potential security issues that that employee handled. (So far, this is the only error I've caught. Still, one needs to check.)

Is there a practical difference between mishandled and ignored for a year? Yes and no. That that defect has been there that long is certainly a problem, but now there's an audit being done. We're not ignoring security holes. We take them very, very seriously. The issue is just a past staff member who did the wrong thing.

Originally Posted by hbidad

Again, moving them and then praise yourself that the queue is near finished is cheating

Less than ten defects were re-filed out of more than 150. Most of the things that were re-filed are either waiting on customer contact or waiting on systems that are due to be replaced; everything that was moved by dev staff was moved for a concrete reason. Nothing was moved for the sake of an early release.

I realize it's frustrating, but please, remember that the devs are people too, and we kind of want to be proud when we release a hundred fifty bugfixes at once. Happy developers work faster; let us be happy. Even if we didn't focus on the thing that makes you interested, we have cleared a tremendous amount of work, and there are a lot of things in this workload that will affect everyone - particularly some sorely needed performance boosts and much-improved error reporting.

The bugs are going to get fixed at the same time that they would if we folded all the rest of the 3.30s into 3.30.00; doing it in pieces just means that nobody has to wait on the work that's already done. Don't put too much weight on the importance of the version number; in terms of calendar time, there's basically no delay here. Would you really prefer the stuff that's going to come out in two months to have 3.30.00's label on it, if it means you don't get the fixes in 3.30.00 until then?

There are a lot of people who need the stuff in 3.30.00, there are security fixes in 3.30.00, the new loop cutter's in 3.30.00, the cron fix is in 3.30.00, there's a ton of internationalization improvement in 3.30.00, et cetera. We need to get the work that's done out there and into people's hands.

Be happy with us. You're getting a whole bunch of new stuff out of this upgrade too. I'm sorry whichever bug you're watching must have gotten pushed back, but whatever it was, there's a good reason for it (a few of those good reasons aren't explained in the bug tracker because they reveal future plans, but there are good reasons for each, I assure you.)

[Dan]

Interesting to see a lot of progression within kayako
I know that I didn't waste my money to pay for support and upgrade.

Anyway... don't forget that Modernbill (or called it Plesk Billing) have new skin now
If you have time please try to integrate as well

[John Haugeland]

Originally Posted by Dan

Interesting to see a lot of progression within kayako
I know that I didn't waste my money to pay for support and upgrade.

We're making a new effort to be more transparent, so that people can see what's going on. The bug tracker in particular has been radically revamped to be more understandable.

Originally Posted by Dan

Anyway... don't forget that Modernbill (or called it Plesk Billing) have new skin now
If you have time please try to integrate as well

Thanks for pointing that out. This is now tracked as issue 701.
Kayako Bug Tracker - Viewing Issue #701 - Update Plesk Billing (was ModernBill) integration to accomodate new skin

[John Haugeland]

pre-emptive "yay"

[Ryan Lederman]

Release Candidate 1 is out: http://forums.kayako.com/f56/3-30-00...ate-1-a-18151/

[Ryan Lederman]

Released: http://forums.kayako.com/f3/3-30-00-...eleased-18304/

[Ryan Lederman]

3.30.01 is out, which fixes several defects in 3.30.00. Everyone is encouraged to upgrade.