On 05/03/2019 17:26, Jonathan Valliere wrote:
I thought the IoFilter changes didn’t break anything.
Me too:/ Sadly, I can tell you that Apache LDAP API had to rollback to
2.0.18 when 2.0.19 was released, because of some breakages. This is
because we rollbacked the changes in 2.0.19, and
I thought the IoFilter changes didn’t break anything.
+1 if we are not committing to support 2.0.X indefinitely.
On Tue, Mar 5, 2019 at 11:23 AM Emmanuel Lécharny
wrote:
>
> On 05/03/2019 15:54, Jonathan Valliere wrote:
> > Why not backport the IoFilter changes and go all out with a whole new
On 05/03/2019 15:54, Jonathan Valliere wrote:
Why not backport the IoFilter changes and go all out with a whole new SSL
design for 2.1.X?
We can't backport the changes made in 2.1 to 2.0, it breaks things in
other projects, this is why we released 2.0.19. The idea is to move
forward with a
Why not backport the IoFilter changes and go all out with a whole new SSL
design for 2.1.X? Then give everyone 18 months of updates to 2.0.X before
being deprecated.
On Tue, Mar 5, 2019 at 9:07 AM Emmanuel Lécharny
wrote:
>
> On 05/03/2019 14:19, Jonathan Valliere wrote:
> > What in 2.1.X is
On 05/03/2019 14:19, Jonathan Valliere wrote:
What in 2.1.X is not compatible with products build around 2.0.X?
The difference lies in the API change in IoFilter interface (which
should not impact your code), and in the IoHandler interface, where the
addition of the event() method has been
What in 2.1.X is not compatible with products build around 2.0.X? Is the
effort to update a project to work with 2.1.X something that takes more
than a couple of minutes? I'm concerned with using minor version numbers as
separate products to maintain.
On Tue, Mar 5, 2019 at 12:47 AM Emmanuel
