Hi,
I don't care how its named ( my favorite would be 0.11.4.1 :p ), but 0.11.4
was out and downloaded already, so thats taken.
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.
IMO, create a branch from the 0.11.4 release commit, cherry-pick all bugfixes,
don't mess with the translations, don't add any risky things like new features
or refactorings, maybe even leave out some risky bugfix.
Then copy the release info from the 0.11.4 release (as its nearly the same
and people still want to know all the changes) and only add a little 0.11.5
top section telling this is a hotfix release to fix the map issue and possibly
some other bugs we have cherry-picked fixes for.
Then test the branch for a few hours (not weeks), meanwhile compile
the new packages, upload and be done with it.
Btw., I yesterday was looking if izpack got new versions, but they seem to
have lost their hoster and the website I saw is a mess, promoting an RC5
as newest download, but the news section having the full release and 3
other bugfix releases already, without providing a download.
Not to speak of their inaccessible "no permission" new bugtracker and
mailing list archive.
So we might want to wait a bit more with updating that, even though we
still have 2 smaller problems with it.
Greetings,
wintertime
Gesendet: Sonntag, 02. August 2015 um 05:24 Uhr
Von: "Caleb Williams" <cale...@gmail.com>
An: "FreeCol Developers" <freecol-developers@lists.sourceforge.net>
Betreff: Re: [Freecol-developers] 0.11.5
Von: "Caleb Williams" <cale...@gmail.com>
An: "FreeCol Developers" <freecol-developers@lists.sourceforge.net>
Betreff: Re: [Freecol-developers] 0.11.5
On Sat, Aug 1, 2015 at 9:59 PM, Michael T. Pope <mp...@computer.org> wrote:
On Sat, 1 Aug 2015 21:02:16 -0500
Caleb Williams <cale...@gmail.com> wrote:
> ... 0.11.4a
Please, let us not mess with the numbering scheme.
Well, in that case, see below:
> I don't think it would be wise
> to just re-release 0.11.4 with this fix. I see no reason why we cannot
> ordinarily wait, but for the fact that this bug seems quite debilitating
> and FreeCol should be kept as usable as possible.
Now I am confused. You seem to be saying for us not to release a
different build of 0.11.4 as 0.11.4. I do not know why you are saying
this as it was not one of the options I proposed, nor would it be. There
are 0.11.4 binaries out there, the best we can do about them is tell
people not to use them.
I was just trying to head off any discussion of that.
0.11.5 it is.
Caleb
------------------------------------------------------------------------------
_______________________________________________ Freecol-developers mailing list Freecol-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freecol-developers