Thanks for suggestion. Here are my thoughts. Currently there're not so much features and tasks left that we're planning to implement. You can see all of them here, just filter status by 'Active' and Release by 'nopCommerce 1.90' and 'nopCommerce 2.00' (about 15 major features). ETA for nopCommerce 1.90 is December 2010. ETA for nopCommerce 2.00 is February 2011. After all them are implemented nopCommerce will have almost everything that a solid e-commerce software should have, and we'll not be releasing new versions so often. After that we'll start working on a marketplace for developers
In the feature tasks for nopCommerce 1.90, 2.00 and 2.01, I do not see anything relating to CMS implementation. Do you have any information on when that will happen?
TIn the feature tasks for nopCommerce 1.90, 2.00 and 2.01, I do not see anything relating to CMS implementation. Do you have any information on when that will happen?
First of all nopCommerce is an eCommerce solution. And we don't plan to create a fully featured CMS in the near time (but there're several minor work items related to CMS)
Personally, a major reason for switching to nopCommerce is that the product is constantly being improved. Yes, frequent versions can create upgrade problems, but you always have the option to not upgrade. I prefer to have the choice to upgrade or not.
Many of the newer features are important to my clients, and they save me hours of customization time.
I love seeing a detailed roadmap of features with ETAs on release dates. That really helps with planning. Much better than "hoping" a feature will get included one day.
I'm very impressed with both the product, and the process for continuing to improve it. Congrats to all involved.
in my opinion , it s quiet ridiculous to complain about fast and continuous development which nowadays are very rare to find specially in a OS project.
with that said, not everybody has to upgrade immediately after each release and as mentioned in the previous post, there is a roadmap that helps planning upgrades. upgrades should match business needs and evaluated against the custom coding and efforts put into it. upgrading just for the sake of "upgrading" has no sense.
I doubt in the software business there will ever be a final version.
Someone will always ask for added features and or changes. MS will allways be delivering new options / features in their software dictating changes to NopCommerce source.
I haven't installed the latest release as for 1 the extra features our company does not need and secondly while the technical changes are probably desirable in order to keep in synch with MS they are not critical to our business.
So we've stuck to an earlier version for now (upgraded a couple of times) and are very happy with it.
Sure we'll update to a later version sometime in the future but for now we do not see what we'd gain by updating every time a later version is released.
Although I'm no PHD in asp.net, I know my way around. From my perception, NC is really neatly coded and it's really comforting to see a release every 2 months or so... It means people are actively working on it, although it's a pain in "there" to upgrade my custom features to newer nopCommerce versions. But this is a job I happily do because it's really a joy to work with nopCommerce!
