Gemini/Meetings/Minutes Nov 20 2012

Gemini Meeting - Tues Nov 20, 2012

Attendees: Juergen, Lazar, Violeta, Glyn, Chris, Mike

1. Actions from Last Meeting
   • All - Add releases to Maven repo
     • Have all been added except for DBAccess and Blueprint
     • Blueprint will add for the next release
     • Web will rename group id to be consistent with other projects
2. Subproject Updates
   • Gemini Naming
     • Build notices just received due to problems with Hudson build
       • Action: Violeta - look into cause of build problems
   • Gemini Web
     • Making another milestone available this week
     • Planning for an end of Dec release
     • Action: Violeta - respond to forum post
   • Gemini Management
     • Waiting for Virgo before releasing 2.0 stream
     • Have made a couple of small releases to 1.0 stream
   • Gemini JPA
     • Release review occurred and 1.1 released
     • Starting on 1.2 - a couple of major features that people have requested
       • Hope to release by June '13
     • Issue with Web integration - Violeta and Mike to discuss in bug report
   • Gemini DBAccess
     • Migrated web site to Git
     • Problems with Hudson build - OOM exception
     • Still working on adding DBAccess artifacts to maven repo
   • Gemini Blueprint
     • Looking at bug backlog
       • Some require significant changes and don't want to put those in 1.0 stream
       • Started a 2.0 stream to fix them
     • Plan for a release by the end of March
3. Web Site Migration
   • All projects have been migrated
   • Problem of subfolders in parent git repo being the same as the subproject repo names
     • Subproject repos can get overwritten/masked
     • Touching the subproject repo seems to solve the problem
4. Other
   • GitHub pull requests
     • Recently came out that there was a pull request on GitHub for Gemini code
     • Wayne got the notification and enabled Gemini committers to be able to be notified/approve pull requests
     • Discussion that allowing pulls from GitHub is not straightforward
       • Need to pull into local repo first to change committer name to actual Eclipse committer
       • If code is pulled to github directly then the code will end up being duplicated on the mirror
     • Some people may decide to just not accept pull requests and direct contributors to the bug reporter instead