From: Karl Dahlke <email@example.com>
Subject: [Edbrowse-dev] version
Date: Thu, 15 Feb 2018 06:56:35 -0500 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
To recap, I created a nightmare with css parsing and querySelectorAll, because we had to, because some websites need it,
then I fixed the nightmare, so it doesn't bog down every site you look at.
With this in mind, and the other changes in the past few months, I think we should stabilize, then stamp a new version.
Fix bugs or make small enhancements (these are often the same thing), sure,
but no more major redesigns until 3.7.2.
Adam I still think we could put your gopher changes in, if you're up for that, I don't view that as a major redesign.
That would be a good thing to have.
But if you think that might not happen for a couple months then maybe move it to the next version.
What do you-all think?
next reply other threads:[~2018-02-15 11:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-15 11:56 Karl Dahlke [this message]
2018-02-15 18:48 ` Adam Thompson
2018-02-15 21:04 ` Karl Dahlke
2018-02-16 19:11 ` Adam Thompson
2018-02-18 2:19 ` Karl Dahlke
2018-02-18 2:42 ` Kevin Carhart
2018-02-18 3:03 ` Karl Dahlke
2018-02-18 3:39 ` Kevin Carhart
2018-02-18 7:43 ` Karl Dahlke
2018-02-18 8:17 ` Dominique Martinet
2018-02-18 8:47 ` Dominique Martinet
2018-02-18 8:30 ` Kevin Carhart
2018-02-18 7:45 ` Kevin Carhart
2018-02-18 8:55 ` Karl Dahlke
2018-02-18 11:29 ` Karl Dahlke
2018-02-18 14:08 ` Karl Dahlke
2018-02-19 1:07 ` [Edbrowse-dev] version / dyndns Kevin Carhart
2018-02-19 3:58 ` [Edbrowse-dev] update on dyndns Kevin Carhart
2018-03-24 16:07 [Edbrowse-dev] version Karl Dahlke
2018-03-25 8:11 ` Kevin Carhart
2018-06-11 15:45 [edbrowse-dev] version Karl Dahlke
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).