[FLOW3-core] Next steps towards 1.1

[Robert Lemke]

Hi folks,

we've reached feature freeze officially last Friday and during the last day I had a few minutes to think about the next steps. As you know, 1.1 is a big package of features this time and it also contains various API changes. This has a few implications …

First of all we must make sure that upgrading from 1.0.x is a smooth as it can be. For that we need to actually take a few of our projects in their 1.0.x state and use the code migration tool plus the upgrading instructions and see where it brings us. Because we take the liberty to change APIs, we must in turn provide excellent upgrading documentation. Let's take this challenge and see if we can make it a masterpiece!

It's about time to release 1.1 soon, but I think we have more too loose if we rush things than we gain from an immediate release. We need to stop adding new nice-to-have features now and from today's view I propose that we plan in two beta releases:

1.1 beta 1 is for making sure that upgrading from 1.0 projects to 1.1 runs flawlessly. It might be that _new_ features are not complete yet (HTTP for example lacks a few methods in the Response class) but at least it's working as good as before. The new features we've ticked off (new bootstrap, reflection service, file monitoring, localization and so on) should really work now. Documentation is updated to reflect changes, but the new features might not be documented yet.

1.1 beta 2 is for incorporated bug fixes for issues discovered during 1.1 beta 1 testing and for a final test of the new features (HTTP, MVC, content security, ...). All these features must be properly documented, because otherwise they can't be tested, right?

Timeline: Due to holidays and team members catching weird bugs, we're a bit late according to our own set schedule. So let's move this again, like as follows:

1.1 beta 1 on Tuesday, 8th of May (no excuses!)

from then on we only focus on:
	
	1. documentation
	2. implementation of small missing features on the _new_ parts (so, no new ideas, no tiny here and there improvements)
	3. watch bug tracker and implement fixes
	4. update website for 1.1 release

1.1 beta 2 on Tuesday, 15th of May
1.1 final on Tuesday, 29th of May with all bells and whistles

Does that sound like a plan to you guys?

robert

-- 
Robert Lemke
Lead Developer TYPO3 Phoenix and FLOW3
Co-Founder TYPO3 Association

Blog: robertlemke.de/blog
Get involved: typo3.org – flow3.org



-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2263 bytes
Desc: not available
URL: <http://lists.typo3.org/pipermail/flow3-team-core/attachments/20120502/a66db95c/attachment.bin>