I like Robby's division into two bullets, and I like the idea of a footnote.
I wrote a note in the documentation for the new safety limits construct
that tries to address both compatibility with the old way(s) of configuring
your webserver and compatibility going forward, in that programmers can
Definitely a suggestion I should have made when I first saw that we
were going to have backwards incompatibility this release!
Robby
On Sat, Feb 1, 2020 at 12:27 PM John Clements wrote:
>
> That makes sense to me, but only if Philip has time to write that section. It
> also opens up a bit of a
That makes sense to me, but only if Philip has time to write that section. It
also opens up a bit of a can of worms in that I’m not sure whether the docs
currently has a good place for “discussion of changes relevant to a particular
release.” I guess I was thinking that just appending it to the
For this particular issue, I think that a section in the webserver
docs that includes things like: how to adjust your old webserver setup
to the new, explains why you might not want to do that, and more
broadly discusses the threats and how the defaults are a good
compromise would be really great.
Wouldn't it make sense to add a footnote to the release notes with a URL or
more detailed information? I know, this sounds nuts. In my mind, though, the
main body of the release notes should be short enough to skim to see whether
there’s anything interesting, but I don’t see a better place to
Looks like two bullets to me. Here's an edit:
* The Web Server provides fine-grained control over various aspects of
handling client connections (timeouts, buffer sizes, maximum header
counts, etc.) via the new "safety limits" construct.
* The web server's default level of trust in
This bullet is a teensy bit bulky, but I stared at it for a few minutes and…
I’d rather switch than fight. I guess that’s why I’m not a Tareyton smoker.
John
> On Jan 27, 2020, at 11:23, Philip McGrath wrote:
>
> On Mon, Jan 27, 2020 at 11:28 AM Matthew Flatt wrote:
> I would also highlight
On Mon, Jan 27, 2020 at 11:28 AM Matthew Flatt wrote:
> I would also highlight that the web
> server change is technically not backward-compatible.
>
…
> * The Web Server provides fine-grained control over various aspects of
>handling client connections (timeouts, buffer sizes, maximum
My preferences are "more responsive" for scrolling, the scrolling
bullet first, "improved" for dark-mode support, the Racket CS bullet
third so that the DrRacket items stay together, and "The Web Server"
instead of "The PLT Web Server". I would also highlight that the web
server change is
On Mon, Jan 27, 2020 at 10:07 AM Matthew Flatt wrote:
>
> At Mon, 27 Jan 2020 09:37:12 -0600, Robby Findler wrote:
> > [...] there is a problem on windows that makes
> > many of them moot (because we cannot seem to reliably detect when the
> > OS is in dark mode). So, IMO, the external
At Mon, 27 Jan 2020 09:37:12 -0600, Robby Findler wrote:
> [...] there is a problem on windows that makes
> many of them moot (because we cannot seem to reliably detect when the
> OS is in dark mode). So, IMO, the external perspective is probably
> that things are better on non-windows platforms
I'm happy with either order wrt to CS and scrolling. Matthew did most
of both of them so perhaps his opinion would be useful.
Robby
On Mon, Jan 27, 2020 at 9:43 AM Matthias Felleisen
wrote:
>
>
> @ John, almost all in one place:
>
> ~~ most suggested fixed incorporated.
> ~~ not incorporated:
Thanks Robby,
Is that the reason why I still don't get full "dark mode" that was
discussed in the thread (
https://groups.google.com/forum/#!topic/racket-users/3GgHnr6IurQ) even in
the latest 7.6.0.6--2020-01-27(c48afdb/a) snapshot build?
--JC
On Monday, January 27, 2020 at 9:37:26 AM UTC-6,
@ John, almost all in one place:
~~ most suggested fixed incorporated.
~~ not incorporated: changing the name of the executable.
~~ not incorporated: Robby’s request to move scrolling up.
~~ bracketed the last bullet; I think it could be dropped.
The final decisions are yours. — Matthias
There are aspects of the improvement that are in cross-platform code
(most of them in fact) but there is a problem on windows that makes
many of them moot (because we cannot seem to reliably detect when the
OS is in dark mode). So, IMO, the external perspective is probably
that things are better
On 1/27/20 4:01 PM, Matthias Felleisen wrote:
Typos fixed.
* Racket CS is ready for production use. We will work to further improve
Racket CS before making it the default implementation, but it now
consistently passes all of our integration tests and generally performs
well. (Compiled
Typos fixed.
* Racket CS is ready for production use. We will work to further improve
Racket CS before making it the default implementation, but it now
consistently passes all of our integration tests and generally performs
well. (Compiled code remains significantly larger compared to the
On 1/26/20 8:19 AM, 'John Clements' via dev-redirect wrote:
The release announcement sketch that I have so far is below. Please
mail me new items and/or edits.
Please phrase announcements using complete sentences and avoid the
word "now".
On Sun, Jan 26, 2020 at 1:19 AM 'John Clements' via dev-redirect
wrote:
>
> The release announcement sketch that I have so far is below. Please
> mail me new items and/or edits.
>
> Please phrase announcements using complete sentences and avoid the
> word "now".
>
The bitmap/url change is not in the web server, I think, and anyway
shouldn't be in the release notes.
Stencil vectors are not in 7.6.
Sam
On Sun, Jan 26, 2020, 2:19 AM 'John Clements' via dev-redirect <
d...@plt-scheme.org> wrote:
> The release announcement sketch that I have so far is
The release announcement sketch that I have so far is below. Please
mail me new items and/or edits.
Please phrase announcements using complete sentences and avoid the
word "now".
--
* DrRacket has support
21 matches
Mail list logo
