Hmm, I am not against for shipping samples with product distribution.. But it is not a scalable solution anymore.. When platform story grows we are tend to reuse features the shipping all the sample within a product distribution is not scale..
IMHO, samples are used in development stages and installing svn or git in that case does not cause any concerns.. If we want to debug and verify the functionality then can't we simply copy the samples and tryout?.. Thanks, Mohan On Mon, Aug 1, 2016 at 5:00 PM, Gihan Anuruddha <[email protected]> wrote: > I see two downsides from above approach. > > 1. Users have to install svn or git in their machine (This is a small > issue, but unnecessary dependency). > 2. Sometimes when we are facing some issues, easiest way for us is, run > the sample and see things are working fine. Specially in a remote machine. > We lose that freedom. > > Above are minor problems. But bit inconvenient for end users. > > Regards, > Gihan > > On Mon, Aug 1, 2016 at 4:32 PM, Mohanadarshan Vivekanandalingam < > [email protected]> wrote: > >> >> >> On Mon, Aug 1, 2016 at 4:02 PM, Niranda Perera <[email protected]> wrote: >> >>> Hi all, >>> >>> At the moment we are maintaining samples of DAS, CEP and ML in their own >>> product repos. Since, DAS integrates both CEP and ML, we need to send these >>> samples with DAS. >>> >>> Currently we do so for ML samples, but the approach we are using is to >>> keep a local copy of the samples in the product-das repo. This approach is >>> rather problematic, because when there are changes in the original samples, >>> we would also have to reflect those changes manually in the product-das >>> copy. >>> >>> Is there a more consistent way to add samples? May be like creating a >>> separate samples feature? >>> >> >> IMO, best option is remove samples from product distribution and maintain >> in a common location (svn or git). In this case, whoever like try the >> samples can refer relevant locations.. >> >> This is also give us a freedom to add/update samples time to time >> without worrying about product releases.. >> >> Thanks, >> Mohan >> >> >>> >>> Would like to hear from you regarding this. >>> >>> Best >>> >>> -- >>> *Niranda Perera* >>> Software Engineer, WSO2 Inc. >>> Mobile: +94-71-554-8430 >>> Twitter: @n1r44 <https://twitter.com/N1R44> >>> https://pythagoreanscript.wordpress.com/ >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> *V. Mohanadarshan* >> *Associate Tech Lead,* >> *Data Technologies Team,* >> *WSO2, Inc. http://wso2.com <http://wso2.com> * >> *lean.enterprise.middleware.* >> >> email: [email protected] >> phone:(+94) 771117673 >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > W.G. Gihan Anuruddha > Senior Software Engineer | WSO2, Inc. > M: +94772272595 > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- *V. Mohanadarshan* *Associate Tech Lead,* *Data Technologies Team,* *WSO2, Inc. http://wso2.com <http://wso2.com> * *lean.enterprise.middleware.* email: [email protected] phone:(+94) 771117673
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
