Since we have the release tag you can go with the same branch(but having version 1.0.1 in the branch name is bit confusing) Until APPM can point to the latest ES release version (with the extension model) , shall we go with the existing branch?
On Wed, Jul 8, 2015 at 11:53 AM, Ruwan Abeykoon <[email protected]> wrote: > Hi ES/AppM teams, > We need to change few pom files and couple of classes in ES (branch > es-1.0.1-apm-reg) in order to get AppM upgraded to C 4.4.0 retaining ES > 1.0.0. > > > What is the best option; > 1. create a new branch es-1.1.0-appm-reg and create a PR with new version > 2. create a PR on top of es-1.0.1-apm-reg, so that the branch will bump up > the version. > > Cheers, > Ruwan > > > -- > > *Ruwan Abeykoon* > *Architect,* > *WSO2, Inc. http://wso2.com <http://wso2.com/> * > *lean.enterprise.middleware.* > > email: [email protected] > phone:(+94) 777739736 > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
