Pavel JanÃk wrote: > > http://wiki.services.openoffice.org/wiki/Release_QA_Tracking_Tool > - why "*Release* QA Tracking Tool?" > This tool can be used also for regular QA done on development milestone > or other builds as well. Build that are not meant to be > "released".
That's true. Even if it was designed with the release workflow in mind, it can be applied to other builds as well. The SVN repository, in fact, is called just "qatrack". > - "types of users" > Just to clarify - you are talking about "roles", right? Yes, I meant "roles". > - about QAL: there are cases where one user is QAL for more languages > (e.g. Rail), please do not forget it. OK. This should not be a problem. > - "English build -> build providers are notified" > The question is when we want BPRs to be notified. I think they should be > notified on every milestone, not only on builds provided by Sun. Sun > skips some builds. Interesting; I didn't know about this. So how does it work? The source code for "milestone mxxx" is declared frozen and made available and then SUN may or may not create builds from it? It this is the case, we could just use the "source code frozen" message to trigger notification to BPRs. Who decides when the source code is ready for a milestone build? Yours, Andrea. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
