Hi Jasintha,
Please find my comments inline.
On Tue, Sep 15, 2015 at 8:48 AM, Jasintha Dasanayake
wrote:
> Hi Kavith
>
> Yes , we should not keep any mapping in DevS side , once this change is
> done in AF this should be reflected into DevS so there shouldn't be
> anything to change in DevS si
Hi Kavith
Yes , we should not keep any mapping in DevS side , once this change is
done in AF this should be reflected into DevS so there shouldn't be
anything to change in DevS side right ?
Thanks and Regards
/Jasintha
On Mon, Sep 14, 2015 at 12:39 PM, Manjula Rathnayake
wrote:
> Hi Kavith,
Hi Kavith,
IMO, we should not store any mapping in DevStuido level. This needs to be
fixed in AF REST API level as well as in backends of AF and it require
considerable time to test and do any data migration if required too.
Since this is not a blocker, we will fix this in M6 milestone and you can
I guess we use trunk because we started this with svn and then moved on to
git. +1 for renaming. @Manjula WDYT?
Thanks & Regards
Danushka Fernando
Senior Software Engineer
WSO2 inc. http://wso2.com/
Mobile : +94716332729
On Fri, Sep 11, 2015 at 5:00 PM, Kavith Lokuhewage wrote:
> Hi,
>
> This i
Hi,
This is regarding $subject raised in [1] and [2].
Currently the default version of an application is given the version
"trunk" (which corresponds to "master" branch of the git repo). When
checking out a version, DevStudio checks whether the user is checking out
the version "trunk" and if so,
