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.
Gemini/Meetings/Minutes Sept 11 2012
< Gemini | Meetings
Revision as of 10:37, 11 September 2012 by Michael.keith.oracle.com (Talk | contribs) (New page: == Gemini Meeting - Tues Sept 11, 2012 == Attendees: Glyn, Lazar, Violeta, Chris, Juergen, Mike # Actions from Last Meeting #* Mike - create a zipfile for the JPA updates repo - done #* ...)
Gemini Meeting - Tues Sept 11, 2012
Attendees: Glyn, Lazar, Violeta, Chris, Juergen, Mike
- Actions from Last Meeting
- Mike - create a zipfile for the JPA updates repo - done
- All - Add releases to Maven repo - Pending
- Subproject Updates
- Management
- Will make a 2.0 milestone available this week
- Web
- 2.2.0 Milestone 1 since last meeting
- Looking at support for Java 7 (needed by Tomcat 7.0.30)
- DBAccess
- Support for H2 will go into the next milestone
- Will sync with Gemini JPA to release later this month
- JPA
- Put out a 1.1.0 Milestone 2 since last meeting
- Finished the documentation for the new features
- Still need to get the docuware done and schedule a release review
- Blueprint
- Released 1.01, but a bug was found while running within Virgo
- Fixed the bug and respun 1.02
- Migrated web site to Git, but does not seem to be updating
- Entered bug 389149 to track the problem (in case others want to monitor progress before migrating)
- Management
- Kepler
- Update on PMC Juno retrospective discussion (see here for RT PMC meeting minutes)
- Glyn to investigate whether LTS will really need to have release train membership as a pre-req
- If still there then Web, Blueprint and Management may all end up having to join the release train if Virgo needs to be on
- JPA will likely also have to join if Gyrex continues to use it and be on the train
- Misc
- Shared Maven repo
- Mike reported that he just copied over the relevant local Maven repo files and regenerated the hash files for remote access
- Mike's approach is probably not very scalable for projects with lots of JARs
- Shared Maven repo