Beta policy, or the lack thereof

A place to discuss the testing process in beta cycles or against SVN for the CMS Made Simple CORE package.
Locked
User avatar
Franck
Dev Team Member
Dev Team Member
Posts: 248
Joined: Tue Jun 12, 2007 1:29 pm
Location: France

Beta policy, or the lack thereof

Post by Franck »

Hello,

I was wondering why there is no beta version everytime a new version (with new features, like the 2.1) to test by users?

For the version 2.0, I had the chance to test it quite early and find several bugs & propose UX suggestions. So could it be possible to release beta versions in a regular cycle?

Thank you.
pierrepercee
Forum Members
Forum Members
Posts: 51
Joined: Thu Jan 10, 2013 8:02 am

Re: Beta policy, or the lack thereof

Post by pierrepercee »

This would also facilitate the work of developers. Test phases is very time-consuming but does not require very specific skills. If some users may have the chance to test the latest versions, this will probably also prevent small forgotten details that lead to publish a bug fix release very quickly.
User avatar
DIGI3
Dev Team Member
Dev Team Member
Posts: 1035
Joined: Wed Feb 25, 2009 4:25 am
Location: Victoria, BC

Re: Beta policy, or the lack thereof

Post by DIGI3 »

We have tried public betas in the past with mixed results, but I think it may be time we revisited them again.

The Dev Team will be discussing ideas at the next meeting. It may be the creation of a Testing Team, or some other method of release that's less than fully public.

Thanks for the input!
Not getting the answer you need? CMSMS support options
User avatar
Franck
Dev Team Member
Dev Team Member
Posts: 248
Joined: Tue Jun 12, 2007 1:29 pm
Location: France

Re: Beta policy, or the lack thereof

Post by Franck »

Thanks for your answer. A testing team could be a good idea, indeed. Wait and see then. :)
jce76350
Beta Tester
Beta Tester
Posts: 1950
Joined: Mon May 29, 2006 1:20 pm
Location: Rouen

Re: Beta policy, or the lack thereof

Post by jce76350 »

It may be the creation of a Testing Team
There is already QA group in the dev team ;)
Best Way is a daily snapshots for all.
Jean-Claude Etiemble
tristan
Dev Team Member
Dev Team Member
Posts: 318
Joined: Tue May 02, 2006 10:58 am
Location: The Netherlands

Re: Beta policy, or the lack thereof

Post by tristan »

I would vote in favour of beta releases/daily snapshots as well. The bug with locking in the recent 2.1 release is a perfect example. This could've been caught very easily with a beta release.

This could also work perfectly for module releases by the way. The small bug in the Self Registration module being a good example. Kindly fixed by Robert back in October on his private svn but only released to the public in December but introducing a bigger problem along the way.

Maybe the QA group could use some extra help?
Locked

Return to “[locked] Quality Assurance”