OpenCart v1.4.0

furiousweebee wrote:

furiousweebee wrote:My view is that OpenCart should be updated as follows:

• The next release: Fix all minor bugs from v1.4.0 as soon as possible.
• Then, fix all major bugs (i.e. those affecting most users or those with the most potential for security risks etc).
• Then, fix any resulting/outstanding minor bugs.
• Release v2.0 as a major upgrade, implementing as many new features as possible (providing most users will benefit from them). If this takes six months, so be it - the version prior to this should be relatively bug-free and working nicely by this point.

Basically, I think the current version includes almost everything a standard store operator would need, so the most important thing is to ensure that's fully working before undertaking any new works. I'd rather wait several months for a thoroughly tested major upgrade than have to tweak every OpenCart installation every few weeks to fix bugs or upgrade extensions.

Just re-iterating my opinion that the next release needs to happen as soon as possible before looking at any new features. There are already various minor bugs that need to be fixed. Many people, such as myself, rarely upgrade to a major release without first waiting for the inevitable minor patches that follow, so you're potentially losing OpenCart "customers" every passing day.

I personally think that bug fixes should be separated from regular releases. Daniel has enough people here finding bugs and ways to fix them that he could spend his time working on new releases while the community works on fixing bugs in the previously released version. I suspect most of the impatient people awaiting 1.4.1 are not awaiting new promised features, but bug fixes from 1.4.0.

joomx wrote:Alpha, Beta, RC, Stable, for testing???

any progress is good progress... who cares what level it's being released. just wait 'till it's out

rocksteady,
danno~

dannowatts wrote:

joomx wrote:Alpha, Beta, RC, Stable, for testing???

any progress is good progress... who cares what level it's being released. just wait 'till it's out

rocksteady,
danno~

Not really!
If the release is published as 'Stable' we here in this forum have to deal with the questions if there are major bugs in it (as they are in 1.4.0).

So, this makes a big difference.

joomx wrote:Not really!
If the release is published as 'Stable' we here in this forum have to deal with the questions if there are major bugs in it (as they are in 1.4.0).

So, this makes a big difference.

Agreed. Then we just get 50 posts of "when can we expect 1.4.2? 1.4.1 is too buggy"

joomx wrote:

dannowatts wrote:

joomx wrote:Alpha, Beta, RC, Stable, for testing???

any progress is good progress... who cares what level it's being released. just wait 'till it's out

rocksteady,
danno~

Not really!
If the release is published as 'Stable' we here in this forum have to deal with the questions if there are major bugs in it (as they are in 1.4.0).

So, this makes a big difference.

i meant you shouldn't worry about the status yet. wait for it to be released before expecting daniel to tell you the status. when it's launched and released, available for download, then we'll know what status it's at.

rocksteady,
danno~

ypour going to have to wait another day. my internet has gone really slow today. i have not bee able to do any proper testing. my ftp is just disconnecting all the time.

Daniel wrote:ypour going to have to wait another day. my internet has gone really slow today. i have not bee able to do any proper testing. my ftp is just disconnecting all the time.

That's not good enough Daniel!

Just kidding. Will there be a changelog or list of bug fixes with this release?

furiousweebee wrote:

Daniel wrote:ypour going to have to wait another day. my internet has gone really slow today. i have not bee able to do any proper testing. my ftp is just disconnecting all the time.

That's not good enough Daniel!

Just kidding. Will there be a changelog or list of bug fixes with this release?

Do you see a changelog for the past versions/revisions in the wiki? I believe not... so we will most likely (highly unlikely) not see one for v1.4.1~

It depends one whether he obliges our beta tester proposal.

mOrAtHa wrote:

furiousweebee wrote:

Daniel wrote:ypour going to have to wait another day. my internet has gone really slow today. i have not bee able to do any proper testing. my ftp is just disconnecting all the time.

That's not good enough Daniel!

Just kidding. Will there be a changelog or list of bug fixes with this release?

Do you see a changelog for the past versions/revisions in the wiki? I believe not... so we will most likely (highly unlikely) not see one for v1.4.1~

This is why OC needs a Release Manager as previously discussed in this thread:

http://forum.opencart.com/viewtopic.php ... 240#p46759

@mOrAtHa and furiousweebee:

Can the two of you work on a changelog or list of bug fixes to help Daniel out?

OpenCart.us wrote:@mOrAtHa and furiousweebee:

Can the two of you work on a changelog or list of bug fixes to help Daniel out?

Possibly, though I have no experience in that. I think if Daniel is the person making the changes, then as long as he can roughly list them, I'm happy to help expand on them and formalise.

OpenCart.us wrote:This is why OC needs a Release Manager as previously discussed in this thread:

http://forum.opencart.com/viewtopic.php ... 240#p46759

@mOrAtHa and furiousweebee:

Can the two of you work on a changelog or list of bug fixes to help Daniel out?

The first step, as Q already pointed out, is a pre-release of beta-release route so that we can iron out any (if any) bugs or other issues before a public release.
Maybe one of the group that is up for beeing beta-tester could create the change list or changes etc.

Where do you sign up for beta test then?

dbstr wrote:Where do you sign up for beta test then?

You cannot.

i2Paq wrote:

dbstr wrote:Where do you sign up for beta test then?

You cannot.

That was a short answer. Could you go one step further and explain why?

Is that dbstr is not qualified, that you do not like his posts and don't want him involved?

Or is it simply a policy to invite testers?

I personally have no desire to be one, so i"m not asking for myself. But I'm sure dbstr and probably others are wondering whether

1) only he cannot

2) others may but some others cannot

3) you have to be invited

peteVA wrote:

i2Paq wrote:

dbstr wrote:Where do you sign up for beta test then?

You cannot.

That was a short answer. Could you go one step further and explain why?

Is that dbstr is not qualified, that you do not like his posts and don't want him involved?

Or is it simply a policy to invite testers?

I personally have no desire to be one, so i"m not asking for myself. But I'm sure dbstr and probably others are wondering whether

1) only he cannot

2) others may but some others cannot

3) you have to be invited

We are waiting on the answer of and actions by Daniel on this beta-test route.

I personly think that tester should be invited, but atm. we are not sure what would be the best way.
Also the list with beta testers should be short and they should have the right skills

So to answer your 1-2-3

1. No
2. Yes
3. Yes

whats going to happen i that I will upload the new version to my google code hosting and post a link on the internal forum. hopefully I should get some feedback.

then i will put the link on the download page.

the only thing i'm worried about is how non english characters are going to look and work sin ce i have changed the encoding of the database.

It's all cool.. ;-)

Daniel wrote: i have changed the encoding of the database.

In what direction...?

Daniel wrote:whats going to happen i that I will upload the new version to my google code hosting and post a link on the internal forum. hopefully I should get some feedback.

then i will put the link on the download page.

the only thing i'm worried about is how non english characters are going to look and work sin ce i have changed the encoding of the database.

when you say the internal forum what forum do you mean.