>> Ondrej Kuzník <ondra(a)mistotebe.net> schrieb am
31.03.2022 um 17:55 in
On Wed, Mar 23, 2022 at 03:07:25PM +0100, Michael Ströder wrote:
> On 3/23/22 12:19, Ondřej Kuzník wrote:
>> On Tue, Mar 22, 2022 at 08:03:35PM +0100, Michael Ströder wrote:
>> > On 3/22/22 18:21, Quanah Gibson-Mount wrote:
>> > > This is the first testing call for OpenLDAP 2.6.2.
>> > Tested git revision 475e57281bc10e56a47021895a7b926e29ac9072 on
>> > Tumbleweed x64_64 (gcc version 11.2.1):
>> > - make test worked
>> > - unit tests of my Python module ldap0 work
>> Just a thought, are people pushing the RC code into testing/pre-prod
> Sometimes I do on my openSUSE-based Æ-DIR test systems based on branches
> my packages in OBS. But it's additional work for which I
don't always have
> spare time left.
thanks, even that's appreciated.
> Do you have any particular things in mind that need more thorough testing
> before 2.6.2 is released?
It was a general question. While it's nice that people run "make test" and
sometimes "make its", it would be even nicer if we got regular feedback
from actual test environments. If we got people to publish any metrics
they gather (performance or otherwise), we could even track the
evolution of the software in a real world setting, I know I'm not asking
for much ;)
Maybe maintain an OVL for each release, where "OVL" means "Operating
Verification List" ;-)
(The list of Operating System Releases where compilation and selftest
>> Does the current schedule of 1+ weeks between a testing
>> call and potential release give you enough time?
> IMHO most people are not going to test in real environments before the
> OpenLDAP project cuts a release, no matter how long this testing period
That has been a hypothesis for a while and this is an attempt to
challenge it, just in case :)
Senior Software Engineer
Symas Corporation http://www.symas.com
Packaged, certified, and supported LDAP solutions powered by OpenLDAP