zeke has posted that a beta of version 2.1 should be available in Mid-May. I am not sure how optimistic this ETA is but I wonder how others feel about having an interim 2.0.15 delivered ahead of 2.1.
There are currently about 25 patches in the Bug Tracker which have not been delivered in a production release. The most important of these fixes addresses a Paypal Express problem (http://forum.cs-cart.com/vbugs.php?do=view&vbug_id=1860). There are another 7 bugs confirmed but not yet fixed and another dozen or so unconfirmed bugs
There is also a required change for Authorize.net which went into effect yesterday (4/16) and is required that all merchants be in compliance by 6/30/2010. This issue affects merchants who accept MasterCard or Discover ([url]http://forum.cs-cart.com/vbugs.php?do=view&vbug_id=1861[/url])
At first I was thinking that I do not really want a release before 2.1 but, after giving it more thought, I think it might be a good idea. I think that they should work at addressing as many bugs as they can in the next couple of weeks and then package them up for a release at the end of April/beginning of May. Then they can deliver a 2.1 beta late May or early June (using their same optimistic schedule).
I am curious what others think.
Bob
[quote name=‘jobosales’]There is also a required change for Authorize.net which went into effect yesterday (4/16) and is required that all merchants be in compliance by 6/30/2010. This issue affects merchants who accept MasterCard or Discover ([url]http://forum.cs-cart.com/vbugs.php?do=view&vbug_id=1861[/url])
[/QUOTE]
Actually, the changes required by Discover card and Mastercard are not due until 6/30/2010 for Authorize,net users thanks to them working out an extension with the credit card companies. All other merchant providers have to be compliant on April 16, 2010 (already past this date) for Discover and May 1, 2010 for Mastercard.
As for a 2.0.15 version. I’d like to see one released. I would just want it to contain all the bug fixes that have been made since 2.0.14. No new features would be required.
I would appreciate a “bug-free” 2.0.15 without new features.
This would serve as the “last of the series” in which I can build upon being the “stable build” in order to continue building upon the same technology.
If CS-Cart would be nice enough to provide fixes for all 2.0.14 issues then I would not require a new 2.0.15 release.
HOWEVER since there are legal rules pertaining (We use Authorize.net) I need the appropriate elements FIXED before I anticipate a 2.1 release for obvious reasons.
It’s great that the cart is being upgraded but the community STILL uses 2.0.6/.8 in some cases as they cannot keep up.
[quote name=‘JesseLeeStringer’]I would appreciate a “bug-free” 2.0.15 without new features.
This would serve as the “last of the series” in which I can build upon being the “stable build” in order to continue building upon the same technology.
If CS-Cart would be nice enough to provide fixes for all 2.0.14 issues then I would not require a new 2.0.15 release.[/QUOTE]
Ugh, I can’t even answer my own poll correctly. I meant to vote “Yes - deliver a version 2.0.15 even if it delays version 2.1 by more than a month”
I think a bugfix-only 2.0.15 to wrap up the issues in the 2.0.x series makes the most sense. I also want them to take the time they need to make sure the new features in 2.1 appear without a bunch of new problems popping up.
Bob
That would break CS-Cart Tradition;) On a serious note, I agree with you…please fix what’s broke before breaking the new 2.1 series. This gives everybody a safe haven if all else fails in 2.1 to go back too.
Stu
2.0.15 bug fixs only and take the time to deliver a STABLE 2.1
Agreed. Stable bug-free version in the 2.0 series and take time to release 2.1. I can’t even get out of 1.3.5 because all the bugs and updates in 2.0. I’m actually paying a non-compliance penalty ($20/mo), but it’s better than losing business from a non-functioning cart.
I suggest cs-cart adopt a new numbering scheme.
Two decimal (for example, 2.0.15) be only bug fixes. No new features. This way the bug fixes are less obtrusive.
One decimal (for example, 2.1) be new features.
This way we are clear what we are downloading from now on out.
I suspect this is the way it was supposed to be, but lately the developers are not adhering to it.
[URL]http://cscart.uservoice.com/forums/40782-general/suggestions/664027-new-update-numbering-scheme?ref=title[/URL]
[quote name=‘Triplets’]I suggest cs-cart adopt a new numbering scheme.
Two decimal (for example, 2.0.15) be only bug fixes. No new features. This way the bug fixes are less obtrusive.
One decimal (for example, 2.1) be new features.
This way we are clear what we are downloading from now on out.[/QUOTE]
I think this is a great idea and is fairly typical of software development. Also would appreciate no undocumented feature releases such as the product page changes that happened in 2.0.13.
Relatively bug free version would be a great place to “park” at while testing 2.1 later.
[COLOR=“Red”][SIZE=“3”]take the time to deliver a STABLE 2.1[/SIZE][/COLOR]
i’ll double this!!!:mrgreen:
Let me be the first one to say that 2.1 will not be stable. New features added means new potential for additional bugs. Sure, it can be managed to have less bugs but, let us face it, there will be bugs in 2.1
Therefore, before we dive into new waters, let us have a release 2.0.15 that will have minimum bugs with the old true and tried features. Let us have a fail safe version that us, users, can fallback to if 2.1 will not workout.
When 2.1 arrives, its bugs might not be all fixed until September or October. During that span it would be nice to have something less buggy, yet not as featurefull.
Lets get the show on the road with 2.1 CS-Cart…I think some excellent progress seems to have been made and there is a need to keep the momentum going.
This waiting game might not be over for ever, and I think CS-Cart needs to get their act together, fix all the bugs and go straight to 2.1 with all the checkout changes.
Their focus is on this now as they see this as a critical path fix…why slow them down now after we got them to drop everything to resolve this critical component with all the pressure we had put on them through this forum??
Call it 2.1.01 for bugs introduced as a result of 2.1.
I am still patiently hanging out for 2.1 and that’s when I plan to start using this 99.95559% complete cart once I see the order process fixed up.!!!
[quote name=‘TexasGuy’]Let me be the first one to say that 2.1 will not be stable. New features added means new potential for additional bugs. Sure, it can be managed to have less bugs but, let us face it, there will be bugs in 2.1
Therefore, before we dive into new waters, let us have a release 2.0.15 that will have minimum bugs with the old true and tried features. Let us have a fail safe version that us, users, can fallback to if 2.1 will not workout.
When 2.1 arrives, its bugs might not be all fixed until September or October. During that span it would be nice to have something less buggy, yet not as featurefull.[/QUOTE]
I totally agree.
[quote name=‘sellon’]Lets get the show on the road with 2.1 CS-Cart…I think some excellent progress seems to have been made and there is a need to keep the momentum going.
This waiting game might not be over for ever, and I think CS-Cart needs to get their act together, fix all the bugs and go straight to 2.1 with all the checkout changes.
Their focus is on this now as they see this as a critical path fix…why slow them down now after we got them to drop everything to resolve this critical component with all the pressure we had put on them through this forum??
Call it 2.1.01 for bugs introduced as a result of 2.1.
I am still patiently hanging out for 2.1 and that’s when I plan to start using this 99.95559% complete cart once I see the order process fixed up.!!![/QUOTE]
I don’t think anyone is suggesting that they slow down - just that they take the time needed to make sure that 2.1 is as bug-free as possible. Given the nature of the changes for 2.1, there will inevitably be bugs (especially considering the addition of multi-vendor support). There will certainly be a 2.1.1 update to account for bugs in 2.1 and also a 2.1.2, 2.1.3, 2.1.well-you-get-the-picture. But do you want to contend with those bugs (and the onslaught of releases needed to address them) on your site if they rush a 2.1 release out.
I doubt that 2.1 will lead to the volume of problems that the entirely-new architecture of 2.0 did but delivering a bugfix-only 2.0.15 without those changes stabilizes the existing branch before moving on. I think it makes much more sense - especially when you figure that we are only 3 weeks away from a projected mid-May release date. They have not even finalized the spec for the checkout and you are counting on them getting this done and done right in a short period of time. I have absolutely zero interest in them hitting some arbitrary release date without first accounting for the quality and stability of the code.
Bob
Does it really matter what they call it? Whether it be 8.9 or 2.17 it’s still the next verision. Don’t get all bent out of shape over titles.
[quote name=‘KBM’]Does it really matter what they call it? Whether it be 8.9 or 2.17 it’s still the next verision. Don’t get all bent out of shape over titles.[/QUOTE]
Did you bother reading the opening post? It is the difference between delivering a bug-fix only 2.0.15 first and taking time with 2.1, or delivering a new features plus bug-fix 2.1 quickly and hoping for the best. Sounds like you are willing to gamble that all the new features in 2.1 will not introduce any bugs.
Bob
[quote name=‘jobosales’]Did you bother reading the opening post? It is the difference between delivering a bug-fix only 2.0.15 first and taking time with 2.1, or delivering a new features plus bug-fix 2.1 quickly and hoping for the best. Sounds like you are willing to gamble that all the new features in 2.1 will not introduce any bugs.
Bob[/QUOTE]
I know there is going to be bugs regardless of how they title updates. They will not be able to take their time with 2.1 if everyone knows about it. I don’t think it’s possible for any software producers to release something without bugs anyhow.
I think they should start releasing patches… updating to the lastest and greatest verision is a PIA and will eventually lose a customer or two while in the upgrading process not to mention all the custom modifications you pay for no longer works. Whereas, a simple patch should be quick to install and shouldn’t disturb custom modifications.
I don’t really care what numbering scheme they use but it is absolutley critical that we must have all bugs fixed before the next branch of functionality is added.
In a way we are all to blame, CS-Cart must be bombarded with feature requests when the cart already has more features than most carts (for the price especially).
I would be more than happy to see new features put on the back burner and CS-Cart spend their development time 100% on bug fixing and speeding up the cart.
The cart needs a more solid foundation on which we can add new features onto at a later date.