[TYPO3-dev] core beta version?

[stefano cecere]

yes, proper beta and tests are done with major releases
these "bugfixes" minor ones aren't really tested by "main street" ;)

now core patches get into the core after 3 +1 by core developers.
but i don't think that they can do a whole bugcheck on different system for each (maybe very minor) patch.

they are core dev, not debuggers!

as far as i work, i am able to get the trunk via svn..
so they could just say: this is the rc for 4.2.2
the changes with 4.2.1 are: . . . .
please check well this and that functions

we can give feedback via bugtracker

after the week they can release a proper packaged 4.2.2

i think this could be an easy solution for everybody...

stefano


Xavier Perseguers wrote:
> Hello,
> 
> Just forwarding this post that was wrongly sent to the core list. But I 
> think the idea is quite interesting:
> 
> -------- Original Message --------
> Subject: [TYPO3-core] core beta version?
> Date: Fri, 10 Oct 2008 11:00:39 +0200
> From: stefano cecere <scecere at krur.com>
> 
> hi everybody
> 
> i just upgraded most of my installations to 4.2.2 (i needed fast to fix 
> the IRRE "can't delete childs" bug)
> now i discover that there is a new bug (introduced by 4.2.2 - 
> http://bugs.typo3.org/view.php?id=9524 ) that breaks decimal values in 
> BE forms
> 
> i am wandering about: shouldn't a (maybe just few days) debug time be 
> programmed for any core upgrade?
> like creating a 4.2.2rc and tell everybody: please test it on this and 
> that new bugfixes?
> 
> i can't follow the trunk core everyday and patch via svn
> what do you think?
> 
> 
> hug and good t3con everybody!!!
> 
> stefano
> -------- [END] Original Message --------
> 
> I think that Stefano is quite right. I updated quite quickly my websites 
> as the 4.2.2 release was stable and was said to contain only minor 
> updates, bug fixes. We all know there was a few bugs introduced such as 
> the mail() problem and the backend passwords. I'm not judging this 
> release, not at all, but "real" tests are made once the new version is 
> coming out, not before as it is easier for many people to download a 
> tar.gz than using subversion on the branch.
> 
> Now, creating a rc1 and a week after the stable release means much work 
> for packaging. Additionnaly this means that the release is not yet 
> stable and many users may not upgrade and thus not test as it would 
> benefit the community.
> 
> I would really like this two phase release. And you?
> 
>