Hi, I'd like to propose changing our naming of releases to use Milestones instead of betas and alphas. The main reason is that we're practicing time boxing and agile development. This means that each release gets new features/ improvements. This is the main point of agile development: release pieces of working features at each release. Betas suggest that the release is almost finished in term of features. On Monday we've planned to release 1.1 Beta 1. However it's no feature complete as we've planned 3 betas and 2 rcs and we plan to add features in the betas. Thus I believe we should use the word "Milestone" which is better suited for our style of development (Note: Milestone was suggest by Sergiu, I'm just borrowing his idea here ;-)). So I'd suggest to change our plan to be: * 1.1 M1 - 28th of May * 1.1 M2 - 18th Of June * 1.1 M3 - 9th of July * 1.1 M4 - 30th of July * 1.1 M5 - 20th of August * 1.1 Final - 3rd of September We only need to agree that M4 and M5 should be focused on bug fixing and not introduce new features (or smallish ones only). This is because we're not yet quite ready with our automated tests. If we had a strong suite of tests we wouldn't need to do that and this is the goal we need to achieve. So I hope we'll see more tests written in M1 to M3. Here's my +1 to this new name. Please cast your votes. Thanks -Vincent

Hi, I'd like to propose changing our naming of releases to use Milestones instead of betas and alphas. The main reason is that we're practicing time boxing and agile development. This means that each release gets new features/improvements. This is the main point of agile development: release pieces of working features at each release. Betas suggest that the release is almost finished in term of features. On Monday we've planned to release 1.1 Beta 1. However it's no feature complete as we've planned 3 betas and 2 rcs and we plan to add features in the betas. Thus I believe we should use the word "Milestone" which is better suited for our style of development (Note: Milestone was suggest by Sergiu, I'm just borrowing his idea here ;-)). So I'd suggest to change our plan to be: * 1.1 M1 - 28th of May * 1.1 M2 - 18th Of June * 1.1 M3 - 9th of July * 1.1 M4 - 30th of July * 1.1 M5 - 20th of August * 1.1 Final - 3rd of September We only need to agree that M4 and M5 should be focused on bug fixing and not introduce new features (or smallish ones only). This is because we're not yet quite ready with our automated tests. If we had a strong suite of tests we wouldn't need to do that and this is the goal we need to achieve. So I hope we'll see more tests written in M1 to M3. Here's my +1 to this new name. Please cast your votes. Thanks -Vincent ------------------------------------------------------------------------ -- You receive this message as a subscriber of the xwiki-dev(a)objectweb.org mailing list. To unsubscribe: mailto:xwiki-dev-unsubscribe@objectweb.org For general help: mailto:sympa@objectweb.org?subject=help ObjectWeb mailing lists service home page: http://www.objectweb.org/wws