[mapguide-internals] RFC 58 Setting up a "Donate to Builds" process for the build infrastructure

[Tom Fukushima]

For me, I would only need the latest daily build.  The use case I see for this is that I think I have fixed a defect mentioned in a trac ticket, but I want to make sure, so I ask the ticket reporter to test against the latest daily build.

If no one else sees a need for posting more than the latest build, I think we can get rid of the cPanel cost. I'm also for keeping costs minimal.

-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Jason Birch
Sent: Monday, February 02, 2009 12:10 PM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] RFC 58 Setting up a "Donate to Builds" process for the build infrastructure

I'm not sure of the value of posting daily builds... unless we're
needing rapid feedback on new features?  For me, the daily builds would
be more of a "hey, fix that broken code you checked in" kind of thing :)

If we need dailies, I'd suggest something that keeps a week of dailies,
and then X number of months of weeklies; perhaps one or two?  Plus, we'd
want to make sure not to perform builds unless the code actually changes
that day/week.

I don't see a lot of use for maintaining a large history of builds.  If
anyone is really interested in this, they could set up a job that pulls
new files to a local store on a regular basis.

Overall, I'd like to keep the costs associated with the MapGuide project
as minimal as possible until we get a better handle of what kind of
ongoing support we have for infrastructure expenses.

Jason