Hi *,
Some time ago there was a discussion about the release for 3.5.
The sub-optimal situation with the release of 3.4.0, was food for the
discussion on the 3.5 release. Quite a lengthy and interesting
discussion at that time (1)
I promised to get back on this issue.
Goal: take a clear look at what influences the development and QA of
3.5.0, in order to make sure that we do not have the problems as with 3.4.0.
I do not want discuss this because I would be convinced that it is
necessary to change the planned release-schedule (2) - I am not even
making that suggestion. Anyway, not now ;-)
I just want to feel a bit comfortable with what we are going to do.
So it is good to make a clear picture of the situation, of the items
involved. I will make a list (not pretending that it is comprehensive)
below.
However, of course it is very unlikely that such an effort can lead to
some solid scientific prediction (anyway, not before the event ;-) ), it
thus serves to get the information and feeling right. Which in itself is
important enough.
And it might lead to the conclusion that more time between freeze and
first RC is needed. Which can be found in either direction of course,
and of which an earlier freeze will definitely be preferred. If..
So, items that come to my mind:
- number and severity of changes on code
how many difficult/basic stuff are touched in these months?
We know that when so much is changed, for sure many nasty hidden
older bugs will surface..
- How much time can one annoying bug ask? Two day, two weeks?
e.g. https://bugs.freedesktop.org/show_bug.cgi?id=40466#c10
- what is the progress in the weak spots in our attention?
Base e.g.
- what can we expect for new large code chunks in the coming months
or integration of some older CWS'es
- the increase in the number of people available for testing
- how many people start working/testing with master/nightly builds?
- how many issues see we from there?
- and how fast are those solved?
- development in the quality and the use of tools for testing
- is attention in testing well spread over Windows / Linux / MacOS ?
- are there other releases/tasks that need attention during that time ?
- how many people are available for beta-RC testing and fixing bugs ?
e.g. the time of the year (Christmas, Western New year)
- can we attract many people for beta-testing
(prize for the top-5 (clear, useful) issue submitting testers ?)
= =
[ Shudder ... would one ever dare to plan any release again
after this listing ? :-p ]
What did I forget?
Maybe some can have a major impact consider?
Is it a useful approach to think a bit more in detail about these items?
Also on the discussion we had before, there was a simple and sound idea
from Norbert (3), worth to consider (expand the time between Beta/RC /
release on Thursday / QA still need to use Daily Build)
Thanks for your feedback,
Cor
1) starting here:
http://lists.freedesktop.org/archives/libreoffice/2011-June/014201.html
2) http://wiki.documentfoundation.org/ReleasePlan#3.5_release
3) http://lists.freedesktop.org/archives/libreoffice/2011-June/014293.html
--
- Cor
- http://nl.libreoffice.org
_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice
