Re: Doc updates on v-c.o
On Thu, Mar 14, 2019 at 9:23 PM Geoffrey Simmons wrote: > > @Dridi, the sentence about Python under “for developers” in “Changes” implies > that python 2 is still an option. I assume that’s no longer correct? That > went in fairly early, before the decision about python 3 was made. Right, I did not catch that one and added the note about dropping python 2 in the Upgrading document. I'm fixing it now. Dridi ___ varnish-dev mailing list varnish-dev@varnish-cache.org https://www.varnish-cache.org/lists/mailman/listinfo/varnish-dev
Re: Doc updates on v-c.o
@Dridi, the sentence about Python under “for developers” in “Changes” implies that python 2 is still an option. I assume that’s no longer correct? That went in fairly early, before the decision about python 3 was made. Thx, Geoff > On Mar 14, 2019, at 8:46 PM, Dridi Boukelmoune wrote: > >> On Thu, Mar 14, 2019 at 8:31 PM Poul-Henning Kamp >> wrote: >> >> >> In message , Geoffrey Simmons >> wr >> ites: >> >> Seems like python3 fallout. should be fixed now > > Also https://varnish-cache.org/docs/ says: > > Documentation for the latest release 6.0 > > 6.1 never made it in the docs :-/ > > Dridi ___ varnish-dev mailing list varnish-dev@varnish-cache.org https://www.varnish-cache.org/lists/mailman/listinfo/varnish-dev
Re: 2019-03-15 release
In message , Dridi Boukelmoune writes: >On Thu, Mar 14, 2019 at 8:43 PM Poul-Henning Kamp wrote: >> >> Do not cut the release until I give the OK. >> >> I/We have a couple of i's to dots and t's to dash first. > >And coverity reported a bunch of things too! Those are part of it. (Many thanks to Federico for getting a Coverity Run through!) -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ varnish-dev mailing list varnish-dev@varnish-cache.org https://www.varnish-cache.org/lists/mailman/listinfo/varnish-dev
Re: 2019-03-15 release
On Thu, Mar 14, 2019 at 8:43 PM Poul-Henning Kamp wrote: > > Do not cut the release until I give the OK. > > I/We have a couple of i's to dots and t's to dash first. And coverity reported a bunch of things too! Dridi ___ varnish-dev mailing list varnish-dev@varnish-cache.org https://www.varnish-cache.org/lists/mailman/listinfo/varnish-dev
Re: Doc updates on v-c.o
On Thu, Mar 14, 2019 at 8:31 PM Poul-Henning Kamp wrote: > > > In message , Geoffrey Simmons > wr > ites: > > Seems like python3 fallout. should be fixed now Also https://varnish-cache.org/docs/ says: Documentation for the latest release 6.0 6.1 never made it in the docs :-/ Dridi ___ varnish-dev mailing list varnish-dev@varnish-cache.org https://www.varnish-cache.org/lists/mailman/listinfo/varnish-dev
2019-03-15 release
Do not cut the release until I give the OK. I/We have a couple of i's to dots and t's to dash first. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ varnish-dev mailing list varnish-dev@varnish-cache.org https://www.varnish-cache.org/lists/mailman/listinfo/varnish-dev
Re: Doc updates on v-c.o
In message , Geoffrey Simmons wr ites: Seems like python3 fallout. should be fixed now -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ varnish-dev mailing list varnish-dev@varnish-cache.org https://www.varnish-cache.org/lists/mailman/listinfo/varnish-dev
Doc updates on v-c.o
I just noticed that the project docs under “trunk” in v-c.o have not been updated for several days. It would good to be able to see the current state before tomorrow’s release. Does someone how to kick the tires? (phk?) Thanks, Geoff ___ varnish-dev mailing list varnish-dev@varnish-cache.org https://www.varnish-cache.org/lists/mailman/listinfo/varnish-dev
