Skip to main content
Topic: What defines a stable release?  (Read 575 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

What defines a stable release?

Just curious because weare now on beta 13 what defines a stable release and how many more test builds are planned?

Re: What defines a stable release?

Reply #1
what defines a stable release
The right word is "who", not "what" ;-)  There will be a stable release when Peter decides so.

(And I still remember how surprised I was when there was finally a 1.0.)
“It sounded bad to me. Digital. They have digital. What is digital? And it’s very complicated, you have to be Albert Einstein to figure it out.”
- Donald Trump, May 2017

Re: What defines a stable release?

Reply #2
There will be a 'stable' when I feel that it is mature enough.

Version 1.3.17 was pretty solid. I'd rather have people stick with it until I'm confident that v1.4 series can replace it. The changes are pretty big and replace code that had been untouched for years. For an example, HTTPS and proxy server handling was heavily reworked and it appears that the new version still does not work properly for some.

I do not want to push a new 'stable' every day hotfixing newly reported usage-ruining issues that were missed during the beta cycle.

Re: What defines a stable release?

Reply #3
Oh yeah absolutely I enjoy using 1.4 beta and find it much improved I am a software tester by trade so I am used to it I am just excited for a official 1,4

 
SimplePortal 1.0.0 RC1 © 2008-2018