Hi One QA resource will be unavailable on 12th and 13th. So there will be a deviation around one day to the original estimate of one week because only one resource will be working on the above mentioned two days.
Thank You Erandi On Tue, Feb 10, 2015 at 11:39 AM, Dimuthu Leelarathne <[email protected]> wrote: > Hi, > > We'll give a new setup tomorrow morning. Meanwhile please cover the breath > in other areas that have not changed. > > thanks, > dimuthu > > On Tue, Feb 10, 2015 at 11:20 AM, Chathurika De Silva < > [email protected]> wrote: > >> Hi All >> >> Considering the above changes and the bug fixes that will be incorporated >> in the latest pack, there should be a new qa cycle on the latest pack. >> While considering the amount of test cases we have as well as the available >> qa resources (#2) it will take around one week to complete the test cycle >> after the pack release date. >> >> Thank You >> Erandi >> >> On Tue, Feb 10, 2015 at 11:18 AM, Manjula Rathnayake <[email protected]> >> wrote: >> >>> Hi all, >>> >>> Please note that only change with respect to existing permission model >>> is that, appOwner is not allowed to create runtime configs in Testing and >>> Production stages. Configs will be copied at the time of >>> promotion/deployment of application in Testing and Production stages. >>> >>> However, the permissions related to databases will not be changed from >>> existing model where each stake holders of runtime environments are allowed >>> to create databases in their environments. eg. QA can create databases on >>> Testing but not in Production. >>> >>> thank you. >>> >>> >>> On Tue, Feb 10, 2015 at 11:04 AM, Amalka Subasinghe <[email protected]> >>> wrote: >>> >>>> Hi All, >>>> >>>> I'm going to do the following changes to the runtime configs >>>> (datasources, properties, external apis) >>>> >>>> - Create/update/read permissions will be as shown in the table after >>>> this fix. >>>> >>>> - The tenant admin also have similar permissions as appowner; he can >>>> only create in development stage and then resources will be propagated to >>>> the testing and production environments via promoting. >>>> So, "create resources in all environments" checkbox, is not valid >>>> anymore, I'm removing it. >>>> >>>> >>>> >>>> >>>> development testing production >>>> appowner create x >>>> >>>> >>>> >>>> update x x x >>>> >>>> read x x x >>>> >>>> >>>> >>>> >>>> >>>> >>>> dev create x >>>> >>>> >>>> >>>> update x >>>> >>>> >>>> >>>> read x x >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> qa create >>>> >>>> >>>> >>>> >>>> update >>>> x >>>> >>>> >>>> read x x >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> devops create >>>> >>>> >>>> >>>> >>>> update >>>> >>>> x >>>> >>>> read >>>> x x >>>> >>>> >>>> >>>> >>>> >>>> >>>> admin create x >>>> >>>> >>>> >>>> update x x x >>>> >>>> read x x x >>>> >>>> Thanks >>>> Amalka >>>> >>>> >>>> _______________________________________________ >>>> Dev mailing list >>>> [email protected] >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> Manjula Rathnayaka >>> Software Engineer >>> WSO2, Inc. >>> Mobile:+94 77 743 1987 >>> >> >> >> >> -- >> *Chathurika Erandi* >> Software Engineer, >> WSO2 Inc. >> >> *E-mail:* [email protected] >> *Mobile: *+94714 328 612 >> *Blog*: chathurikaerandi.blogspot.com >> > > > > -- > Dimuthu Leelarathne > Architect & Product Lead of App Factory > > WSO2, Inc. (http://wso2.com) > email: [email protected] > Mobile : 0773661935 > > Lean . Enterprise . Middleware > -- *Chathurika Erandi* Software Engineer, WSO2 Inc. *E-mail:* [email protected] *Mobile: *+94714 328 612 *Blog*: chathurikaerandi.blogspot.com
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
