[3956] in BarnOwl Developers
Re: Any interest in a new release sometime soon
daemon@ATHENA.MIT.EDU (Adam Glasgall)
Tue Aug 23 11:13:52 2016
To: Jason Gross <jasongross9@gmail.com>, Sam Hartman <hartmans@mit.edu>,
barnowl-dev@mit.edu
From: Adam Glasgall <adam@crossproduct.net>
Date: Tue, 23 Aug 2016 11:13:49 -0400
In-Reply-To: <CAKObCaqv7izMiJyPhJyBxTE1Y6R6uRNuwV6JzSc=6=CYkMKdhA@mail.gmail.com>
On 08/23/2016 10:31 AM, Jason Gross wrote:
> (Sorry, I meant to point at the two PRs of deferred logging, and of
> moving the logging code to Perl, which allows nicer logging of things
> like IRC messages)
>
We could do a release. The process is a bit annoying, though most of
that is the locker builds.
Jason, remind me how the perl-loging code interacts with the
do-logging-i/o-on-a-worker-thread-to-avoid-blocking-the-UI feature?
Adam
>
> On Tue, Aug 23, 2016, 7:29 AM Jason Gross <jasongross9@gmail.com
> <mailto:jasongross9@gmail.com>> wrote:
>
> I have interest in it (as well as interest in getting my two
> long-standing PRs merged (deferred logging to handle AFS blips, and
> irc-auto-reconnect to deal with internet blips), for which I've been
> running a patched BarnOwl myself). I've never been part of the
> release process before, though, and am not entirely sure what goes
> into releasing.
>
>
> On Tue, Aug 23, 2016, 7:08 AM Sam Hartman <hartmans@mit.edu
> <mailto:hartmans@mit.edu>> wrote:
>
>
> I need to make a new upload of barnowl to deal with an FTBFS bug for
> Debian.
> It's been kind of a long time since the last barnowl release.
> The fix needed for this issue is fairly simple, although openssl 1.1
> looms on the horizon.
> Any interest in trying to make a release in the next couple of
> months in
> hopes of getting something new into stretch?
>
