Jump to content
  • Checkout
  • Login
  • Get in touch

osCommerce

The e-commerce.

2.2 MS1 is coming! 2.2 MS1 is coming!


sojomy

Recommended Posts

Ok, so a possible release date for v2.2 MS1 has been announced in the latest weekly summary report here : http://www.oscommerce.com/community/weekly,88

 

What does this mean? When MS1 is released, is this the same thing as saying this is v2.2.1? And is MS2 going to be like saying v2.2.2? Then after MS4 (which could be called v2.2.4) is released, is the next version going to be v2.2 FINAL or v2.3?

 

None of that really matters, because I don't care what anyone calls it. My question is are people going to standardize? Can we all just use the same version for once? So when I ask for help, and someone says what version are you using, I can finally say v2.2 MS1 (or v2.2.1)? Instead of saying, "Oh, I'm using version October 12th 2002". And hearing, "Well I'm not sure what code you have because I'm using December 20th 2002". If we are all using v2.2 MS1, we will all know what eachother's code is (aside from custom changes).

 

Also, is MS1 being declared as officially stable enough to run a live shop? I don't mean do the people here think it's stable enough, I mean do the developers think that it is stable enough? And if so, why the MS1, MS2, etc. naming scheme?

 

Ok, despite my efforts to convince everyone to use the same version, I want everyone to know (especially the developer's) that I love osCommerce. I started playing with it almost a year ago, and kept hearing about a "final version" coming out soon. I held my boss off for this long because of how much support there is for this product, compared to the support you get from a company who sells shopping cart software. Sure, if the cart doesn't work, they'll help you out, but when you mention that you want to customize it, they tell you to figure it out yourself (if you're even allowed to modify it at all). So to the Dev Team, thank you!

Link to comment
Share on other sites

I doubt that everyone on this forum is going to switch to MS1. I've spent 2 months learning and customizing my version and I am not going to go through it again and I can safely say that there is going to be a lot of shop owners that are going to say the same thing. If there was a script you could run that would upgrade a older version to the MS1 without making any changes to your customization, then I would be all for upgrading.

 

I am hoping that this wonderful development team will release contributions that will help us older version owners to fix bug that was fixed in MS1, but I know that may be too much to ask.

 

I agree that this is a wonderful project and I hope that it continues to develop into the best shopping cart on the market, even though I think it is now. And I also hope that these people continue to support us all on whatever version that we use.

 

Thank you to all the people on this forum that has helped me and everyone else, and to the development team for creating this whole community.

Steve

-------------------------

Link to comment
Share on other sites

yeah whoppidy fin doo...

 

I've spent alot of time customizing a snapshot from mid november that I won't think about switching till v2.2 final (which should really be called v2.3).

 

if the devs don't see the changes as important enough to change the version number (say from v2.2 to v2.21 or whatever... no we gotta use milestones?? like we're re-inventing windows here or something), then I really don't see it worthy of updating too (especially since i've spent endless hours on the one I am using now)...

The only thing necessary for evil to flourish is for good men to do nothing

- Edmund Burke

Link to comment
Share on other sites

yeah whoppidy fin doo...

 

I've spent alot of time customizing a snapshot from mid november that I won't think about switching till v2.2 final (which should really be called v2.3).

 

if the devs don't see the changes as important enough to change the version number (say from v2.2 to v2.21 or whatever... no we gotta use milestones?? like we're re-inventing windows here or something), then I really don't see it worthy of updating too (especially since i've spent endless hours on the one I am using now)...

 

Ditto.

Link to comment
Share on other sites

I've been holding off on customizing too much waiting for MS1. I for one, think it has been worth the wait. I have kept myself busy learning more about the program, its stregnths and weaknesses, and working on my products (of which there are many). So in a way the delay has been a blessing for me.

 

As far as upgrading an already customized shop "If it ain't broke don't fix it" most likely can apply. I hope to document my customizations in such a way that as new milestones are added I can figure out what is worth upgrading and how to make the changes to the new files without spending months doing it :) Maybe impossible, but maybe not. I see the coming features as things I can utilize, but maybe adding contributions to MS1 I will realize I don't need to upgrade older stores, but just need to use them for newer stores.

 

I'm excited, I'm looking forward to playing with the new milestone and getting some highly customized, highly specialized, much needed stores online in the next couple of weeks.

 

Debbie

[no external urls in signatures please, kthanks]

Link to comment
Share on other sites

I've thought about this a lot lately. IMHO, it would be nice to have a preselected set of contributions that we could turn on/off as we wanted from the admin section (red/green buttons). That way everyone would be a little bit happier and there would be a lot less confusion for the new folks who are just getting started with OSC.

 

Style sheets are the best way to customize I think, but some folks lean to more radical modifications for their individual tastes. In those cases, a template would be a cool thing to do.

 

I feel the heart of the whole package is the database, as our products certainly vary from site to site. The more custom settings we could put in there, the better.

 

Your mileage will certainly vary, but that's just this old solarman's opinion... 8)

Link to comment
Share on other sites

BY the way, all the entries in the workboard are close.  

So i guess the release date would be Sunday

http://www.oscommerce.com/community/workboard

And I sure hope so, because my boss told me "I'll wait till monday afternoon. If it's not out, I'll just go buy X-Cart and we can have it by tuesday."

Screw that, I want my osCommerce!

Link to comment
Share on other sites

So i guess the release date would be Sunday

 

Not quite :)

 

We are looking over some final bug reports over this weekend and then doing a review of the code base which should only take a day or so then it should be ready for a release.

Mark Evans

osCommerce Monkey & Lead Guitarist for "Sparky + the Monkeys" (Album on sale in all good record shops)

 

---------------------------------------

Software is like sex: It's better when it's free. (Linus Torvalds)

Link to comment
Share on other sites

AFIK The Milestone relaeses are to ease problems using the constantly changing CVS. They arn't final stable releases simply reference points.

 

It is easier for people to download and install the same release, that way there will be hunders or thousands of people all using an identical copy. Now any contributions or fixes can easily state what Milestone they are for. Where as at the moment a contribution made this week may not work with next weeks CVS.

 

This will make it much easier to solve problems because you will be able to say I have unmodified MS1 and cant do this, confident that lots of other people also have an identoical set-up. At the moment people have no way of knowing if what they have is the same as you. You might get todays CVS and I might grab one tomorrow, now I can't help you because mine has some big chunks of new code commited to it.

Link to comment
Share on other sites

Not quite :)

 

We are looking over some final bug reports over this weekend and then doing a review of the code base which should only take a day or so then it should be ready for a release.

 

So it means that it will take another WEEK now.

:?

Link to comment
Share on other sites

So it means that it will take another WEEK now.  

 

I'm sure the developers will do the best they can in their free time when they come home from their day jobs (the jobs that pay the mortgage, put food on the table etc.)

 

Have a little patience my friend, after all this software is provided free.

 

cheers

barry

Link to comment
Share on other sites

From a oscommerce user/supporter point of view.....

 

Releasing of 2.2.MS1 is one thing, the more important thing is going forward... What do I mean?

 

After the release of 2.2.MS1, I, for one is gonna switch to 2.2.MS1, but my biggest concern is that 2.2.MS1 is just 2.2.MS1 with no more "support" to it.... even if a bug is found, there will not be 2.2.MS1.X .

 

If a bug is found after the release of MS1 and if it is not patched onto MS1, user like me would have to go to CVS and pull out the bug fix and path it to my own MS1 copy. Then, I'll be back to my current state.... then it wouldn't really matters if MS1 is released or not.

 

What I think would encourage users to move to MS1 is this.... there would be a branch out of main CVS tree for MS1. Any bug found, related to MS1 would be patched. In terms of MS1, there would be no more feature changes, just bug fixes.... and most importantly, unless required to fix a bug, the database structure should not change....

 

So, for a user who "test drive" the MS1, found that the features are good enough for their usage, they can safely download the latest MS1 release and work on it... and if a bug is being fixed, they would have to patch it.

 

It would definately be easier to patch bugs based on MS1, rather than pulling the file off main CVS, as that file might contains new stuffs meant for MS2 which is likely to break the current MS1.

 

Juz my 2 cents....

 

 

Linus Kerk

Link to comment
Share on other sites

Which contribution have been added to MS1 so far?

 

None, contributions will not be added until around the end of the MS path.

 

See the following from Harald

 

Depending on the work involved with the integration, contributions will be mainly added at the end of the Milestone path when the current codebase has been finalized.

 

The following link should also give you a general idea of what will be included in each MS release.

 

http://www.oscommerce.com/community/workboard

Mark Evans

osCommerce Monkey & Lead Guitarist for "Sparky + the Monkeys" (Album on sale in all good record shops)

 

---------------------------------------

Software is like sex: It's better when it's free. (Linus Torvalds)

Link to comment
Share on other sites

i wouldn't imagine there would be any contributions added to ms1, going by what has been said already contributions will be included in the final release at the end of the MS path. (which is a little bit away yet)

 

cheers

barry

Link to comment
Share on other sites

I haven't seen this question answered in the archives. Apologies if I overlooked it.

 

That said, will there be a supported upgrade path from MS1 to MS2 to MS3 to MS4? Something like an upgrade script or, at the very least, a decent tutorial?

 

--kurt

Gentoo Linux

Link to comment
Share on other sites

Have you decided on the final contributions which you will add at the end of MS path.

 

Not yet we are taking suggestions here

 

http://www.oscommerce.com/forums/viewtopic.php?t=30725

 

We will be going through all the suggestions soon and will then produce a final list of what contributions will be added.

Mark Evans

osCommerce Monkey & Lead Guitarist for "Sparky + the Monkeys" (Album on sale in all good record shops)

 

---------------------------------------

Software is like sex: It's better when it's free. (Linus Torvalds)

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...