PureBasic Forums - English

@Fred,
Belive there is not one people who will say...it was to early for a beta release.

If there someone...I will make him silent...really!

I don't want it this weekend or next week (half term, busy with the family), I don't want to be one of the last to get the update.

Fred & Freak:You could have it on a download link that you have to click:

"Yes, I understand its a beta and I will not complain if it accidently formats my hard drive!"

-Anthony

Derek wrote:I don't want it this weekend or next week (half term, busy with the family), I don't want to be one of the last to get the update.

Be silent

It strikes me that the more time we spend asking for this the more time the team has to spend dealing with these requests and less time they have to get the thing to Beta stage.

Isn't a stable Beta what we really want?

It also seems to me that more of us there are who have early Beta, the more questions and suggestions the team gets. Which equals more time responding. Which means less time developing.

Just a thought.



(Treasure it - I seldom have a thought)


Edited to stablise the Beta (above)

Dare wrote:Isn't Beta what we really want?

I see you have the alpha

I see you are a speculator.

Was just thinking about the last beta release.

It also seems to me that more of us there are who have early Beta, the more questions and suggestions the team gets. Which equals more time responding. Which means less time developing.

And the likelyhood that more bugs will be found at a faster rate?

DoubleDutch wrote:

It also seems to me that more of us there are who have early Beta, the more questions and suggestions the team gets. Which equals more time responding. Which means less time developing.

And the likelyhood that more bugs will be found at a faster rate?

But there's no point in releasing it with known bugs that are being worked on just to get more bug reports.

And dont forget...

After release is before release.
So there will be no release without a bug.
As more tester test the release as more bugs will be found.

In my opinion, we should wait for the BETA version.

The ALPHA version is only for testing, if new features work, so that the IDE doesn't crash all the time if you work with it.

But in my opinion, we should expand the BETA period, because the last BETA period (3.04 => 4.00) was too short. We needed 2 Updates (4.01 and 4.02) to fix most of the known problems and there are still many bugs to fix!

Considering this experience, that the last BETA period was quite short (imho too short), I suggest to keep the ALPHA period short, but closed, so that we have time enough to explore the new version for bugs when the BETA is released.

We need a lot of time, because there are bugs that are found very late, e. g. if the BETA period is over.
YOu may have a look at the PB history/changelog (4.01). There is a bug listed that I've discovered (ExaminePreferences didn't list first key).
I found this bug too late so that it couldn't be fixed within BETA-4.00-period.


All in all, my opinion is that ALPHa period should be kept short, but closed. Publishing ALPHA version would be more work for Fred & Co., so the best thing is to wait for BETA release.

AND51 wrote: Considering this experience, that the last BETA period was quite short (imho too short), .

So it is time to open the PB4.10 as beta period.

It would seem to me that Fred and freak would be best positioned to make the decision as to when/whether alpha/beta.

I'm content to rely on their judgement. I believe they've done a very good job with PureBasic so far.

They have probably learned to make sure they don't inadvertently 'announce' any future alpha's though

cheers

OMG, I thought, you requested Fred to release ALPHA, but the title of this topic says "BETA".

In spite of that: As I said, we should wait, until ALPHA period has finished successfully.

AND51 wrote:OMG, I thought, you requested Fred to release ALPHA, but the title of this topic says "BETA".

In spite of that: As I said, we should wait, until ALPHA period has finished successfully.

Tell what is the scope of 'finished successfully'?
The only scope for me is:
All feature implemented (not really bugfree).
So no more new feature is planed for next release.
-> beta can go out.