Dimuthu, This is great!
Do you think you, or someone else, could put these actions into some sort of scenarios (like the ones that we did for sign-up/log-in here [1]<https://docs.google.com/a/wso2.com/document/d/1o_nECJfstub_GGD-0Elcnc2U1oAhEEvqybLijv5ziE4/edit#heading=h.36pqj9u28y4t> )? For example, there will be a scenario in which someone is the only developer for an app (single person scenario) and application owner - what will that person be doing to release various versions of the app? Then there are smaller team scenarios with some sort of small project in which people just release v.X and all start working on v.(X+1). Then some sort of more complex projects in which some features span multiple versions (?) And probably some scenarios in which a patch needs to be released to a previously released v.(X-1)... At WSO2 we have people like yourself with experience leading many projects from simple to complex. I think if we describe them as scenarios rather than just a set of individual actions, this will help us both with the UI design and realistic automated tests. I hope this makes sense. I'll be happy to help - but my experience in this area is much inferior than yours. Thanks again for taking the lead on this! That is one of the key areas of the AF/AC functionality! Dmitry [1] https://docs.google.com/a/wso2.com/document/d/1o_nECJfstub_GGD-0Elcnc2U1oAhEEvqybLijv5ziE4/edit#heading=h.36pqj9u28y4t On Mon, Apr 7, 2014 at 2:52 PM, Dimuthu Leelarathne <[email protected]>wrote: > Users > > Developers (And any user with develop permission) > > Description > > Users will have many versions in development for a single application. > Each version will have it's own repository. Users will want to see their > build statues and high level picture of current status of each of the > version undergoing development. > > Acceptance criteria, > > As a authorised user (developer, app owner) I will be able to, > -View repos of versions in the development phase > -Trigger builds and deployments of versions in the development phase > -View which build was last triggered > -View which build is currently deployed > -Test applications that are deployed > -Set/unset auto-build/auto-deploy parameters > -Create new branches by selecting a version and giving the new version > -Fork the whole repo if the repo is not forked already. Once forked all > branches in the master repo is visible in forked repo > -Add newly added versions to my forked repo > -Commit to forked repos and master repo > -Edit code using cloud based development tooling > > > As an app owner > -Delete the forked repo > > thanks, > dimuthu > > > > > -- > Dimuthu Leelarathne > Architect & Product Lead of App Factory > > WSO2, Inc. (http://wso2.com) > email: [email protected] > Mobile : 0773661935 > > Lean . Enterprise . Middleware > -- Dmitry Sotnikov VP of Cloud; WSO2, Inc.; http://wso2.com/ email: [email protected]; cell: +1.949.303.9653; Skype: DSotnikov Lean . Enterprise . Middleware <http://wso2.com/events/>
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
