Re: [native-lang] OpenOffice.org 1.1.5 Release Candidate Is Here
Jacqueline McNally <[email protected]>
| Newsgroups | gmane.comp.openoffice.nativelanguage |
|---|---|
| Message-ID | <[email protected]> |
Thank you for your responses Andre. I agree with all that you have said this and at other times on the matter. This is the only point that I would like to discuss further. >> >> We have always announced the release candidates widely assuming that >> the QA team are in the thick of it and the most aware. > > > No, that has been started with 1.1.2 or 1.1.3. Before that time we used > to announce RC within the project but not to the enduser. Prior to 1.1.2 our community was much smaller. I would say too, that our community now consists of many more endusers, whereas our early endusers tended to be people and organisations that did not subscribe to our lists or participate in their way previously. So now our "endusers" are perhaps those that are more aware being part of the community and there are those that do not form part of our community and perhaps considered the "public" or endusers-at-large. I hesitated about sending the announcement to announce@ for this very reason. But saw that the 1.1.4rc (http://www.openoffice.org/servlets/ReadMsg?list=announce&msgNo=225) announcement was sent to this list, so sent the 1.1.5rc one. >> Perhaps we can re-visit the process on the QA project list. I really >> would like to invite more people to join the QA project as I find that >> when a release is made this is when we have the discussions of "I >> didn't know it was going to work that way" when it has been >> progressing that way for months :( > > > http://qa.openoffice.org/servlets/BrowseList?list=dev&by=thread&from=489067 > > Has been stopped (imo), as: > - discussion abut re-establishing the release committee slowed down > - current (formal) QA-Leads don't care Yes you are right, you introduced a very good summary as to how you saw the release process from a QA pov. I too documented the marketing or publicity process wrt not just releases but all pr. This too was commented on and then left. Other than my attempt to stick to what was documented and encouraging discussion as you have done, I don't know what to suggest. I have been mostly out of list discussions this last three months, and I'm sorry if I have missed an important discussion or community decision during this time. Regards Jacqueline (who is already worrying about how to explain a second beta)