Tuesday, November 24, 2009

EAP build 10626 - Almost RC

A new EAP build as the release approaches. We are focused on fixing the most critical emerging issues now, so this is almost a release candidate build.

Apart from a number of fixed issues, minor improvements slipped through: presentation of the snapshot dependency builds failures, ability to specify prefix for EC2 agent name, dedicated action to remote run all committed but not pushed Git changes in IDEA, etc.

This is the first build which uses new TeamCity 5.0 license keys. It has time limited (60 days) EAP key bundled, so you do not need to do anything, the bundled key will be used automatically. New license keys are introduced to handle upgrade policy that we are going to announce with the 5.0 release.

In brief, new TeamCity 5.0 license key (both server and agent) will work with any version released during a year since the date of purchase. Further upgrades will be available for a discounted price.

If you already have any TeamCity licenses, you can upgrade them with a discount. If you have bought TeamCity 4.5 license within the last several month, you get 5.0 for free.

Precise terms will be announced a bit later.

6 comments:

Alun Harford said...

"In brief, new TeamCity 5.0 license key (both server and agent) will work with any version released during a year since the date of purchase. Further upgrades will be available for a discounted price."

Can you clarify that? Are you moving to a subscription model, or still selling licenses?

Thomas said...

Can you specify how long do you mean by several months eligible for a upgrade? From when it will be a free upgrade and from when it will be a discount? Also, can you give more details regarding to the price & discount?

I reckon if jetbrains is moving to a subscription model, it should notice the user early instead when the release comes out. As in IT we all have resource control and need multiple approval for budget.

And can you let us know if we are not going to upgrade the licence, is TeamCity going to keep releasing bug fixes and support TeamCity v4? It is alright if TeamCity is charging for new functions but fixing current bugs / support should be a cost that we already paid in the current licence.

Yegor Yarko said...

Alun,

> Are you moving to a subscription model, or still selling licenses?

The terms change (or, more precisely they are defined: there were no announced upgrade policy beforehand) for upgrades only.

Everything other stays the same: we still sell perpetual licenses (the license bought for a TeamCity version will work with the version forever).

The "one year" policy only relates to the period of free upgrades: the license will work with any TeamCity version released within the year.

Yegor Yarko said...

Thomas,

> Can you specify how long do you mean by several months eligible for a upgrade?

As I mentioned, this will be announced later, I simply do not have all the details yet.

> is TeamCity going to keep releasing bug fixes and support TeamCity v4?

There can be 4.5.x maintenance releases in which we will address the most critical issues.

Alun Harford said...

I can understand that you want to get revenue from your new features but if you want to go down that road you still need to support bug fixes on your old versions for a longer period than one year.

If I go to my client and recommend that they use Teamcity as their CI server - and a critical bug crops up 10 months later which is fixed 1 year and 1 day after they have bought the license - that would be a problem. And frankly it would be my problem because I'd recommended your software to the client.

So at the moment I can't recommend your software. I suspect a substantial part of your revenue comes from this sales model.

Yegor Yarko said...

Alun,

We might release critical bugfix updates when necessary and they can work with licenses that already have free upgrade year finished.

Actually, I'd say that when you commit to some software and need to rely on the bugfix updates it is more an issue of trust in the software vendor then any agreement/conditions. I believe there is no legal "obligation" to fix bugs, just a matter of attitude to customers...

And I may assure you that we do care. Earning money is by far not the only our target.