Sophie Gautier wrote:
Jacqueline McNally wrote:
[...]
This definition works well if there is a finite group working on the
release cycle. But here, and with other OSS, everyone has the
opportunity to be involved in the progression of the software through
its release cycle.
So, at this time, we *know* that our RC is not ready to be released. A
showstopper has been raised yesterday at the releases list. It has
already
been marked as fixed, so I'd expect to see a new RC within the next few
days.
Yes, we will, so we will have another one. But don't you think it is
better that many more people are able and willing to download and test
the "releases that are not yet production" ?
Jacqueline are you doing support ? You'll see that RC means nothing for
people and this release will go in production just as if it's a stable.
Yes I do support in fielding questions from endusers and know that beta,
development builds, rc, etc often do not mean much to those that simply
wish to use OOo. At the same time, I prefer to attempt to document and
explain what they mean, as endusers are increasingly asking after the
next version(s) and I prefer to say what is the "stable" version or join
the QA project to assist with the versions in development.
Also, it is endusers that are beginning to make up the greater part of
the OOo community and it would be great if they were invited to
participate and support that community.
Measured and experienced testers are vital, but end-users that are
willing to give it a go are also invaluable as they often do things in
a way that is difficult to include in regression and smoke tests.
So .. the problem with the announcement is, that we cannot be shure
who ist
testing what RC ...
The files have dates and it is the first rc.
users ignore that generally
Agreed. But I thought we were talking about people who were wishing to
participate in the QA process.
The thing, we have missed is to announce the availabilty of the RC at
the QA
project and ask "experienced" people to do the tests. We do have a test
process and protocols, but we do not use it :-(
We have always announced the release candidates widely assuming that
the QA team are in the thick of it and the most aware.
No, we always have announced our own language once QA passed.
Louis asked John or I to make ready web pages and make the announcement.
I did not hesistate and offered. I have participated in the "release"
since 1.0 and the only item I was not sure about this time was which
lists to send the announcement too, and checked that the
http://www.openoffice.org/servlets/ReadMsg?list=announce&msgNo=225
(1.1.4rc) was sent to announce@, discuss@, users@, and [EMAIL PROTECTED]
Can you
imagine what it will be to answer to all that users meeting stoppers and
the image we give ?
The process is : we do smoke tests, update the status page and announce
our release once available. I don't understand why it shouldn't be
respected other wise, no smoke tests are necessary and we can stop QAing
our release.
The reason I checked where the previous announcement was sent is that:
- I am always concerned that the release announements are made before QA
is completed for many languages.
- As the person that responds to the webmaster mail, I understand the
increased volume of messages that can be avoided by making available at
least a certain number of languages available at the time of the
announcement.
I thought this time that the announcement was geared towards those that
do wish to participate and or understand the development and release
cycle which is why I was happy to volunteer.
It is true that I have not participated this last three months, but I
did not think the release process (fortunately or unfortuantely) had
changed. Apologies if it has and I was unaware.
Regards
Jacqueline
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
