Hi all, So what is the final conclusion ? Is it the branch we going to do current active development or is it both branch and trunk ? As every product have quite a few other dependent features, isn't it better we all agree to one thing.
Assuming we go with the branch, AFAIK there are still diffs between branch and trunk and thus the latest greg pack generated from branch (for regression testing) became useless as there are still some code left(i.e in kernel) which has not went to the branch. Thanks On Tue, Jul 24, 2012 at 9:11 PM, Amila Suriarachchi <[email protected]> wrote: > > > On Tue, Jul 24, 2012 at 8:55 PM, Ajith Vitharana <[email protected]> wrote: > >> >> >> On Tue, Jul 24, 2012 at 5:56 PM, Amila Suriarachchi <[email protected]>wrote: >> >>> >>> >>> On Tue, Jul 24, 2012 at 5:51 PM, Ajith Vitharana <[email protected]>wrote: >>> >>>> >>>> >>>> On Tue, Jul 24, 2012 at 5:13 PM, Amila Suriarachchi <[email protected]>wrote: >>>> >>>>> >>>>> >>>>> On Tue, Jul 24, 2012 at 4:59 PM, Pradeep Fernando <[email protected]>wrote: >>>>> >>>>>> >>>>>> >>>>>> On Tue, Jul 24, 2012 at 3:52 PM, Amila Suriarachchi >>>>>> <[email protected]>wrote: >>>>>> >>>>>>> When cutting the branch can we avoid the components which are not >>>>>>> released with the current set of products. >>>>>>> >>>>>>> For an example CEP component can be kept only in trunk and we will >>>>>>> branch it when we ready to release the CEP. Since each and every >>>>>>> component >>>>>>> has branches this will be an viable option. >>>>>>> >>>>>>> >>>>>> >>>>>> No this is not possible. We have already created the branch. On the >>>>>> other hand, there is no such thing as releasing from the trunk. So why >>>>>> don't you do active development in the branch itself. >>>>>> >>>>> >>>>> As you know still there is no date on release on other products. So >>>>> working on both trunk and branch for those products now on not really >>>>> efficient. So we can work on trunk utill near the release date and do the >>>>> branch. >>>>> >>>> >>>> --1. We have already merged G-Reg branch with trunk and committing our >>>> fixes to trunk and branch.(based on discussion in "[Dev] Carbon 4 >>>> Orbit/Kernel/Platform Branching") . And also we have already started >>>> releasing milestone packs based on the branch. Therefore every one should >>>> commit to branch. Because we can't do the same thing again. >>>> >>> >>> why you need to do the same thing again? you can keep on doing what you >>> have been doing. >>> >>> I am not saying every one should work on trunk. >>> >> >> Hi Amila, >> >> We can't build and release reliable pack as milestone build >> without properly merging rest of the kernel and platform(trunk) with >> branch. Therefore it is better to consider the branch as the primary >> location at the release time. Because we have a chance to merge the trunk >> from branch at the end of the release. >> > > if you want to continue on the branch with GReg components and merge them > with the branch you can do that. > > Why you want CEP and other also to do the same? The thing is those > products won't release with current release plan. > > However generally correct approach would be to working on the trunk and > merge the required changes to branch. This way we and keep trunk stable as > well. > > thanks, > Amila. > > >> >> Thanks >> Ajith >> >>> >>> thanks, >>> Amila. >>> >>>> >>>> Thanks >>>> Ajithn >>>> >>>> >>>>> thanks, >>>>> Amila. >>>>> >>>>>> >>>>>> >>>>>> --pradeep >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> *Amila Suriarachchi* >>>>> >>>>> Software Architect >>>>> WSO2 Inc. ; http://wso2.com >>>>> lean . enterprise . middleware >>>>> >>>>> phone : +94 71 3082805 >>>>> >>>>> >>>>> _______________________________________________ >>>>> Dev mailing list >>>>> [email protected] >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> Ajith Vitharana. >>>> WSO2 Inc. - http://wso2.org >>>> Email : [email protected] >>>> Mobile : +94714631794 >>>> >>>> >>>> >>> >>> >>> -- >>> *Amila Suriarachchi* >>> >>> Software Architect >>> WSO2 Inc. ; http://wso2.com >>> lean . enterprise . middleware >>> >>> phone : +94 71 3082805 >>> >>> >> >> >> -- >> Ajith Vitharana. >> WSO2 Inc. - http://wso2.org >> Email : [email protected] >> Mobile : +94714631794 >> >> >> > > > -- > *Amila Suriarachchi* > > Software Architect > WSO2 Inc. ; http://wso2.com > lean . enterprise . middleware > > phone : +94 71 3082805 > > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Subash Chaturanga Software Engineer WSO2 Inc. http://wso2.com email - [email protected] phone - 077 2225922
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
