Hi,

> Gesendet: Sonntag, 02. August 2015 um 09:04 Uhr
> Von: "Michael T. Pope" <mp...@computer.org>
> An: "FreeCol Developers" <freecol-developers@lists.sourceforge.net>
> Betreff: Re: [Freecol-developers] 0.11.5
>
> On Sun, 2 Aug 2015 08:22:57 +0200
> win...@genial.ms wrote:
> > As there is a crippling bug and 0.11.3 is too old as a full replacement, we
> > are responsible for getting a hotfix release out ASAP, as we don't want to
> > have users endure the problem unnecessarily long.
> 
> OK, two firm votes for a quick 0.11.5 is indicative.  Although I still grin
> at the thought that 0.11.3 is "old".
> 
> > IMO, create a branch from the 0.11.4 release commit, cherry-pick all 
> > bugfixes,
> 
> The minimal set is 0.11.4 (ecbc3b7) + fix#2878 (167ecf9) + fix#2885
> (56ecbac).  I do not think the other bug fixes are safe enough and/or
> string-change free.
> 

I was going through the changelist independently and here are the commits,
which I found looked mergeable and possibly useful. It would need to be
shortened still to remove too risky stuff:

a2297d91 Autosave directory fix
5de4460f Integer option limits
7aef6f59 + b8c21dc2 + 8394732c BR#2875 package, maybe not useful enough
167ecf98 BR#2878
72190eeb splash moving, unnecessary?
1728101d temporary race condition fix
62073e9c IR#164, don't know if necessary?
56ecbac7 BR#2885
9f0b19cb + fa00b093 + 67e79229 Do we care about website stuff in the release 
branch?

> > Then copy the release info from the 0.11.4 release...
> 
> Can I get you to do the Release Notes?  I have to leave shortly, and am
> unlikely to have time to roll the release until tomorrow evening anyway.
> 

I'll update the wiki, but can't complete it until we know whats included.
You can proofread/change it tomorrow?


Greetings,

wintertime

------------------------------------------------------------------------------
_______________________________________________
Freecol-developers mailing list
Freecol-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freecol-developers

Reply via email to