[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: allegro-developers@xxxxxxxxxx
- Subject: [AD] 5.1.13.1
- From: SiegeLord <siegelordex@xxxxxxxxxx>
- Date: Sun, 28 Feb 2016 11:09:08 -0800
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding; bh=yufuaA4TaezWW9OWDoOqFVk0gmGMEtQDu1IB0gtXBqM=; b=Z4f5aEOnOxD1Qft10ja3qmtsd8iKNKuN+jYUyHokbPOiBx2gCvq+cDcqMbHoPNJH2b sjvTY5LeJsKXeylUO6bCeyGZ4uP3wQsdRl8W+ht6szn0TQAIAdt9l+DuoBp4d/EG7VH8 WWRrfSmISKQmU4+UcCR7+a/YNVPXnOCuBXeOp95PV86ScDYVZUf59NAnNInmdo7WWvQm Vt9rBH99quux8t42MuosXV5fEcDEAs6mz0rcTKlDSruDbAJ7i7TB8viux5JaSsHikAUq LSR8MC4UQm8QQh05erqLGJeEZPrrluJ+ywy0egifr7VC+0fyi96TE3Q1O4NZ8HY80hYz Mxkw==
I'm going to release 5.1.13.1 today (a bug fix release for 5.1.13,
fixing this: https://github.com/liballeg/allegro5/issues/575). Typically
I wouldn't bother doing bug fix releases for 5.1.x, but this seems like
an annoying regression and I wanted to explore the general procedure for
creating such a release. Since this bug only affects MSVC, I'll only
update the MSVC binaries.
-SL