(split) API discussion

[MACscr]

Well, that other version was released on the 17th. That means the next release will have the API, woo hoo! Now we only have like a year to wait. =P

[Jamie Edwards]

Hi there,

It is unlikely that the API will feature in the next release (which will be a minor). It may come in one of the next major releases.

[MACscr]

Originally Posted by Jamie Edwards

Hi there,

It is unlikely that the API will feature in the next release (which will be a minor). It may come in one of the next major releases.

LOL, typical kayako quality.

[craigbrass]

Jamie: I don't know if you have noticed this but it says the following inside the api file :-

// Disabled till v4.00.00

[Jamie Edwards]

Yes, I have noticed, thanks.

Originally Posted by craigbrass

Jamie: I don't know if you have noticed this but it says the following inside the api file :-

[Jamie Edwards]

Originally Posted by MACscr

LOL, typical kayako quality.

Absolutely; we're aiming to achieve tighter and more regular stable releases in-between major versions to better the quality of each release.

[craigbrass]

I am personally all for Kayako stopping wasting around with V3 and just working on V4 that will fix ALL the problems with one release. Wasting time with V3 is just going to delay V4.

[Jamie Edwards]

Originally Posted by craigbrass

I am personally all for Kayako stopping wasting around with V3 and just working on V4 that will fix ALL the problems with one release. Wasting time with V3 is just going to delay V4.

I am strongly of the opposite opinion. V4 is some time away, and there are a number of issues with Version 3 that need solving.

Not to mention, not everyone will be expected to (nor would everyone out of choice) upgrade to Version 4 as soon as it is out. We have a big customer base which means a lot of Version 3 users.

The only things that we will defer to the next major product line overhaul are major new features or changes to core functionality.

We will not drop support or maintenance of Version 3 in order to develop Version 4.

[Matthew]

Originally Posted by Jamie Edwards

I am strongly of the opposite opinion. V4 is some time away, and there are a number of issues with Version 3 that need solving.

Not to mention, not everyone will be expected to (nor would everyone out of choice) upgrade to Version 4 as soon as it is out. We have a big customer base which means a lot of Version 3 users.

Hear, hear! Good one on you, mate!

[MACscr]

Originally Posted by Jamie Edwards

Hi all,

A core API has been developed and the API spec will be released soon

Does he remember this response on 17-05-2007?

[Jamie Edwards]

Originally Posted by MACscr

Does he remember this response on 17-05-2007?

He does, but sometimes changes are unavoidable and are common, particularly when development teams are small and growing (or even shrinking - Mahesh, the developer who was working on the APIs has since left Kayako).

Please have patience. I would suggest reading through this thread; if you would rather we never let you know our estimates for delivery at the time, then we won't publish them. If you do want to know, you will have to take them as grey (not in black and white).

Thanks,

[craigbrass]

Out of interest, how is the hunt for new developers going?

[Jamie Edwards]

Originally Posted by craigbrass

Out of interest, how is the hunt for new developers going?

Progressing steadily, and John has settled in well.

[MACscr]

Originally Posted by Jamie Edwards

He does, but sometimes changes are unavoidable and are common, particularly when development teams are small and growing (or even shrinking - Mahesh, the developer who was working on the APIs has since left Kayako).

Please have patience. I would suggest reading through this thread; if you would rather we never let you know our estimates for delivery at the time, then we won't publish them. If you do want to know, you will have to take them as grey (not in black and white).

Thanks,

Thats only a legitimate excuse for Open Source projects, not commercial ones with paid developers. Any quality company will set deadlines and timeliness for their development team. Yes, they do have to be adjusted on occasion, but they still have to be made. If they arent, then things do not get completed in a timely manner and developers become lazy. We obviously are seeing this with Kayako on a daily basis. Again, nothing wrong with changing dates, but were talking about years here. This is way to common with Kayako. You promise the world to clients, then never deliver 50% of the time and other 50% takes months to years when you yourself or one of your "sales" people say that it would be ready next week. Maybe you should check out WHT sometime and see why you were rated as one of the worst companies to deal with.

My opinion is based as being an IT director, project manager, and developer.

[welch]

Originally Posted by MACscr

Thats only a legitimate excuse for Open Source projects, not commercial ones with paid developers. Any quality company will set deadlines and timeliness for their development team. Yes, they do have to be adjusted on occasion, but they still have to be made. If they arent, then things do not get completed in a timely manner and developers become lazy. We obviously are seeing this with Kayako on a daily basis. Again, nothing wrong with changing dates, but were talking about years here. This is way to common with Kayako. You promise the world to clients, then never deliver 50% of the time and other 50% takes months to years when you yourself or one of your "sales" people say that it would be ready next week. Maybe you should check out WHT sometime and see why you were rated as one of the worst companies to deal with.

My opinion is based as being an IT director, project manager, and developer.

Though it is sometimes difficult to keep good programmers on staff all the time and relaying bugs (Just went through that, but eventually got on the same page) are difficult, I do believe they are trying. I think though they should look at community involvement as a more serious channel for advancement.