From: Chris Brannon <chris@the-brannons.com>
To: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] version 3.6.0
Date: Thu, 01 Oct 2015 16:56:52 -0700 [thread overview]
Message-ID: <87d1wycfcr.fsf@mushroom.localdomain> (raw)
In-Reply-To: <20150901171617.eklhad@comcast.net> (Karl Dahlke's message of "Thu, 01 Oct 2015 17:16:17 -0400")
Karl Dahlke <eklhad@comcast.net> writes:
> Chris maybe you want to maintain a list of items to close before new version.
Yes, great idea. I don't think we're ready yet. This is a nice list;
my comments are below.
> Will they be releasing an official version that we are comfortable with?
> If not, how can we build and bundle our software with version 5.1.15
This is a big sticking point for a new edbrowse release. I don't know
what Geoff's release plans are, but that's a discussion we can have
sometime soonish, I suppose. We're still hammering out tidy issues.
If we end up bundling our own Tidy 5, my job is to make this painless
for distributors.
> Are we still getting seg faults or other serious problems?
Yes we are, but things are starting to slow down.
It needs a lot more exercise. You know what might be helpful here? I
could make some "bleeding edge" static builds of the latest code, and
then we could put out a call for testers on the command-line list.
Not having to do a song and dance to build all of this software from git
would make life easier for some would-be bug hunters.
Maybe I'll get to the point where I keep two sets of statics: one that
is "stable", and the other that is rebuilt from the latest code as often
as possible.
> Maybe have js off by default in the first windows port.
Yes, this is fine with me.
> but will it be feasible to maintain an edbrowse.exe along with our statics,
Sure it will, but I need someone to build it for me and to keep the
Windows build in sync with everything else.
-- Chris
prev parent reply other threads:[~2015-10-01 23:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 21:16 Karl Dahlke
2015-10-01 23:56 ` Chris Brannon [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d1wycfcr.fsf@mushroom.localdomain \
--to=chris@the-brannons.com \
--cc=Edbrowse-dev@lists.the-brannons.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).