Uses of Beta Release
- Real time testing results from Customer
- No fear to release large/new features (Release new features with enable/disable through config properties)
- No fear to feel user’s acceptance
Release Mechanism – Web / Standalone
Release new features / fixes / patches to small amount customer base and slowly increase based on product stability.
Week 1 – 5% of Users
End of Week 3 – 10% of Users
End of Week 6 – 25% of Users
End of Week 12 – 50% of Users
End of Week 18 – 100% of Users
This % and Release schedules to be finalized based on project needs.
Practically seen following:
1. Company A deployed project A and at load balancer level they are controlling % of traffic to specific server. On new site they solicit feed back and offer gift cards / raffle tickets, ..etc
2. Company B is having 40 web instances. They will deploy instance by instance slowly with days gap
3. Company C is building standalone software. It release software to free community edition first. Based on feed back they release to commercial customers.
4. WordPress / Google and other release Beta to free customers first to avoid liability. Based on it is success they will release later to commercial customers.
5. Company D is having large customers in USA and small customers in other small countries like Italy. They first release software in Italy and after some time they release in USA.