пт, 17 мая 2019 г. в 13:39, Aleksandar Lazic <[email protected]>:
> Am 16.05.2019 um 10:00 schrieb Илья Шипицин: > > > > чт, 16 мая 2019 г. в 02:02, Aleksandar Lazic <[email protected] > > <mailto:[email protected]>>: > > > > Am 15.05.2019 um 18:52 schrieb Willy Tarreau: > > > Hi, > > > > > [snipp] > > > > I'd like to emit a new -dev release next week with the rest of the > pending > > > stuff, aiming at a final release by the end of this month. Please > do test > > > and report issues so that we don't get all of them in the last 3 > days as > > > usual. We all know releases slip a bit and I'm fine with this, but > at > > > least I'd like this to be for a good reason. Oh and keep in mind, > this > > > is *development* so please be careful with it. We all really > appreciate > > > to see bugs reported on live traffic but please don't use it as an > excuse > > > for switching all your LBs on it, or it may bite you hard! > > > > ;-) > > > > > I'm going to open a -next branch to collect the pending stuff for > 2.1. This > > > one will periodically be rebased on top of master so that it can > become the > > > next master after the release. > > > > > > Have fun! > > > Willy > > > > > > --- > > > Please find the usual URLs below : > > > Site index : http://www.haproxy.org/ > > > Discourse : http://discourse.haproxy.org/ > > > Slack channel : https://slack.haproxy.org/ > > > Issue tracker : https://github.com/haproxy/haproxy/issues > > > Sources : http://www.haproxy.org/download/2.0/src/ > > > Git repository : http://git.haproxy.org/git/haproxy.git/ > > > Git Web browsing : http://git.haproxy.org/?p=haproxy.git > > > Changelog : > http://www.haproxy.org/download/2.0/src/CHANGELOG > > > Cyril's HTML doc : http://cbonte.github.io/haproxy-dconv/ > > > > Docker images. > > > > OSSL: https://hub.docker.com/r/me2digital/haproxy20-centos > > BSSL: https://hub.docker.com/r/me2digital/haproxy20-boringssl > > > > > > Openssl build log: > > ########################## Starting vtest ########################## > > Testing with haproxy version: 2.0-dev3 > > # top TEST reg-tests/seamless-reload/abns_socket.vtc FAILED > (2.259) exit=2 > > 1 tests failed, 0 tests skipped, 39 tests passed > > > > https://gitlab.com/aleks001/haproxy20-centos/-/jobs/213234777 > > > > Boringssl build log: > > > > ########################## Starting vtest ########################## > > Testing with haproxy version: 2.0-dev3 > > # top TEST reg-tests/seamless-reload/abns_socket.vtc FAILED > (2.220) exit=2 > > 1 tests failed, 0 tests skipped, 38 tests passed > > > > https://gitlab.com/aleks001/haproxy20-boringssl/-/jobs/213241924 > > > > As we use more and more the CI features of github what's the opinion > of the > > community to use this features to create and push Container images > to the docker > > registry via the CI? > > > > > > gitlab.com <http://gitlab.com> allows mirroring arbitrary repo and > running CI > > (feature is called "CI/CD for external repo") > > the only requirement is having .gitlab-ci.yml > > > > so ... we can add .gitlab-ci.yml to main repo ... and use mirroring, i.e. > > git.haproxy.org --> gitlab.com > > Thanks for suggestion, I haven't know that. > > Well I don't think that's good to add another external tool. > From my point of view are enought *ci* parts in the current repo, due to > this > fact I would not like to add another one. > I did not mean "another" tool. I meant "if there's gitlab already, ok, lets integrate it into main repo" Anyway, travis-ci might be used as well. > > > I'm fine to keep it as it is but from project point of view it could > be better > > to have all together on one place, right? > > > > I'm also pretty curious about the first QUIC version ;-) > > > > > Willy > > > --- > > > Complete changelog : > > > > [snipp] > > Regards > Aleks >
