We're just wrapping it up today... We decided to move straight to final for 3.2 and defer any known issues for 3.2.1 - it wasn't worth holding back the release any longer.
Originally Posted by Stju
How about Switch Button?
It still haven't made it's way to SVN...
I have it running locally, just making sure it's worthy of releasing currently. It's a pretty trivial component but I'm tempted to make it a ux for now as it hasn't had a lot of time under testing yet.
What we may do is release it separately ahead of 3.3, as well as making it a 3.3 component. That way we can release it as soon as it's ready and still have it as an official component. I'd rather take that approach than ship something half-working.
We're just wrapping it up today... We decided to move straight to final for 3.2 and defer any known issues for 3.2.1 - it wasn't worth holding back the release any longer.
I have it running locally, just making sure it's worthy of releasing currently. It's a pretty trivial component but I'm tempted to make it a ux for now as it hasn't had a lot of time under testing yet.
So you are releasing a new version with known open bugs??? I understood that right?
We're just wrapping it up today... We decided to move straight to final for 3.2 and defer any known issues for 3.2.1 - it wasn't worth holding back the release any longer.
We decided to issue a release candidate after all to allow for some final testing. I'm confident that the RC is a very stable release already but it's better to tread on the side of caution.
Originally Posted by TizianoF
So you are releasing a new version with known open bugs??? I understood that right?
With a library this size covering so many browser/OS combinations of course there are known bugs. They're open and visible in the bugs forum. We try to tread the line between fixing as many as we can for each release, adding desirable new features and making releases timely and frequent.
Thank you and the whole team. As you don't have very long release cycles it'S the best to concentrate on stability instead feature richness. All features can be used as ux until they are stable enough to become a part of the core (or not).
I'm personally very happy with the releases, all is very stable. I ran 3.2beta now the whole time while developing and didn't had any problems or obvious bugs. Good work!
vg Steffen
--------------------------------------
Release Manager of TYPO3 4.5 energlobe.de - german online magazine
We already prepared our code to be 3.2 compatible and with beta we ran just in to few issues, that were fixed already!
We are ready! Thank You Ext team!
Stju
Maybe it's just me, but in my experience it's usually best to stay well clear from "the bleeding edge." And any major software product, shortly after any major release, is a bleeding edge.
+1 for such component But this will be addressed to a higher version. Maybe someone already worked on something simular? I'm just fronted with this request from a client
vg Steffen
--------------------------------------
Release Manager of TYPO3 4.5 energlobe.de - german online magazine