Hi Lothar,
thanks to chime in!
On 5/26/26 22:45, Fredrik Roubert wrote:
On Tue 26 May 2026 at 18:26 +0200, Lothar Haeger via dev wrote:
Everyone is using Studio in production all over the place for more than
a decade (it's simply the best free OSS LDAP Browser/Editor out there) -
why not finally reflect that in the version number?
I don't know, but the simple fact that five years now have passed since
the last milestone release and it still isn't quite possible yet to do
the next one makes it seem to me as if things aren't yet quite so in
order as a proper 2.0 release normally would signify.
This is a very good question.
I think we have been *very* conservative with versions numbering and
features. For instance, between 2011 and 2017 we have had 33 milestones
and 2 RC before releasing a 1.0 for LDAP API. It was a bit quicker for
2.0, with only 4 milestones in 1 year.
The server is still in milestone mode since 2011, and we are targeting a
M28 as we speak.
For Studio, we are in milestone mode since 2012.
Frankly, I think Lothar is just right: let's get the 2.0 out. It
requires a bit of work since the LDAP API has evolved a bit since the
last studio release, so is the server.
But frankly, as much as I think the server is not production ready (we
still have to fix the data loss, and we need a working replication),
Studio *is* fine (beside the TLS 1.3 issue in the latest version)
The biggest issue is to be able to cut this release, in a fast moving
environment (Eclipse and Java).
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
