[fdo-internals] 3.4 update?

[Trevor Wekel]

Not sure I want to suggest this because it is going to be a bunch more work for me but...

For Fdo 3.5, should we move the open source builds to a community managed machine?  I am hosting a VMware virtualization environment and spinning up one more VM wouldn't kill me.

The MapGuide Open Source build machine is using Cruise Control .Net.  There was a bit of setup involved but the community chipped in so it wasn't brutal to do.

Thanks,
Trevor

From: fdo-internals-bounces at lists.osgeo.org [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Greg Boone
Sent: September 23, 2009 6:34 AM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] 3.4 update?

I will see what can be done.

From: fdo-internals-bounces at lists.osgeo.org [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Jason Birch
Sent: Wednesday, September 23, 2009 2:12 AM
To: FDO Internals Mail List
Subject: [fdo-internals] 3.4 update?

Are there any plans to do a new build of 3.4 to pass along the recent memory leak fixes, and to fix the provider naming issue with the King Oracle provider?

I'm going to be releasing an RC for MapGuide 2.1 within the next couple days, and if there was a patched windows build of FDO 3.4 to go along with it, that would be very cool.

Jason
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/fdo-internals/attachments/20090923/67debe73/attachment.html