Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [corona-dev] Weekly Development Conference Call: Tuesday, May 22 @ 10:00 AM EDT

Corona Development Conference Call: Tuesday, May 22, 2007 @ 10:00 AM EDT

 

Meeting Minutes

  • Please reply to the dev mailing list for any updates or corrections.

 

Attendees

  • Dennis O'Flynn
  • Jim Wright
  • Glenn Everitt
  • Edyta Kalka
  • Marcin Okraszewski
  • Piotr Jaworowski
  • Brian Roberts
  • Paul Styles

 

 

Minutes

 

News and Noteworthy

Marcin: Pawel is out this week and next.  He and his wife had their 2nd child this past week!

 

Glenn: Serena recently made some acquisitions and plan to do integrate into a solution using ALF.

 

Community Building

Dennis: The Europa webinar for Corona has been delayed from June 15 to July 11.

 

Europa

Dennis: Beginning with Europa M7, Declarative Services is no longer included in the Equinox distribution.  DS was included in M2, M3, M4, M5, and M6.  This has a negative impact on Corona because of its dependency upon DS.  Based upon an email from Jeff McAffer posted to cross-project-issues-dev mailing list, DS will not be approved to be released.

 

Paul: Will Corona work with Prosyst’s implementation of DS?

Dennis: Yes.  Because Corona is dependent upon the OSGI specification, not a specific vendor’s implementation

 

Paul: When will Prosyst’s DS be available?

Dennis: After Europa.  Actual timeframe is not known.  They are waiting for IP approval.  However, the IP process is focused on items for Europa and Prosyst’s DS implementation is not scheduled for Europa.

 

Glenn: Would it be possible for Corona to embedded DS for its internal use?

Dennis: I don’t know?  It need to be approved by Europa Release Review.

 

Glenn: There are still several IP requests outstanding for Corona.  These need to be approved for Corona to participate in Europa.

 

Marcin: We need to resolve the issue regarding the use of the ContextContainer model that has been committed to HEAD.  Currently, Corona’s RC build is based off of a Branch that uses the old ContextContainer model.

Jim: The HEAD is becoming more stable.  We should consider using this for the next RC build.

Glenn: Corona’s Europa release should be based off of the Branch.  However, it would be best to release Corona (regardless of Europa) with HEAD because of the improved ContextContainer model.  This way we would not have to support two code bases.

Glenn: As of this morning, you committed updates to ResourceDescriptors for container definitions.  This fixes some issues with our test container.

 

Glenn: To meet Europa release, we should stop work on the new ContextContainer model (HEAD), and focus on testing and bug fix of the Branch.

Marcin:  Seems like work that would be in vain because it would become obsolete when the HEAD is released.

Brian: You should focus work on the new model.

 

Release Engineering

Dennis: The release / build scheduled has been updated to be aligned with the Europa schedule.  The last two release / builds  are on a weekly (not bi-weekly) schedule.

 

Corona Frameworks

 

Server-Side Framework

 

Collaboration Framework

 

Exemplary Implementation (ProjectContainer)

 

 

Out-of-Box

Jim: With RC0, both the client and server need to be using the same version.  An M10 client will not work with the RC0 server.

 

Paul: Is it a viable option to have a Corona server pre-installed on Corona’s vserver for use by Europa users?

Dennis: Need to determine if network performance is due to our company’s internal network or issues with using a “virtual” server.

Glenn: Has anyone tried connecting to the vserver from outside work?  

All: No.

 

Dennis: The install of a Corona enabled client is impacted with the non-availability of DS.  It would have to be manually downloaded and installed by each user.

Glenn: This will have a negative impact on the out-of-box experience.

 

 

Open Issues

 

 

 


The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.

Back to the top