[TYPO3-core] Thoughts about the 6.2 stabilizing phase

[Steffen Gebert]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Ernesto,

> Now let's go on with TESTING TESTING TESTING! Try it out in your
> own projects, report experiences, work on improving stability by
> reporting your findings.

what about upgrading typo3.org? Would be a good test :)

Kind regards
Steffen

- -- 
Steffen Gebert
TYPO3 Server Administration Team Member

TYPO3 .... inspiring people to share!
Get involved: http://typo3.org

My wish list:
https://www.amazon.de/registry/wishlist/922E3JYSQ7CV/ref=cm_wl_sb_v?sort=priority

On 21/11/13 22:01, Ernesto Baschny wrote:
> Hi fellow TYPO3 CMS contributors,
> 
> the main goal now is a "stable 6.2 release". Please let's focus on
> the important stabilization! Try to follow these principles:
> 
> * No experiments.
> 
> * Do not make changes in parts that you don't fully understand.
> 
> * Do not touch areas that are the "dark side of TYPO3" without 
> consulting expert advise first.
> 
> * Consider the impact of the changes you make - both positive and 
> negative. TYPO3 CMS is a professional product and we have the 
> responsibility to maintain this reputation.
> 
> * Be aware of who is working on what and who are the persons of
> trust and ask in certain areas. Don't step on each others toes =>
> communicate!
> 
> * Make sure the Unit and Functional Tests work on your setup so you
> can test them yourself before merging something. Do not rely only
> on Jenkins and Travis!
> 
> * If you have some patch that you reviewed and consider it
> "stable", take a step back and give it some time. If not 100% sure,
> wait a couple of hours before merging, maybe ask some expert around
> for a further review.
> 
> * If you need to revert some change, please explain that to a
> broader audience (i.e. through this mailing list, like Markus Klein
> did some threads ago - a very valuable input to the team and a way
> for the whole team to learn from mistakes).
> 
> In case of doubt, please ask the release team (Olly Hader, Steffen 
> Ritter, Christian Kuhn, Helmut Hummel, Benni Mack, Xavier
> Perseguers or myself).
> 
> We won't be working on NEW FEATURES yet. If some of you are
> already working on these or wanting to review them, keep them in
> your own for later. We won't be branching off the 6.2 development
> in order to avoid the extra work of backporting fixes in the
> current development phase. The plan is to branch only as soon as
> 6.2.0 is released.
> 
> As of "New Features" for 6.2, there is no plan to add anything
> else. The current state is feature complete. I mention "plan"
> because it might turn out that we require certain "feature" in
> order to gain (i.e. API) stability. Also improving Usability might
> be seen as a "Feature" but in some cases the lack of usability is a
> Bug. Consult me in case of doubt!
> 
> Now let's go on with TESTING TESTING TESTING! Try it out in your
> own projects, report experiences, work on improving stability by
> reporting your findings.
> 
> Kind regards and happy coding!
> 
> Cheers, Ernesto
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJSjzg3AAoJEIskG/rSlyw41+cH/0A1iCin9E06Zb5sKd139qH4
0NvKOr7ICyjFAbcSbfut6/HxGLt92sj+o+rTiRa4wA7FG7bv4fvFlJqnyf44JUA8
p6W/1GF64NXsFzbWYVqT1BE/0j25h7IQD9NkccIQbp9MgYNcc9z8X+kwYwsL0vOF
z5WAHHQyQqM2X/frkmN5V9D6UXUJMzkSu7vQxR06TwOv4GVbK8Acpyu8WtSIy6lH
5TkHPeR8sKxny8Q9CFRCmFPGCzR3Ba/jvdXycm5ydPvW6xFO/kKhzDQxu+Lsl44M
BXjZMb+JE/wBAfpCoGyog6YaUol9NuXqpC+ZhfPIHy+5btn6QrB+jbhr0V48Nwo=
=UTQ3
-----END PGP SIGNATURE-----