More frequently updates

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
7 years ago
I think we should make intermediate refresh settings.
We've got this update history ... > > 3.7, > 3.8, > 3.9, > 4.0
But it is possible to do so 3.9, > 3.9.1, > 3.9.2, > ... > 4.0, > ...
Because there are important isprovlenija and finals to wait about six months to get fixes.
You have to do or autoupdate a function in the nopcommerce where the fixes will go for one week, if there are one.

p.s.
Now, I have 5 projects based on Nopcommerce 3.9, because we've imported about 5000 categories and 40000 items, and it turns out that there's a malfunction in product import, and some of the merchandise is not in those categories, and now I have to wait 6 months for the version 4.0.
Question: And if there's a problem, I'm going to wait six more months for the 4.1 version?

______________________
Я думаю нужно сделать промежуточные обновлеия.
у нас сейчас такая история обновления ...>>3.7>>3.8>>3.9>>4.0
но можно сделать так 3.9>>3.9.1>>3.9.2>>...>>4.0>>...
Потому что есть важные испровления и доработки который нужно ждать примерно 6 месяцев пока выйдет испровления.
Нужно сделать или AutoUpdate функцию в NopCommerce где понедельно выйдут испровления, если есть таковые.

P.S.
У меня сейчас 5 пректов на основе NopCommerce 3.9 стоят, потому что мы импортировали примерно 5000 категорий и 40000 товаров, и оказалось что в Product Import Модуле есть неисправность и часть товаров попало не в те категории, и сейчас мне нужно ждать 6 месяцев пока выйдет 4.0 версия.
Вопрос: а если будет найдено еще неисправности , мне ждать еще 6 месяцев пока выйдет 4.1 версия?
6 years ago
Hi Tigran,

Thanka a lot for suggestion! I cannot find a topic on our forums where we discussed it with developers and third-party vendors. But the main issue with too frequest release cycle (e.g. each 2 months) is that all vendors will have to spend a lot of time to update their plugins and themes to each new version. 6 months is very optimal perioid. And the only prodblem is bugs found sometimes (like in any other software). So in order to get more stable releases we just need better testing and introduction of BETA releases (for example, please see this topic). The good point is that nopCommerce is an open-source solution and any issue can be fixed manually (if required)
6 years ago
Hi Andrei

BETA releases is a good idea.
Because now i have problem, i cant import Categories and Manufacturers with images. I need wait after Release 4.0.



P.S.

i think adding ability to Update Nopcommerce and Plugins in Admin area(with 1 click) is also good idea.
6 years ago
a.m. wrote:
...But the main issue with too frequent release cycle (e.g. each 2 months) is that all vendors will have to spend a lot of time to update their plugins and themes to each new version...

It didn't used to be that way all the time.  Updating the packages (e.g. Autofac, etc.) is what typically causes the incompatibilities.  If those types of updates could be deferred until later in the development cycle, then it may be  possible to have more frequent releases.
6 years ago
Too frequent updates also makes it difficult for developers to migrate and keep up with the latest version
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.