4 Kicks

Economics of Continuous Deployment(ayende.com)

submitted by dpetersondpeterson(4397) 3 months, 12 days ago

CI is great, you'd think then that continuous deployment would be just as awesome. Clients automatically get access to the latest build, and you as the developer don't even have to think about it. That's what Ayende and his team thought as well, until they discovered the hidden economic issues behind this delivery model.

2 comments |category: |Views: 221

tags: another

new Add a live kick counter to your blog >> liveImage

You can even customize the image by choosing your own colors, and then clicking the button below to update the preview and the html code:

  • "Kick It" text
  • "Kick It" background
  • kick count text
  • kick count background
  • border

Simply copy and paste this HTML into your blog post.


Users who kicked this story:
guffshemrguffshemr(178) - vijaystvijayst(1311) - bsenoffbsenoff(1583) - dpetersondpeterson(4397)
Comments:

posted by vijaystvijayst(1311) 3 months, 11 days ago 0

An annual license fee should solve the economic problem of continuous integration. This will allow developers to work on major features and bugs in the current features.

Reply

posted by dpetersondpeterson(4397) 3 months, 11 days ago 0

I agree, however I think another option would be to make use of release tags and provide access to tagged builds based on license. If you tag your releases and push fixes to those release branches, that will allow users to get updates without having access to the latest features in a newer version. This allows someone to pay once for their product, yet still receive timely updates without paying a subscription.

Reply

information Login or create an account to comment on this story
Submit a Story
View upcoming stories
How else can I help?
Add our feeds to your site

Most Active Users

What's this?