Meego Wiki
Views

Release Engineering/New Package Checklist

From MeeGo wiki
(Difference between revisions)
Jump to: navigation, search
(→New package checklist)
Line 5: Line 5:
Following this checklist will ensure smooth submission and acceptance of NEW package.  
Following this checklist will ensure smooth submission and acceptance of NEW package.  
-
==== Step 1: agreed upon by copyright owner ====
+
==== 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.  
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.
* 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 ====
==== Step 2: Appropriate license ====
-
* I have tested my changes on all relevant hardware.  All code must be solid and tested before submission.
+
Please make sure appropriate license is attached to this new package. Specially MeeGo doesn't expect a package of GPLV3 into default
-
* If I make a change to a big package with a lot of dependents like the kernel, qt, etc. I will make sure this does not break any MeeGo verticals.
+
-
* If my change will cause regressions, I must communicate with Release Engineering on what the expected regressions will be, and the ETA of when this can be rectified.
+
-
==== Step 3: Changelog must refer to a feature # or bug # ====
+
==== Step 3: It must be with a FEA# ====
 +
 
 +
==== Step 3: Submit to correct target project ====
 +
 
 +
==== Step 4: Claim owner ====

Revision as of 15:57, 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 expect a package of GPLV3 into default

Step 3: It must be with a FEA#

Step 3: Submit to correct target project

Step 4: Claim owner

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