[mapguide-internals] MapGuide Open Source 2.1 - where isthecontinuous integration system ????

[Jason Birch]

Hey Tom,
 
I'm not sure that the community has the mechanisms in place (funding, etc) to do it right.  I guess Trevor could set up a PayPal account :)  Perhaps we need to look at joining the OSGeo project sponsorship program?  Or investigating whether we can get some support at Telascience, though their hardware seems a bit stressed these days.
 
If this turns out to be beyond our current capabilities, I don't think it would necessarily be bad to leave packaging in one individual's hands, as long as all of the required files to do so are in SVN.  Many open source projects with limited resources operate this way.  
 
What do we need?  I believe that Trevor's outlined this in previous emails, but lets flesh it out before putting it into an RFC:
 
-> Server Machines (VM) / OS
  - Windows 200x
  - Linux (at least one flavour)
 
-> Software
  - Windows:  Visual Studio Standard for builds, some kind of continuous build framework (can't remember what Trevor recommended here)
  - Linux: Buildbot?
 
-> Glue
  - Copies of existing scripts for command-line building in Windows (I've asked for these before, but I don't think they made it into SVN)
  - Description of current unit testing procedures
  - Documentation on files/keys/configuration/permissions required for Windows installer.  I don't think the InstallShield files will be of much help to anyone here, but could be surprised?  Worse case, I can reverse-engineer this from the 2.0 installer, but...
  - And of course time/effort from folks to get it all put together.  I'm happy to contribute where I can...
 
Am I missing anything?
 
Jason