Andre Schnabel wrote:

Hi Naoyuki,

Naoyuki Ishimura schrieb:

Hi,

I have no problem to assign build per request base, but if we can have
consensus to allow people who has MGR role should be able to add
build, I believe it's more reasonable. (technically, it's already possible, right?)


Well that is, what I've been told, but what does not work. At least I cannot see, where I could add a new build for one localization only.

Sorry, you're right.
Only 'en MGR' seems to be allowed to add a new build now.
I believe it's reasonable you (comunity QA lead) has that right.

Karl, I feel it's natural Andre has 'en' and 'de' lang attribute, but it seems if one has en attr, then he/she can see only English test cases for maintenance even if he/she has other language attribute. (I tested that my account with en/ja attribute.)
Can you please fix that?
If it's hard to fix, then I can make another admin account who has en/MGR attribute for him.

I would like to allow comminity lead(MGR) to add project/build, but we may need to
have some guildline to avoid duplication.
For example: "MGR who wants to make a new Build in TCM, he/she needs to announce it
to [EMAIL PROTECTED] list at least 2 days before."


Well we have certain times, when we need to test. E.g. all localization teams should now test the 2.0.3 RC's. Therefore I asked for MGR role for all localiations in TCM. (It's my task to coordiante the testing and the most easiest thing for me would be, if I could add a new build).

There might be othere times, to start a test (e.g. spezial localization testing, release test for a new platform ...). Such builds should be added on request, or as suggested with an announcement.

You're right, again...

Naoyuki


André

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to