[3429] in BarnOwl Developers
Re: tagging barnowl 1.9rc2 (= 1.9???) later today
daemon@ATHENA.MIT.EDU (Alex Dehnert)
Sun May 26 02:16:08 2013
Date: Sun, 26 May 2013 02:16:01 -0400
From: Alex Dehnert <alex@dehnerts.com>
To: Geoffrey Thomas <geofft@ldpreload.com>
CC: barnowl-dev@mit.edu
In-Reply-To: <alpine.DEB.2.00.1305251246540.27837@dr-wily.mit.edu>
Can we add the "default_format with a more useful error message" patch
(so "Config error: see http://web.mit.edu/df" or some such, instead of
just the URL)? It does seem like several people have received the new
default format and been confused.
Also, is it worth planning to tag 1.10rc1 shortly after 1.9 releases? It
seems like we've gotten quite a few new commits between 1.9rc1 and now,
so maybe it's reasonable to do two releases in short order.
~~Alex
On 05/25/2013 03:50 PM, Geoffrey Thomas wrote:
> I intend to tag barnowl 1.9rc2 with the contents of the release-1.9
> branch on my github clone:
>
> https://github.com/geofft/barnowl/commits/release-1.9
>
> This is barnowl 1.9rc1, plus a couple of serious-looking bugs from
> master that looked worth including in a release. My plan is to tag it
> either later today or tomorrow, do a locker build of barnowl-beta, and
> then do a release maybe a week later if all looks well.
>
> Let me know if there's anything that should get in the release that
> isn't there, or vice versa.
>
