On 7 Feb 2011, at 15:42, Zhu, Peter J wrote: > Hi > >> -----Original Message----- >> From: Anas Nashif [mailto:[email protected]] >> Sent: Monday, February 07, 2011 2:23 AM >> To: Zhu, Peter J >> Cc: [email protected] list) >> Subject: Re: [meego-packaging] Changes on how patterns are applied and >> deployed >> >> >> On 6 Feb 2011, at 12:57, Zhu, Peter J wrote: >> >>> Hi >>>> -----Original Message----- >>>> From: [email protected] >>>> [mailto:[email protected]] On Behalf Of Anas Nashif >>>> Sent: Friday, February 04, 2011 9:40 PM >>>> To: [email protected] list) >>>> Subject: [meego-packaging] Changes on how patterns are applied and >> deployed >>>> >>>> Hi, >>>> >>>> Up until now, patterns were maintained in a git tree and OBS (as meta data >> for >>>> projects). Changes have been committed to OBS using a script that applies >> the >>>> changes in the git tree to OBS. This action was done in the background >> without >>>> any notifications (unless you monitor the git tree). >>>> In addition to that, we used the same patterns for Trunk and Trunk:Testing >>>> which caused lots of issues when certain new packages have been in >>>> Trunk:Testing and still did not make it to Trunk. >>>> >>>> The patterns will still be maintained in GIT, however, we now package them >>>> and do not maintain them in OBS anymore (for now they are still available >>>> as >>>> metadata in OBS, but we do not use them in new repos), instead, whenever >> a >>>> new repo is created we extract the patterns from the package >> package-groups >>>> and apply them on the repo. >>> How does Trunk repo know what changes are T:T only and exclude them >> then? >> >> >> changes are tested in Trunk:Testing and pushed to Trunk when verified, just >> like >> any package. >> > Since we have just one branch of package-groups, how doesn't Trunk repo pick > up changes for T:T only?
Because changes are packaged and submitted to Trunk:Testing, verified and when all OK, pushed to Trunk, so Trunk does not pick changes unless the package has been moved from Trunk:Testing to Trunk. Anas > > Peter >>> >>> Could we have a T:T branch for package-groups? >> >> >> That is useless and will just complicate things, since the time difference >> is very >> small between Trunk:Testing and Trunk. Any change has to be tested in >> Trunk:Testing first and then pushed to Trunk. >> >> >> Anas >> >>> >>> Peter >>>> >>>> Any change to the patterns have to be packaged and submitted to >>>> Trunk:Testing first (first add to git as a direct commit or a merge >>>> request), >> this >>>> will give everyone the possibility to review the changes on the >> meego-commits >>>> mailing list. Once it has been verified on Trunk:Testing it will be pushed >>>> to >> Trunk >>>> with related added packages if they do not exist in Trunk already. >>>> >>> >>>> Note: The same would also apply to kickstart files, that is something we >>>> are >>>> working on right now. >>>> >>>> >>>> Regards, >>>> Anas >>>> _______________________________________________ >>>> MeeGo-packaging mailing list >>>> [email protected] >>>> http://lists.meego.com/listinfo/meego-packaging > _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
