On Tue, Jan 12, 2021 at 01:34:08PM +0100, Tim Düsterhus wrote:
> I'm not sure that's necessary. For features there IMO only three states:
>
> - Implemented: Closed + Fixed.
> - Not Planned: Closed + No Label.
> - Maybe Planned: Open.
I'm having a problem with the last one, which is that we're con
Willy,
Am 12.01.21 um 11:49 schrieb Willy Tarreau:
>> Maybe it makes sense to look through the list of currently open feature
>> requests and close the ones that are very unlikely to be implemented (or
>> unlikely to be implemented in the next few years) to clean up the
>> tracker a bit.
>
> Prob
Hi Tim,
On Sun, Jan 10, 2021 at 04:37:16PM +0100, Tim Düsterhus wrote:
> as of right now feature requests make up almost half of the open issues
> in the issue tracker (102 / 226). When looking through them I'm seeing a
> few that are probably not going to be implemented any time soon (if ever).
On 11.01.21 00:32, John Traweek CCNA, Sec+ wrote:
unsubscribe
You can unsubscribe you self from the list.
https://www.haproxy.org/#tact
Regards
Aleks
On 1/10/21, 10:03 AM, "Tim Düsterhus" wrote:
Hi List,
Willy,
Lukas,
as of right now feature requests make up almost ha
unsubscribe
On 1/10/21, 10:03 AM, "Tim Düsterhus" wrote:
Hi List,
Willy,
Lukas,
as of right now feature requests make up almost half of the open issues
in the issue tracker (102 / 226). When looking through them I'm seeing a
few that are probably not going to be impleme
Hi List,
Willy,
Lukas,
as of right now feature requests make up almost half of the open issues
in the issue tracker (102 / 226). When looking through them I'm seeing a
few that are probably not going to be implemented any time soon (if ever).
An example would be "cache-aware server push" (#31):
h
6 matches
Mail list logo
