Meego Wiki
Views

Release Engineering/New Package Checklist

From MeeGo wiki
(Difference between revisions)
Jump to: navigation, search
(→New package checklist)
(→New package checklist)
Line 22: Line 22:
==== Step 3: It must be with a FEA# ====
==== Step 3: It must be with a FEA# ====
-
Make sure this new package is with a feature. If  
+
Make sure this new package is with a feature. If there is no FEA# for the package, file one by yourself and get it approved by Program Manager
==== Step 3: Submit to correct target project ====
==== Step 3: Submit to correct target project ====
 +
 +
Depends on what this new package for and desire of copyright owner for that package, you might choose to submit different project
 +
 +
* Trunk:Testing which is staging project for Trunk for all those CORE(base + middleware) packages
 +
* Trunk:Vertical/Trunk:UX which is for those UX or application packages
 +
*
==== Step 4: Claim owner ====
==== Step 4: Claim owner ====

Revision as of 16:26, 25 January 2011

Contents

New package checklist

This a checklist which developers have to follow to submit a new package to MeeGo OBS of http://build.meego.com. This checklist talks about only specical parts for new package, for other commen practise required to submit code to MeeGo, please follow Submission Checklist

Following this checklist will ensure smooth submission and acceptance of NEW package.

Step 1: Agreed upon by copyright owner

Please make sure copyright owner of this new package agree putting it in public MeeGo OBS of http://build.meego.com. Especially if it's owned by a company, we need to be more careful.

  • For package owned by Intel, please make sure it passes open source PDT. Nokia has similar process inside.
  • If this package is from community
    • Talks to maintainer via project mailing list to ask for permission
    • If first approach is unavailable, please make sure it is in at least two other linux distributions

Step 2: Appropriate license

Please make sure appropriate license is attached to this new package. Specially MeeGo doesn't allow a package of GPLV3 into default build of non-netbook image. So make sure it doesn't need to be installed by default if it's GPLV3. Otherwise, if this new package is GPLV3 and/or has dependency of another GPLV3 package, you either stop here or you could do following to move further

  • Remove GPLv3 parts or parts requires another GPLV3 package OR
  • Rewrite GPLv3 parts by yourself so that this package doens't need to be GPLV3 OR
  • Revert back to a non-GPLV3 version

Step 3: It must be with a FEA#

Make sure this new package is with a feature. If there is no FEA# for the package, file one by yourself and get it approved by Program Manager

Step 3: Submit to correct target project

Depends on what this new package for and desire of copyright owner for that package, you might choose to submit different project

  • Trunk:Testing which is staging project for Trunk for all those CORE(base + middleware) packages
  • Trunk:Vertical/Trunk:UX which is for those UX or application packages

Step 4: Claim owner

Retrieved from "http://wiki.meego.com/Release_Engineering/New_Package_Checklist"
Personal tools