hi, On Mon, Jan 10, 2011 at 11:29 AM, Srinath Perera <[email protected]> wrote: > If we need a change to a graduated artifact, what is the process, how > are we going to communicate that and update the repository?
you have to do a svn copy to get the source from graduated directory. * Do the changes * update the version according to the versioning strategy * do a svn move from the trunk to the graduated/ some_directory_structure / new version. --Pradeep. --Srinath > > On Mon, Jan 10, 2011 at 11:24 AM, Sameera Jayasoma <[email protected]> wrote: >> >> >> On Mon, Jan 10, 2011 at 11:12 AM, Afkham Azeez <[email protected]> wrote: >>> >>> +1. Please move the graduated code under this structure. It should have >>> versions, just like in the case of our branches. >> >> +1. This is part of the graduation process. If a component is graduated, >> source code will be moved to the graduated space. >> >> Sameera >>> >>> Azeez >>> >>> On Mon, Jan 10, 2011 at 11:05 AM, Pradeep Fernando <[email protected]> >>> wrote: >>>> >>>> Hi devs, >>>> >>>> During an off-line discussion with Afkham Azeez, we (me , Sameera) >>>> noted that, it is hard to locate the source of the artifacts that have >>>> being graduated during an older release. >>>> >>>> For an example during the last AS release Charith had to dig in to a >>>> old carbon release to get the source of the xfer component. (to fix a >>>> bug). We thought of maintaining a separate source structure for the >>>> graduated component under the name "graduated" . this is similar to >>>> the attic directory structure, but the only difference is that a >>>> developer may bring back the graduated component to fix a bug. (means >>>> we have to maintain versions). >>>> >>>> >>>> if you have any other views regarding this effort please reply to this >>>> mail thread. >>>> >>>> thanks, >>>> --Pradeep. >>>> _______________________________________________ >>>> Carbon-dev mailing list >>>> [email protected] >>>> https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >>> >>> >>> -- >>> Afkham Azeez >>> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com, >>> >>> Member; Apache Software Foundation; http://www.apache.org/ >>> email: [email protected] cell: +94 77 3320919 >>> blog: http://blog.afkham.org >>> twitter: http://twitter.com/afkham_azeez >>> linked-in: http://lk.linkedin.com/in/afkhamazeez >>> >>> Lean . Enterprise . Middleware >>> >>> _______________________________________________ >>> Carbon-dev mailing list >>> [email protected] >>> https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >> >> >> >> -- >> Sameera Jayasoma >> Technical Lead and Product Manager, WSO2 Carbon >> >> WSO2, Inc. (http://wso2.com) >> email: [email protected] >> blog: http://tech.jayasoma.org >> >> Lean . Enterprise . Middleware >> >> _______________________________________________ >> Carbon-dev mailing list >> [email protected] >> https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> > > > > -- > ============================ > Srinath Perera, Ph.D. > Senior Software Architect, WSO2 Inc. > Visiting Lecturer, University of Moratuwa > Member, Apache Software Foundation > Research Scientist, Lanka Software Foundation > Blog: http://srinathsview.blogspot.com/ > _______________________________________________ > Carbon-dev mailing list > [email protected] > https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- Pradeep Fernando Software Engineer WSO2 Inc; http://wso2.com/ blog: http://pradeepfernando.blogspot.com/ m: +94776603662 _______________________________________________ Carbon-dev mailing list [email protected] https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev
