A few qns/comments about step 1,
1) when is the right timing to modify all .ks files to point to the new UX
repo? It should be synced among all release engineers.
2) Trunk:UX:testing is new. Will BOSS automatically handle the creation of TT
images using ux:testing repo?
3) Since there will be multiple Trunk:UX maintainers, what's your suggestion
about the trunk:ux:testing acceptance and trunk:ux promotion ownership?
4) will Trunk:{Handset|Netbook|IVI}/* be removed immediately after the moving?
- Bingwei
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Nashif, Anas
Sent: Saturday, January 15, 2011 11:48 PM
To: [email protected]
Subject: [meego-packaging] Please READ: Build System project restructuring
announcement
Hi,
As a measure of cleanup and to better reflect the MeeGo architecture in the
build system, we are planning to redo the project structure.
The restructuring would happen in three steps, starting with the least
intrusive one:
1) Step 1: Start 2011-01-20
- Create Trunk:UX and Trunk:UX:Testing
- Move Trunk:{Handset|Netbook|IVI}/* to Trunk:UX
- Make Trunk:Testing a link to Trunk
- Initial package cleanup of new Trunk:UX project.
Result:
- Trunk
- Trunk:UX
- Trunk:non-oss
With corresponding *:Testing projects.
How will this affect you?
* This step will produce one single repository for UX and application on top
of Core instead of the many we have right now.
* Image configurations will need to be changed and would point to at least 3
repos: core, ux and non-oss (if needed)
* If you have been developing against one of the Trunk sub-projects
(Netbook,Handset, IVI), then you will need to re-branch or relink to the new
Trunk:UX project
_______________________________________________
MeeGo-packaging mailing list
[email protected]
http://lists.meego.com/listinfo/meego-packaging
