osHelpers.com Posted March 6, 2010 Share Posted March 6, 2010 I am constantly finding myself battling statements on other forums such as: "oscommerce is old and hardly updated" "OSC is hard to manage and practically dead. "the latest stable 2.2 branch (which is still release candidate 2 and requires 2 patches after install) was released on January 15, 2008. That's over 2 years ago. Latest from branch 3.0 was the release of Alpha 5 on March 15, 2009 which is exactly a year ago - and it's an alpha release which makes me reluctant to put it on production web site." ...the list goes on and on. One of the main complaints I am seeing is the lack of periodic updates so I am wondering: What IS the current state of osCommerce? Link to comment Share on other sites More sharing options...
Jan Zonjee Posted March 6, 2010 Share Posted March 6, 2010 What IS the current state of osCommerce? This is the current state of what will become the next release of version 2.2. Link to comment Share on other sites More sharing options...
MrPhil Posted March 6, 2010 Share Posted March 6, 2010 As I've commented on elsewhere, it is irrelevant as to what is in github. What counts is what's in an official release that distributors pick up and is available for download from this site. How about declaring the current state (if reasonably stable) as RC3? Let's get something out there that shows that osC is in fact supported and alive! What counts most of all is that the world can see that osC moves forward. By the way, development is going about it all wrong. A Release Candidate should not be getting new code and features. The only thing that should be done is to fix reported bugs in the previous RC. Put out RC3, and if it's not too bad, make it Gold. Immediately start work on 2.3, to hold all the security fixes still dribbling in to 2.2. Until 3.0 has been out (Gold) for quite a while, osC is obligated to keep the 2.x stream alive for security and stability updates. New features can be omitted from the 2.x stream, but security and stability fixes are mandatory. Likewise, osC 3.0 needs to get moving forward. Let's go to Beta 1, and commit to a schedule of Betas and then Release Candidates. No more dragging on for years at an Alpha release. Show that osC is moving forward. Compare osC with SMF (Simple Machines Forum): 2.0 is at RC3 (moves forward at a reasonable pace), while 1.0.x and 1.1.x are still receiving security-related updates (but no new features). Link to comment Share on other sites More sharing options...
New 
Recommended Posts
Archived
This topic is now archived and is closed to further replies.