Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Orbit Minutes 070626"

Line 15: Line 15:
  
 
===IP Log info===
 
===IP Log info===
An IP Log is now generated with each build and is available from the download page. The file is far from complete, please update with info for the bundles that you own.  
+
An IP Log is now generated with each build and is available from the download page.  
 +
* The file is far from complete, please update with info for the bundles that you own.  
  
 
===Tests===
 
===Tests===
Line 22: Line 23:
 
* people need to change manifest casing
 
* people need to change manifest casing
 
* <font color="red">Action: DJ to enter bug against PDE to validate this is casing</font>
 
* <font color="red">Action: DJ to enter bug against PDE to validate this is casing</font>
* <font color="red">Action: DJ to gather bundles which are failing and will send note to mailing list. </font> We need to see if these are tested on Linux.
+
* <font color="red">Action: DJ to gather bundles which are failing and will send note to mailing list. </font>
 +
* We need to see if these are tested on Linux.
  
  
Line 42: Line 44:
  
 
===Signing Bundles===
 
===Signing Bundles===
 +
There are some problems with signed bundles because not all teams sign. (and Orbit doesn't)
 
* e.g. platform signs but wtp doesn't sign - same bundle, same qualifier
 
* e.g. platform signs but wtp doesn't sign - same bundle, same qualifier
 
* signing is not a requirement for Europa
 
* signing is not a requirement for Europa
Line 50: Line 53:
  
 
===R-builds===
 
===R-builds===
 +
Discussions surrounding Orbit R-Builds.
 
* when is the next r-build?
 
* when is the next r-build?
 
* how do we plan for this?
 
* how do we plan for this?
Line 58: Line 62:
 
* create new map files? had because its based on what people consume
 
* create new map files? had because its based on what people consume
 
* how about new features? set1 is for europa, something new for maintenance, etc.
 
* how about new features? set1 is for europa, something new for maintenance, etc.
 
+
* thought from Pascal: have the build produce multiple map files, one for each consumer based on the info in the ip log file
===Map files===
+
* have the build produce multiple map files, one for each consumer based on the info in the ip log file
+
  
 
==Next Meeting==
 
==Next Meeting==
* TBD
+
[http://timeanddate.com/worldclock/fixedtime.html?month=07&day=24&year=2007&hour=10&min=0&sec=0&p1=188 July 24, 2007 at 1000 EDT], Agenda: [[Orbit Minutes 070626]]
<!--
+
[http://timeanddate.com/worldclock/fixedtime.html?month=06&day=26&year=2007&hour=10&min=0&sec=0&p1=188 June 26, 2007 at 1000 EDT], Agenda: [[Orbit Minutes 070626]]
+
-->
+
  
 
[[Category:Orbit]]
 
[[Category:Orbit]]
 
[[Category:Orbit/Meeting]]
 
[[Category:Orbit/Meeting]]
 
[[Category:Meeting]]
 
[[Category:Meeting]]

Revision as of 11:07, 26 June 2007

Attendees

  • Christian Damus
  • Joel Cayne
  • Jeff McAffer
  • Pascal Rapicault
  • DJ Houghton
  • Chris Aniszczyk
  • David Williams

Discussion

IP Log info

An IP Log is now generated with each build and is available from the download page.

  • The file is far from complete, please update with info for the bundles that you own.

Tests

We have also added a basic test suite which verifies the layout of bundles.

  • some tests are currently fail because their manifest files aren't the right casing
  • people need to change manifest casing
  • Action: DJ to enter bug against PDE to validate this is casing
  • Action: DJ to gather bundles which are failing and will send note to mailing list.
  • We need to see if these are tested on Linux.


New Bundles

Now that we have declared a "recommended" build, is it ok to start releasing new bundles to Orbit?

  • remove for this week
  • add nightly builds? requires separate streams
  • R-builds are really a packaging problem?
  • build it from a status file?
  • Action: Chris to remove 2 new bundles from feature/map file until next week.

Conf Calls

The Eclipse Foundation has a new infrastructure for conference calls. We should start using it for Orbit calls.

  • Action: Jeff to co-ordinate and send note with new info.

Bundle downloads

Do we want to try and make the GET URLs generated by Orbit be build-independent? That is, not have the build id in it so consumers don't always have to update their map files if there is a new Orbit build and their bundle didn't change?

  • Action: DJ to write wiki describing problems.

Signing Bundles

There are some problems with signed bundles because not all teams sign. (and Orbit doesn't)

  • e.g. platform signs but wtp doesn't sign - same bundle, same qualifier
  • signing is not a requirement for Europa
  • orbit doesn't sign but always said we should
  • probably a couple days or a weeks worth of work to modify build scripts
  • Action: David to send a note to cross-project warning people of potential problems.
  • only happens when you have people unzipping on top of a signed version

R-builds

Discussions surrounding Orbit R-Builds.

  • when is the next r-build?
  • how do we plan for this?
  • same as regular project?
  • branch releng project to europa_maintenance
  • need to tag the map files for each build
  • do we really need branches?
  • create new map files? had because its based on what people consume
  • how about new features? set1 is for europa, something new for maintenance, etc.
  • thought from Pascal: have the build produce multiple map files, one for each consumer based on the info in the ip log file

Next Meeting

July 24, 2007 at 1000 EDT, Agenda: Orbit Minutes 070626

Back to the top