Getting bug fixes for PS 1.1

[Skipper]

How does one get the fixes for the resolved bugs in Prestashop 1.1 ?

I see bugs being fixed in the bugtracker, but no possibility to get the fixes. Looking at subversion, it appears that PS 1.2 is already underway, so that I can't know what is development, and presumably too early to use, and what is fix.

Anyone ?

[TropischBruin]

There are not separate bug-fixes, these bugs will be fixed in the next release.

The Team have decided to not release any bug-fixes to make sure that we do not get the same mess as with other carts.

[Skipper]

Ouch, but Thanks! for your answer anyway.

[spott]

But You can allways take needed parts from SVN and with that fix most important bugs for You. I am using this method.

[Soha 8084]

Thanks for the thread Skipper I was wondering too

and I agree OUCH!

spott not every presta user can do that successfully

it took me 3 months for now since I found presta of modifications and now just when am ready to open online the new release is here

and I failed to update the wiki way !!

alot of issues came up and bugs

I want you to please explain that:

is all these bugs caused by new features???
will they be fixed in the next release ???

if I can't fix bugs myself should I wait for the next release??

what about fresh installation??? does it have alot of bugs too??

thanks

[clokwise]

There are not separate bug-fixes, these bugs will be fixed in the next release.
The Team have decided to not release any bug-fixes to make sure that we do not get the same mess as with other carts.

Hang on, are you saying that it's pointless to add any bugs to the Bug Tracker because no one is going to fix them??? I was wondering about that actually because I've submitted a few this week and never gotten any feedback.

BTW, it's just my opinion, but v1.1 was released WAAAY too early. It's still super buggy. Don't get me wrong, it's a fantastic release, but I was shocked when it was released last week. It could have used another month or so of polishing and bug fixing. IMO.

[Skipper]

I really hope I misunderstand this release scheme. Because otherwise this implies that there will never be a truly stable release.

The 1.1 fixed the bugs from 1.0 and introduced news features and bugs with them.
The 1.2, which is the current trunk, fixes the 1.1 bugs and will add new features and bugs with them.

If you want a 1.1 with the known issues ironed out, you will have to do that all manually, because the 1.2 will *not* be a fixed 1.1

TropischBruin commented about the problems other projects have, but, imho, he have left out the word "many": "many other carts" have problems, but not all. Two practiced possibilities:
- Only every second release introduces new features: The 1.1 is stable-enough with new features and collects the bug reports, the 1.2 has no new features, only fixes and cosmetics. The 1.3 is stable enough with new features ...
- Keep trunk for development, and open a subversion branch 1.1 that gets fixes applied. From there, either svn checkouts will help, or patch sets can be created.

As it stands, PS seems to be in "permanent beta" for the so-called "stable". But again: I hope I misunderstand this policy.

[ruilong]

That's why they release RC 1 - 4
then when that's done, they release final version.
1.1 is final version. there has been 1.1.0.1 up to 1.1.0.5 that is todays version.. 5 releases! then you get new features for 1.2
(ok the first RC versions was just released to a small group of testers) but RC3 and 4 was released to the public.. so you had 2 version to find bugs with a dedicated testing team, and 2 more versions with the help of the public, when all the bugs where fixed, 1.1 stable was released.

[Skipper]

Ruilong, the RCs are marked as "not stable enough for production", these are not relevant for many merchants. You touch another issue: How well, how seriously and by whom is the software tested before being released as stable. It appears that there is some room for improvement.

But the original question refers to something that has been declared stable, that is in production *now* and which needs fixes, again *now*.

[TropischBruin]

I really hope I misunderstand this release scheme. Because otherwise this implies that there will never be a truly stable release.

I agree with you

TropischBruin commented about the problems other projects have, but, imho, he have left out the word "many": "many other carts" have problems, but not all. Two practiced possibilities:
- Only every second release introduces new features: The 1.1 is stable-enough with new features and collects the bug reports, the 1.2 has no new features, only fixes and cosmetics. The 1.3 is stable enough with new features ...
- Keep trunk for development, and open a subversion branch 1.1 that gets fixes applied. From there, either svn checkouts will help, or patch sets can be created.

As it stands, PS seems to be in "permanent beta" for the so-called "stable". But again: I hope I misunderstand this policy.

Again I agree.

Maybe whe should call out to the def-Team to release a stable and finished product (PS 1.2) before introducing new features and thus new bugs.

[Soha 8084]

Maybe whe should call out to the def-Team to release a stable and finished product (PS 1.2) before introducing new features and thus new bugs.

I Agree this is what we should do really

please old members especially presta developers contact the presta team for that

I think this release is not yet recommended for production

[Damien Metzger]

The main problem is that most of the bugs are discovered in real online shop, not testing version.
And if a version is not called "stable", no one dare to use it for real. So if we use the release scheme you suggested, there won't be enough people who would use the "stable-enough" release but only waiting for the full stable one.

We call a version "stable" when there aren't any important bugs left after several beta releases. And that's what we've done.

Eventually I'm not the one responsible for the releases, but that's how I see things.

[Skipper]

I understand your position perfectly well. But what do you suggest ?

What is the recommended procedure to have a stable 1.1 instead of a stable 1.2 without "any important bugs left"?

[Damien Metzger]

I've no perfect solution. However, there may be a few leads.

- If the community developed the new features, then our job would be to be responsible for the stability of the whole project: merging the best contributions into the trunk, fixing everything that has to be fixed and releasing versions that can only be more stable than the previous one.

- Make the open source part of our job profitable (eg. http://www.prestashop.com/en/donate/). Currently, there is no way for us to live by only developing the open source project. Make it possible, then releasing bugless versions will not only be something we do freely but a duty.

- Hire someone who will be responsible for your bugs. If there is a bug in one of the website I take care of, I fix it as soon as possible. If you choose to use an open source project and you do not pay anything, then you are the one responsible for the bugs.


Mind that I don't say that we don't care of we release non-stable versions, but remember that we are only penniless developers :]

[ruilong]

I understand your position perfectly well. But what do you suggest ?

What is the recommended procedure to have a stable 1.1 instead of a stable 1.2 without "any important bugs left"?

I suggest that you and the rest of the community help with the testing.
When 1.2 RC1 is released to the public then download it, test it on your localcomputer by these steps
1. install your current live shop localy
2. upgrade to RC1
3. Try adding products and items as with your live shop, doing orders and trying to follow the steps for your customers.
4. report all bugs

this way you can be sure that when 1.2 stable is released the features you use in your shop will work without bugs.

[clokwise]

Wow, based on such reply it seems we will never see a stable 1.1! I hope we are not all repeating our cries when 1.2 stable is released. I'll certainly submit bug reports beforehand, but for now I consider myself lucky that I know PHP just barely enough to hack most of my bugs out myself.

[TropischBruin]

I've no perfect solution. However, there may be a few leads.

- If the community developed the new features, then our job would be to be responsible for the stability of the whole project: merging the best contributions into the trunk, fixing everything that has to be fixed and releasing versions that can only be more stable than the previous one.

I do not agree.

If you release a version without releasing new features in it and call this "stable" then people will start using it. Any bugs left can then be found and irond out and these fixes will be in the next and thus most stable final release.

Any new features released by the community can be in a contribution database if it is a module and will be called "beta"or "RC". If the are stable they will be then adopted by the dev-Team and released as a official part of the next stable release.

- Make the open source part of our job profitable (eg. http://www.prestashop.com/en/donate/). Currently, there is no way for us to live by only developing the open source project. Make it possible, then releasing bugless versions will not only be something we do freely but a duty.

I'm willing the support any open-source project and mostly I do. But looking at the link you are telling me that no-one has ever contributed?

- Hire someone who will be responsible for your bugs. If there is a bug in one of the website I take care of, I fix it as soon as possible. If you choose to use an open source project and you do not pay anything, then you are the one responsible for the bugs.

I do not want to hire anyone to fix bugs found in open-source software, I turn to the forum so people can benifit from my findings and also the solution used to fix it. This is the engine behind open-source, we all work together! :-)

Mind that I don't say that we don't care of we release non-stable versions, but remember that we are only penniless developers :]

I know you all mind and want to make this product what osCommerce used to be (and secretly still is), the best open cart.
But the way PS is going with these releases which are, to be honest, not stable and because of the new features in every release that bring on new bugs that is something I cannot use in my store where as for the moment my store runs a stable osCommerce with 150+ contributions/modifications for over 2 years.

So, again, release a version without new additions but with ironed out bugs before introducing new features.

I applaud to you all in the def-Team who have brought us this great product!

[clokwise]

So, again, release a version without new additions but with ironed out bugs before introducing new features.
I applaud to you all in the def-Team who have brought us this great product!

Yes, I totally agree. The effort put into 1.1 was phenomenal, it is a great leap ahead of 1.0!! BUT... it was absolutely released prematurely. I believe the number of outstanding bugs is substantial enough to warrant a point release (or even two) before 1.2 betas start appearing. I'm willing to put those betas to test and make bug reports and maybe even contribute code if I am able.