Corona Development Conference Call: Tuesday, Nov 21, 2006 @ 10:00 AM EST
Meeting
Minutes
- Please
reply to the dev mailing list for any updates or corrections.
Attendees
- Dennis
O'Flynn
- Glenn
Everitt
- Jim
Wright
- Pawel
Kaczmarek
- Piotr
Jaworowski
- Marcin
Okraszewski
- Edyta
Kalka
- Paul
Styles
- Brian
Roberts
News
Minutes
- Corona
1.0.0M5
- Status…
- Distribution
post to download area
- Ant
setup script tested by development team.
- Still being validated by “management”
- Buckminster
Demo
- We
plan to demo M5 to Buckminster during the week of Nov 27 – Dec 1.
- Problems
with Proxies
- Dennis
posted problem description to corona-dev
- M5
vserver is not usable from behind firewall
- Corona
1.0.0M7
- Planning
has begun. Initial scope is defined on wiki.
- ECF
v1.0 will require significant changes for adoption
- SDO
- Should
Corona
adopt a consistent SDO model not only for the Context Container
definition, but for all of the Repository Descriptors as well? Should
this also extend to the objects returned from each “repository”.
- Corona, and/or
applications adopting Corona,
would need to create Repository Adaptors that return SDO
- Debate of the issues to be held in corona-dev@xxxxxxxxxxx
- FYI
- Apache Tuscany (SCA) has its own SDO that is not compatible with the
Eclipse SDO.
- Remaining
Schedule
- Aligning
initial release with Europa (Jun 2007) is a higher priority than
providing a release at EclipseCon (Mar 2007).
- Planning
a release 1.0 for Jun 2007 allows for more preparation for “Release
Review”
Miscellaneous
Action Item
- [Compuware
committers] Development team (within Compuware) to begin using M5 within
their development environment.
- [Brian
Roberts] will coordinate the creation of a Flash demo of Corona
- [Glenn/Edyta]
Provide an overview Jackrabbit to the team
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.
|
