[mapguide-internals] Update on builds infrastructure

[Zac Spitzer]

I concur! lets get 2.1 out the door asap and wait on RFC 60

but can we consider making making a major point release for
when RFC60 is ready?

z

On Sun, Sep 20, 2009 at 7:39 AM, Jason Birch <jason at jasonbirch.com> wrote:
> I can get it done, but it may be better if I helped setting up an easier way
> of pushing the official beta builds in the VM environment :)
> IMO, unless we decide to get RFC60 into 2.1 B2, it's going into trunk and
> being deferred to 2.2, and this was the main reason I've been holding back.
>  I am a bit worried about potential destabilization at this point, and my
> preference would be to push RFC60 back.  This is a great addition, and I'd
> use it myself, but I don't like the risk.
>
> If UV wants to maintain a sandbox branch of 2.1 that contains the RFC60 work
> to allow him to easily pull up fixes from the 2.1 stream for his client, as
> well as a sandbox branch of trunk for official integration at 2.2, I'd be
> happy with this approach.
>
> Jason
>
> 2009/9/18 Trevor Wekel <trevor_wekel at otxsystems.com>
>
>> Hi everyone,
>>
>> After two days of trickery, I have successfully migrated the MapGuide Open
>> Source build environment to VMware vSphere.  I decided to do this for a
>> couple of reasons:
>>
>> VMware is easier to use, more manageable, has integrated high availability
>> and integrated backup capability.  I also have nearly three years of
>> experience with VMware ESX technology.  From my perspective, it is simply a
>> better fit especially from a multi-platform (Windows/Linux) perspective.
>>
>> In addition, I am planning to move my VMware virtualization stack to a
>> colocation site.  This should improve uptime and reliability of the build
>> environment.  It also gives the Project the ability to host additional
>> infrastructure such as a code review tool.
>>
>> I am going to spend some time working on the build environment over the
>> next few days.  The first task on my list is to integrate the installer into
>> the build environment.  I will likely ping the list a few times as I work
>> through the process.
>>
>> Jason - depending on your timelines and availability, I may be able to
>> generate the second beta which was discussed at the PSC meeting last week.
>>  I should have something by end of next week if I don't hit too many snags.
>>
>> Thanks,
>> Trevor
>>
>>
>> _______________________________________________
>> mapguide-internals mailing list
>> mapguide-internals at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>>
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>



-- 
Zac Spitzer -
http://zacster.blogspot.com
+61 405 847 168