+1
On Fri, Jan 3, 2014 at 11:29 AM, Eranda Sooriyabandara <[email protected]>wrote: > Hi Isuruwan, > Here with your scenario, there can be a issue if we encounter a bug in > registry or governance component where we need to fix in a product release > before we release the refactored components. > > In such a scenario we can follow the following steps > 1. Move the refactored code to a next version > 2. Copy the released component code to the next version > 3. Fix the bug in both refactored and the patch release components > > E.g : If we need to fix a bug in org.wso2.carbon.governance.api and we > fefactored the code in 4.2.2 where the released component version is 4.2.1, > then we need to follow the following steps > > Move the refactored code from 4.2.2 to 4.2.3 > Copy 4.2.1 code to 4.2.2 > Fix the bug in 4.2.2 and 4.2.3 > > WDYT? > > thanks > Eranda > > > On Thu, Jan 2, 2014 at 10:42 PM, Isuruwan Herath <[email protected]>wrote: > >> Hi, >> >> If we are proceeding with new component versions, in the case of common >> components used by ongoing releases: should a new version be created anyway >> and proceed and merge later once the release is done? >> >> >> On Thu, Jan 2, 2014 at 9:51 PM, Selvaratnam Uthaiyashankar < >> [email protected]> wrote: >> >>> >>> >>> >>> On Thu, Jan 2, 2014 at 9:51 PM, Selvaratnam Uthaiyashankar < >>> [email protected]> wrote: >>> >>>> >>>> >>>> >>>> On Thu, Jan 2, 2014 at 9:32 PM, Senaka Fernando <[email protected]>wrote: >>>> >>>>> Hi Shankar, >>>>> >>>>> Yes that's what we do right now. But, wouldn't this complicate >>>>> parallel development work, especially if two or more products start >>>>> changing common components in separate scratch areas? (ex:- we had a bad >>>>> experience sometime back when the IS changes done in scratch were merged >>>>> into release branch). >>>>> >>>>> IMHO, may be we don't need to have a chunk08 (that's just a grouping >>>>> for the build), but we do need to use the same branch to commit changes. >>>>> Of >>>>> course with new version numbers if the components have been releases >>>>> already. >>>>> >>>>> Based on what we (Azeez/Sameera/SameeraP/myself) discussed in the >>>>> morning (correct me if I'm wrong), unless we keep committing to the >>>>> branch, >>>>> we loose patches etc that were provided for a previous release. >>>>> >>>> >>>> >>>> Yes, in that case, you can create a new component version and commit >>>> there, but not create the chunk08 folders. How are we going to build those >>>> components is an issue. one option is to create "chuck-future" >>>> >>> >>> *chunk-future >>> >>> >>>> or some folder and have the build configured there and move the >>>> components from there to correct chunk when we decide the chunk. WDYT? >>>> >>>> Regards, >>>> Shankar >>>> >>>> >>>> >>>>> >>>>> Thanks, >>>>> Senaka. >>>>> >>>>> >>>>> On Thu, Jan 2, 2014 at 9:22 PM, Selvaratnam Uthaiyashankar < >>>>> [email protected]> wrote: >>>>> >>>>>> >>>>>> >>>>>> >>>>>> On Thu, Jan 2, 2014 at 8:58 PM, Eranda Sooriyabandara < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> Hi Nuwan, >>>>>>> >>>>>>> Looping carbon-dev >>>>>>> >>>>>>> >>>>>>>>> G-Reg team will be starting to work on $subject. Team members who >>>>>>>>> are not allocated to support and are not working on C5 registry >>>>>>>>> re-factoring will start work on this. As discussed with Azeez, we will >>>>>>>>> create chunk-08 for commits. Following are the planned areas which >>>>>>>>> will be >>>>>>>>> >>>>>>>> focused: >>>>>>>>> >>>>>>>> >>>>>>>> Why do you have to create chunk08? It is wrong to create chunk08 >>>>>>>> until chunk07 is released. >>>>>>>> >>>>>>> >>>>>>> This is not a short term plan and will not cater any feature >>>>>>> improvements or new features, plus this may contain some changes to the >>>>>>> APIs. So we thought of having these refactored components separately >>>>>>> until >>>>>>> they are done so that others can use there after. >>>>>>> >>>>>> >>>>>> But, this is a wrong process to create chunk08 before chunk 07 is >>>>>> released. If you want to keep it separate, may be you can use scratch >>>>>> area. >>>>>> >>>>>> Regards, >>>>>> Shankar >>>>>> >>>>>> >>>>>> >>>>>>> >>>>>>> thanks >>>>>>> Eranda >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> S.Uthaiyashankar >>>>>> VP Engineering >>>>>> WSO2 Inc. >>>>>> http://wso2.com/ - "lean . enterprise . middleware" >>>>>> >>>>>> Phone: +94 714897591 >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> *Senaka Fernando* >>>>> Senior Technical Lead; WSO2 Inc.; http://wso2.com >>>>> >>>>> >>>>> >>>>> * Member; Apache Software Foundation; http://apache.org >>>>> <http://apache.org>E-mail: senaka AT wso2.com <http://wso2.com>**P: >>>>> +1 408 754 7388 <%2B1%20408%20754%207388>; ext: 51736*; >>>>> >>>>> >>>>> *M: +94 77 322 1818 <%2B94%2077%20322%201818> Linked-In: >>>>> http://linkedin.com/in/senakafernando >>>>> <http://linkedin.com/in/senakafernando>*Lean . Enterprise . Middleware >>>>> >>>> >>>> >>>> >>>> -- >>>> S.Uthaiyashankar >>>> VP Engineering >>>> WSO2 Inc. >>>> http://wso2.com/ - "lean . enterprise . middleware" >>>> >>>> Phone: +94 714897591 >>>> >>> >>> >>> >>> -- >>> S.Uthaiyashankar >>> VP Engineering >>> WSO2 Inc. >>> http://wso2.com/ - "lean . enterprise . middleware" >>> >>> Phone: +94 714897591 >>> >> >> >> >> -- >> Isuruwan Herath >> Technical Lead >> >> Contact: +94 776 273 296 >> > > > > -- > > *Eranda Sooriyabandara*Senior Software Engineer; > Integration Technologies Team; > WSO2 Inc.; http://wso2.com > Lean . Enterprise . Middleware > > E-mail: eranda AT wso2.com > Mobile: +94 716 472 816 > Linked-In: http://www.linkedin.com/in/erandasooriyabandara > Blog: http://emsooriyabandara.blogspot.com/ > > > > > -- Isuruwan Herath Technical Lead Contact: +94 776 273 296
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
