From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] 3.5.3
Date: Fri, 06 Feb 2015 17:48:19 -0500 [thread overview]
Message-ID: <20150106174819.eklhad@comcast.net> (raw)
Ok I pushed a change so version is 3.5.3.git.
Chris, when the time is right, update this to 3.5.3,
mark that version in git, and then update to 3.5.4.git.
But when should that be?
When should we mark the next version?
We've made a lot of changes, good changes, since 3.5.2.
I've documented these in the CHANGES file,
please check and make sure I haven't missed anything.
Edbrowse works at least as well as before, and in many cases better,
so should we soon cut a new version 3.5.3,
or should we wait a bit and fold in the initial imap access
that Chris and I have started working on?
I would think no later than the imap push, we should mark the next version,
because some of the next changes, like Adam looking into tidy5
to parse html, are pretty substantial and systemic.
Karl Dahlke
next reply other threads:[~2015-02-06 22:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-06 22:48 Karl Dahlke [this message]
2015-02-07 16:24 ` Adam Thompson
2015-02-07 17:32 ` Chris Brannon
2015-02-07 16:34 ` Chris Brannon
2015-02-07 16:40 Karl Dahlke
2015-02-07 18:07 ` Adam Thompson
2015-02-09 14:07 Chris Brannon
2015-02-09 14:17 ` Adam Thompson
2015-02-09 14:26 Karl Dahlke
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=20150106174819.eklhad@comcast.net \
--to=eklhad@comcast.net \
--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).