[3430] in BarnOwl Developers
Re: tagging barnowl 1.9rc2 (= 1.9???) later today
daemon@ATHENA.MIT.EDU (Geoffrey Thomas)
Sun May 26 05:38:20 2013
In-Reply-To: <51A1A8A1.8030500@dehnerts.com>
Cc: Geoffrey Thomas <geofft@ldpreload.com>,
"barnowl-dev@mit.edu" <barnowl-dev@mit.edu>
From: Geoffrey Thomas <geofft@MIT.EDU>
Date: Sun, 26 May 2013 02:38:12 -0700
To: Alex Dehnert <alex@dehnerts.com>
I was vaguely hoping to have the df locker by now, but yes, my intention is t=
o add that onto the release branch when we get it. If it's important to add "=
Config error" before releasing barnowl-beta, I'm happy to do this in two com=
mits,
I'm not as familiar with the work on master and it looks like there might be=
unfinished stuff, so I don't have strong opinions on when to tag 1.10. Skip=
ping the 1.9 release did vaguely occur to me, though.
--=20
Geoffrey Thomas (via mobile)
On May 25, 2013, at 23:16, Alex Dehnert <alex@dehnerts.com> wrote:
> 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.
>=20
> 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.
>=20
> ~~Alex
>=20
> 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:
>>=20
>> https://github.com/geofft/barnowl/commits/release-1.9
>>=20
>> 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.
>>=20
>> Let me know if there's anything that should get in the release that
>> isn't there, or vice versa.
>>=20
>=20
