We've prepared a draft of the roadmap for the next version of nopCommerce (2.70). It doesn't contain any major features because all development efforts will be focused on improving existing functionality/performance/usability, refactoring, fixing bugs, and making nopCommerce more pluggable.
You can find all existing work items for version 2.65 here and for version 2.70 here.
By the way, have a look at this forum topic (the survey results). I think we'll start working on multi-store and multi-vendor support very soon (in several months). It's not for sure, but 99%. "Better CMS support" task is also demanded. Other features were voted as "Nice to have - but not essential". So they'll be implemented later.
Your thoughts?
UPDATE 1: An intermediate version (2.65) of nopCommerce was released because of an issue in FluentValidation described here and here. In brief, the previous version FluentValidation library (and hence nopCommerce) does not work on servers with ASP.NET 4.5 installed. It should be done as soon as possible because many servers (on shared hosting) will be upgraded to ASP.NET 4.5 in the near time.
UPDATE 2: Now after version 2.65 has been released we have the new updated roadmap for version 2.70. Please find it here. Estimate release time - the end of December (it's better to have a new release each 3-4 months). A lot of new work items has been added to it. This roadmap contains the following highlight features:
- Better CMS support
- Further performance optimization
- Support ID-less urls
- ACL on Categories
- ACL on Products
- Create a new modern public store default theme
- Improve affiliate support
- Allow developers to REPLACE certain blocks of a page with their own widgets
- And a lot of minor enhancements
UPDATE 3: Version 2.70 will be released in the beginning of December. Almost everything that was on its roadmap is implemented. A couple of tasks are postponed. A "new modern public store default theme" will be published as a separate package after 2.70 (please find more info here). After it's fully tested, it'll be added into the next official package (version 2.80). BETA testers are welcome!