Hi Udara, We decided to use current AppM branch on ES for version bump up as you suggested. We need to do change the branch name to better reflect that it is related to AppM only and removing all version relevant parts in the branch name to avoid confusion.
This branch will be used for back-porting some ES 2.0 functionalities if need arises. we can tag the relevant points on this branch as and when a release made. Can we rename the branch "es-1.0.1-apm-reg" to "app-manager" ? Cheers, Ruwan On Wed, Jul 8, 2015 at 3:41 PM, Udara Rathnayake <[email protected]> wrote: > Hi Ruwan, > > On Wed, Jul 8, 2015 at 2:04 PM, Ruwan Yatawara <[email protected]> wrote: > >> Hi Udara, >> >> Yes, We would always have the release tag, but would it not be a bit >> confusing for someone who is not aware of this to basically go ahead and >> start development? >> > Yes, ideally we need to carry development in master and avoid this > confusion.But APPM depends on ES1.0, hence we have this separate branch. > > >> and since the branch name is going to be the same the ES feature version >> in both the already released APPM and the one that will be immediately >> released will be the same. This is very confusing don't you think? >> >> Hence.shall we go and straight away create a separate branch with the PR, >> as suggested by Ruwan as it would be much cleaner, going forward? >> > > I thought APPM will move with the latest ES model soon after 1.1(next > immediate) hence proposed above. > >> >> Thanks and Regards, >> >> Ruwan Yatawara >> >> Senior Software Engineer, >> WSO2 Inc. >> >> email : [email protected] >> mobile : +94 77 9110413 >> blog : http://ruwansrants.blogspot.com/ >> www: :http://wso2.com >> >> >> On Wed, Jul 8, 2015 at 12:21 PM, Ruwan Abeykoon <[email protected]> wrote: >> >>> Hi Udara, >>> >>> +1 : go with the existing branch, then tag new release. >>> >>> @Sumedha, @Dinusha please confirm. >>> >>> Cheers, >>> Ruwan >>> >>> On Wed, Jul 8, 2015 at 12:15 PM, Udara Rathnayake <[email protected]> >>> wrote: >>> >>>> 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 >>>>> >>>>> >>>> >>> >>> >>> -- >>> >>> *Ruwan Abeykoon* >>> *Architect,* >>> *WSO2, Inc. http://wso2.com <http://wso2.com/> * >>> *lean.enterprise.middleware.* >>> >>> email: [email protected] >>> phone:(+94) 777739736 >>> >> >> > -- *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
