We would need permission from Torsten D, our release manager, but I would
also second Thorsten R's proposal to defer the 2.12 release by a week or
two. I have been spread very thin this summer with my day job projects and
will be out of town myself on the 16-18 of August.
I think we should at minimum get the Mac and Windows build slaves going,
generate release candidates for both platforms, and push those out in the
wild for a week (and address any major issues that surface) before
finalizing the actual release.
I apologize for not being more out in front of this ... this has been the
summer from hell (work-wise) for me.
Regards,
Curt.
On Tue, Aug 13, 2013 at 7:24 AM, James Turner <zakal...@mac.com> wrote:
>
> On 13 Aug 2013, at 12:58, Renk Thorsten <thorsten.i.r...@jyu.fi> wrote:
>
> On the risk of making myself really unpopular, but would now be a good
> time to defer the release? It seems James is caught in the middle of
> moving, Stuart indicated some other private things piling up, I have the
> maddest travelling schedule I've ever had in my life this fall, and I
> haven't seen a number of other folks around for a while, we don't have
> release candidates out which will have impacts on bugfixes, assuming
> there'd be anyone around capable of doing bugfixes,...
>
> It seems we've hit a fluctuation where pretty much everyone is occupied
> with something else at the moment (?) - if that's the case, should we still
> go ahead?
>
>
> That's possibly a fair suggestion. I am scheduled to get my new broadband
> connection up and running tomorrow (Wednesday) so the Mac build slave will
> be available at that time (with decent upstream bandwidth again). However
> my time is a bit fragmented and likely to remain so for a few weeks - I'm
> happy to merge patches or anything else anyone explicitly requests, but I'm
> not focused enough to start chasing other people to get things done :)
>
> Once the Mac build slave is back, the biggest obstacle to an RC is getting
> the Windows build slaves to behave; if anyone on Windows could look at the
> Jenkins logs and shed any light, it would help.
>
> Kind regards,
> James
>
>
>
> ------------------------------------------------------------------------------
> Get 100% visibility into Java/.NET code with AppDynamics Lite!
> It's a free troubleshooting tool designed for production.
> Get down to code-level detail for bottlenecks, with <2% overhead.
> Download for free and get started troubleshooting in minutes.
> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
> _______________________________________________
> Flightgear-devel mailing list
> Flightgear-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>
>
--
Curtis Olson:
http://www.atiak.com - http://aem.umn.edu/~uav/
http://www.flightgear.org - http://gallinazo.flightgear.org
------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
