Jump to: navigation, search

Difference between revisions of "Nebula Actions"

(New page: == Nighlty builds == We are ready to provide nighlty build for every widget. We just need that every committer creates a releng plugin for his widgets. This can be done very quickly (say 1...)
 
 
(3 intermediate revisions by one other user not shown)
Line 1: Line 1:
== Nighlty builds ==
 
We are ready to provide nighlty build for every widget. We just need that every committer creates a releng plugin for his widgets. This can be done very quickly (say 10 minutes). Read instructions here [[http://wiki.eclipse.org/Nebula_Releng]]
 
 
Question : the zip files contains "-incubation". Is it enough or do we need to change something else ?
 
 
 
 
== Project plan ==
 
== Project plan ==
 
We have to provide a project plan. Aside from release planning, each widget have to provide links to committed, proposed and deferred bugzilla items. In order to do this, you need to :  
 
We have to provide a project plan. Aside from release planning, each widget have to provide links to committed, proposed and deferred bugzilla items. In order to do this, you need to :  
Line 11: Line 6:
 
- Add keyword 'plan' to your major bugzilla items and update priorities. For Gallery : P1 = committed, P2/P3 : proposed, P4/P5 : deferred
 
- Add keyword 'plan' to your major bugzilla items and update priorities. For Gallery : P1 = committed, P2/P3 : proposed, P4/P5 : deferred
  
This can be done in 30 minutes.
+
To edit the project plan, checkout the Nebula website from cvs and edit
 +
 
 +
  project-info/nebula-project-plan.xml
 +
 
 +
This can be done approx. in 30 minutes.
 +
 
 +
Helpful links :
 +
 
 +
- Project Plan Documentation :  [http://wiki.eclipse.org/Development_Resources/Project_Plan]
 +
 
 +
- Current Nebula project plan : [http://www.eclipse.org/projects/project-plan.php?projectid=technology.nebula]
 +
 
 +
- Current Nebula project plan as XML: [http://www.eclipse.org/projects/project-plan.php?projectid=technology.nebula&raw=1]
  
 
== IP Log ==
 
== IP Log ==
Line 17: Line 24:
 
We have to provide an IP log. It automatically generated from bugs attachements having the flag iplog+.  
 
We have to provide an IP log. It automatically generated from bugs attachements having the flag iplog+.  
 
We just have to dig bugzilla for patch which were applied to the code and add this flag.
 
We just have to dig bugzilla for patch which were applied to the code and add this flag.
 +
 +
See IP log: [http://www.eclipse.org/projects/ip_log.php?projectid=technology.nebula]
  
  

Latest revision as of 03:20, 16 December 2010

Project plan

We have to provide a project plan. Aside from release planning, each widget have to provide links to committed, proposed and deferred bugzilla items. In order to do this, you need to :

- Add 3 bugzilla search urls to nebula-project-plan.xml

- Add keyword 'plan' to your major bugzilla items and update priorities. For Gallery : P1 = committed, P2/P3 : proposed, P4/P5 : deferred

To edit the project plan, checkout the Nebula website from cvs and edit

 project-info/nebula-project-plan.xml

This can be done approx. in 30 minutes.

Helpful links :

- Project Plan Documentation : [1]

- Current Nebula project plan : [2]

- Current Nebula project plan as XML: [3]

IP Log

We have to provide an IP log. It automatically generated from bugs attachements having the flag iplog+. We just have to dig bugzilla for patch which were applied to the code and add this flag.

See IP log: [4]


Examples

We are very close to provide an offical Webstart example of Nebula widgets, but only 4 widgets currently have their example tab. It is very easy to turn a snippet to an example tab, but if you have some more free time, show your widget at its best.

A bug have been logged for each missing widget. (include bug # here)


Ohloh (Bonus)

The CVS history of Nebula is analysed by ohloh : http://www.ohloh.net/p/5650. If each committer adds its name, photo and location, this would provide some nice informations and stats. :)