We are on beta 11 and there are already 60 threads posted concerning bugs and problems. This is depressing. It doesn't look like we are any nearer a stable full release than we were with some of the earlier betas.
Why?
Because we are still adding functionality and making changes when we should be just fixing bugs.
I would like a reliable version of PB2 to use.
I don't want to play around with the language indefinitely.
Does anyone agree with this view?
Too many betas, too many changes
No. 3.94 is the current reliable version you requested. There is no later "reliable" version.
Since you (in another thread) jumped directly from beta 1 to beta 11 you really shouldn't comment on the nearness to the final release in the earlier betas. As I've tried all betas I assure you that beta 11 is a lot more stable than many earlier betas. There is definetely more bug fixing than feature adding going on. Only a few minor "features" have been added, most of these have been to fix shortcomings in the current implementation/design of some already existing feature.
Also, most of the bugs reported for beta 11 and unfixed bugs reported for previous betas are a lot less severe than bugs reported for the earlier betas so you cannot judge by the count alone.
Since you (in another thread) jumped directly from beta 1 to beta 11 you really shouldn't comment on the nearness to the final release in the earlier betas. As I've tried all betas I assure you that beta 11 is a lot more stable than many earlier betas. There is definetely more bug fixing than feature adding going on. Only a few minor "features" have been added, most of these have been to fix shortcomings in the current implementation/design of some already existing feature.
Also, most of the bugs reported for beta 11 and unfixed bugs reported for previous betas are a lot less severe than bugs reported for the earlier betas so you cannot judge by the count alone.
-
netmaestro
- PureBasic Bullfrog
- Posts: 8451
- Joined: Wed Jul 06, 2005 5:42 am
- Location: Fort Nelson, BC, Canada
I know it's a difficult process but we really are getting quite close now. The number of outstanding bugs is not large and it hasn't been growing much in the last couple of weeks. And as trond points out, they are a lot less serious issues than earlier ones. You have to bear in mind that this version represents a major rewrite of a lot of the libraries and that comes at a price. It won't be long now as the team has been hinting that the beta period is drawing to a close and they are firm that no new changes are planned between now and then.
BERESHEIT
-
Bonne_den_kule
- Addict
- Posts: 841
- Joined: Mon Jun 07, 2004 7:10 pm
http://en.wikipedia.org/wiki/Development_stage#Beta
Betas are supposed to be buggy.A beta version or beta release usually represents the first version of a computer program that implements all required features although additional features may be added. It is likely to be unstable but useful for internal demonstrations and previews to select customers, but not yet ready for release. Some developers refer to this stage as a preview, as a technical preview (TP) or as an early access.
geoff,
i'm agree with you when you say there are lot's of changes.
but i can't be agree with the other points.
PB4 is still beta. So if you decided to use it in production, it is at your own risk. And no, it's not so buggy... i think it is becoming very reliable (for my needs) and much more consistent. the work done by fred, freak, bericko and users feedback is really wonderful.
PB4 was announced since the first beta, that backward compatibility was broken. It was clearly announced.
As a funny remark, i can say it's much more difficult to convert PB4.0 to PB3.94 than to convert PB3.94 to PB4.0
PB4 rocks, in my opinion. happy user
i'm agree with you when you say there are lot's of changes.
but i can't be agree with the other points.
PB4 is still beta. So if you decided to use it in production, it is at your own risk. And no, it's not so buggy... i think it is becoming very reliable (for my needs) and much more consistent. the work done by fred, freak, bericko and users feedback is really wonderful.
PB4 was announced since the first beta, that backward compatibility was broken. It was clearly announced.
As a funny remark, i can say it's much more difficult to convert PB4.0 to PB3.94 than to convert PB3.94 to PB4.0
PB4 rocks, in my opinion. happy user
No programming language is perfect. There is not even a single best language.
There are only languages well suited or perhaps poorly suited for particular purposes. Herbert Mayer
There are only languages well suited or perhaps poorly suited for particular purposes. Herbert Mayer
-
Psychophanta
- Always Here
- Posts: 5153
- Joined: Wed Jun 11, 2003 9:33 pm
- Location: Anare
- Contact:
-
Killswitch
- Enthusiast
- Posts: 731
- Joined: Wed Apr 21, 2004 7:12 pm
-
Num3
- PureBasic Expert
- Posts: 2812
- Joined: Fri Apr 25, 2003 4:51 pm
- Location: Portugal, Lisbon
- Contact:
True...
Remember that PB 3.xx came in many versions too, most of them because of necessary updates and bug fixes...
PB 4.0 will have much less bugs because of the heavy Alpha & Beta releases , and this is very good, cause will never reach PB 4.94
due to them ...
*Future Landmark*
After PB 4.2 Fred will start working on #PB (sharp PB) and at least two more parallel flavours: CPB (c PureBasic) and VPB (Visual PB)
Remember that PB 3.xx came in many versions too, most of them because of necessary updates and bug fixes...
PB 4.0 will have much less bugs because of the heavy Alpha & Beta releases , and this is very good, cause will never reach PB 4.94
due to them ...*Future Landmark*
After PB 4.2 Fred will start working on #PB (sharp PB) and at least two more parallel flavours: CPB (c PureBasic) and VPB (Visual PB)
Re: Too many betas, too many changes
I desagree...geoff wrote:We are on beta 11 and there are already 60 threads posted concerning bugs and problems. This is depressing. It doesn't look like we are any nearer a stable full release than we were with some of the earlier betas.
Why?
Because we are still adding functionality and making changes when we should be just fixing bugs.
I would like a reliable version of PB2 to use.
I don't want to play around with the language indefinitely.
Does anyone agree with this view?
It's better to push the Beta version to the limits to find as many bug as possible. If Fred and Freak take the time to test all command one by one the final release need more time to be ready.
So by converting yours codes from V3.94 to V4.00 to find and report bug will speedup the process and help Fred and Freak to complete the V4.00.
Regards
Guimauve
-
maw
Give us more betas!!!
Geoff: since you don't seem to have the time and/or patience to keep up with every new beta that is released and keep track of relevant posts on the forum you really shouldn't be using the betas! Just wait for the final 4.0 which will be ready... When it's done!
The privilege to use a beta does, in my mind, come with alot of responsibility!
Geoff: since you don't seem to have the time and/or patience to keep up with every new beta that is released and keep track of relevant posts on the forum you really shouldn't be using the betas! Just wait for the final 4.0 which will be ready... When it's done!
The privilege to use a beta does, in my mind, come with alot of responsibility!
a "bug free" version is highly unlikely (near impossible). I like the number of betas fred has "shared" with us, as it affords us an opportunity to test in our own environment as opposed to him testing in a PB lab.geoff wrote:Yeah OK, fair comment.Psychophanta wrote:Geoff, be patient
Does anyone think a bug free version is achievable? Like a good C compiler, for example?
Does anyone else think this is a worthwhile target?
If I want "stability" I still use 3.94. If I want features, I'm happy to try 4. I'm personally pleased we're getting all this feedback (bug fixes) before a production release.
cheers