Firstly, congratulations on the release. OpenCart 2.0 did look amazing when we first saw it, and I can see that a few issues we had initially have apparently been fixed..
If I may in regards to the releases:
- My feeling is that I agree it may be worth introducing a short RC cycle to encourage testing, which would have eliminated bugs like the "text_edit string" bug. It doesn't hurt, even if its only 3 days long, and encourages semi-developer types to test it. This is commonplace in most software projects. Without one, Opencart also runs a slightly greater risk of releasing a version which corrupts a users database. RC releases are particularly effective on more targeted projects like this I feel, because bugs are easily replicated, and the code is so easy, they can often be fixed by newbies. Not a dealbreaker for us, but nice to have
- It may be worth splitting the downloads page into two rows.. The top showing stable releases, and the bottom unstable, showing a graph representing #open bugs, and closed bugs, and a link to the latest Nightly. This would demonstrate that open issues are getting actively addressed. People who aren't in the know may see no news for a few months, and think that nothing is happening. This would help address that
Well, from the view of a developer - maybe.
As a non-developer, you would be using whatever Fantastico or whatever provides anyway honestly. Not really sure how many non-developers would feel ok setting up MySQL. So, in theory yes, in practice, I disagree..
Hiring paid (!!) developers from India - hmmm.
And now only a few hours after publishing the latest release several commits again?
Be more respectful. And, bugs will always be found in software.. Projects which wait until there are 0 bugs on all installations will never have a release, because its a moving target. You may eventually fix 100% bugs if you never upgrade your server, but, a minor upgrade will break things eventually. Even bug fixes such as Shellshock took a few attempts to get right.
That being said, this project is free, and open source. So, given the pricing, We are happy with it.
And if you check the commits on the project, the reality is, the majority of the code for the project is committed by Daniel and James.. So, in all essence, it isn't really a true community project anyway. The reality is, if the community disappeared, the project would be usable. If they disappeared, the commits would drop to almost 0.
But, I also don't think the forum is the right place to be shouting at others.. It might be best to do it in a PM (because, to the rest of the community such as myself, it feels like that awkward moment when a Boss starts shouting at an employee whilst they are with a customer because they made a minor mistake).
But I'll be testing tomorrow. Just to check though, are upgrades from 1.5.x to 220.127.116.11 working properly?