Slow down…

Regarding new versions of NopCommerce.

Personally I would like to have less but bigger updates.

Version 1.8 is out; let’s test it so that everything works 100%. Discounts, gift cards and so on (
also see my post: https://www.nopcommerce.com/boards/t/6618/testing-nopcommerce-before-deploy.aspx).

Do not add any functions until we know that everything works. After that, discuss what new functions we need. Then implement them very carefully.

New payment modules are quite easy to implement. Let the community test them before they are officially released.

Major functions (like a CMS) should also be testes very carefully before release. One again, let the community test it (call it beta test or whatever).

In conclusion:
1, Test 1.8 so that it works 100%.
2, Discuss minor and major updates.
3, Small updates (payment modules and so on) and major updates are created simultaneously.
4, When they are all tested so they work 100%, release update.

Regards

Carl-Johan Larsson

Carl,

Thanks for suggestion. Absoletely agree that each release should be well tested. BTW usually we announce roadmaps (see this topic) and beta-releases (see this topic)

See also the following topic - https://www.nopcommerce.com/boards/t/5930/it-is-going-to-fast.aspx

Thank you for your quick reply.

I wasn’t aware that there was any possibility to test the beta releases.

Do you think that you could gather some people (the more the better) that could test the update before it is released?

It would be great if there were some structure on, for example if a Norwegian could make sure that there are no bugs when you run in “Norwegian” mode.

One could also assign specific tasks to specific users. I could for instance pretend to be a store that only sells downloadable products; someone else is a store that heavily relies on using discounts. The possibilities are endless.

I’m aware that you are extremely busy, so if you would like to, I could handle the list of testers and see to that they have specific roles.

Regards
Carl-Johan Larsson

There's no need to have a limited list of testers. I think that everybody could be a tester. All he needs to do is to subscribe to our newsletter. Before releasing a new version we'll make an email announcement that 'Beta' is ready and everybody is welcome to test it (similar to this topic).

You can also start testing of upcoming version right now. Go to downloads page, scroll the page down to 'TFS version for developers' section. It has all instructions to get the latest version (developer trunk)