Hi Willy. Am 30.09.2018 um 11:05 schrieb Willy Tarreau: > Hi Aleks, > > On Sun, Sep 30, 2018 at 10:38:20AM +0200, Aleksandar Lazic wrote: >> Do you have any release date for 1.9, as I plan to launch some new site and >> thought to use 1.9 from beginning because it sounds like that 1.9 will be >> able >> to handle h2 with the backend. > > It's initially planned for end of October/early November, but I think we'll > stretch the months a little bit. The extremely difficult part is the rework > of the HTTP engine to migrate to the native internal representation which > is needed to transport H2 semantics from end to end. While a huge amount > of work has been done on this, it also uncovered some very old design > heritage that needed to be replaced and that takes time to address, such > as the changes to logging and error snapshots to make them work out of > streams, or the change of connection orientation which we initially expected > to postpone after 1.9 but that we discovered late is mandatory to finish the > work, and the change of the idle connections that's needed to maintain > keep-alive on the backend side. > > These changes have a huge impact on the code and the architecture, so as > per the technical vs functional release cycle, I'd really want to have > this in 1.9 so that we have all the basis for much cleaner and calmer > development for 2.0. But I'm sure we will face yet more surprises. > > Thus if we see that it's definitely not workable to complete these changes > by ~November, we'll possibly release without them but will put all of them > in a -next branch that we'll merge soon after the release. However if we > manage to have something almost done, I'm willing to push the deadline a > little bit further to let this be finished. Christopher suggested that we > might have a 3rd option which is to have the two implementations side by > side and that we decide by configuration which one to use depending on > the desired features. That's indeed an option (a temporary one) but I > don't like it much due to the risk of increased complexity with bug > reports. That's still definitely something to keep in mind anyway.
I agree here with you. > I sincerely hope it's the last time we engage in such complex changes in a > single version! I got caught several years ago during the 1.5 development > and this time it's even more complex than what we had to redesign by then! Well when I think back to 2003 haproxy is now complete different, cool evolution ;-) > Hoping this clarifies the situation a bit, Yes definitely. I will start with 1.8 just to be on the save site. Thank you for your always detailed answer. ;-) > Willy Best regards Aleks