[Nut-upsdev] nut-2.4.2 : IPV6 badly managed at configure

Alexey Loukianov mooroon2 at mail.ru
Thu Feb 25 09:54:07 UTC 2010

Hash: SHA1

24.02.2010 14:44, Arjen de Korte wrote:
> Citeren Arnaud Quette <aquette.dev at gmail.com>:
>> I'll now be thinking about mechanisms to avoid this kind of situation
>> in the future.
> More frequent releases is the only thing that helps. This time was no  
> different from the past, the reports about regressions usually only  
> arrive *after* we release a new version. People only start testing  
> once we release something. The feedback from testing version has  
> typically been limited to the subscribers to the development  
> mailinglist, which is not nearly enough to what we need.

As I had already mentioned on the list the NUT site is unavailable from several
Moscow ISPs due to upstream routing problem so I wasn't able to check the site
contents prior to the release of 2.4.2. I would like to know if were there any
release candidates published on the frontpage of the site?

I think that in case devteam want users to test something it is not sufficient
just to post "Release Freeze - Please Test" message on the mailing list. Posting
a link to the freshest "pre-release testing" tarball on the frontpage will give
much more feedback. Increasing pre-release testing phase from one week to - say
- - a month, will also help. Co-operating with major linux package vendors (like
DAG/RPMFORGE, ATrpms, e.t.c.) and respective analogues from the other operating
systems to provide compiled release candidates binaries will widen the testing
community with people that are unexperienced to compile themselves but still may
wish to give valuable feedback.

And in the end, it won't hurt much if NUT will release more often than once in a

P.S. Another thing to think about is a possible split of NUT from one big
tarball to a separate parts that may be released separately. It is not a big
surprise that the drivers part of a NUT seems to be changing more frequently
than the rest of the codebase. Is is also not a big surprise that the fresh
drivers are of a bigger requirement than a "new fancy feature there and here"
from the point of view of a user with an unsupported device. Suppose that a
company had purchased a new server + a new UPS, and this UPS is not supported
yet by the NUT. Corporate security policy often require not to use SVN snapshots
on production servers, and that means that company will have to wait for about a
year till a new release of the NUT arrives that adds a support for this device.
If the drivers were a separate package that gets released - say - monthly, the
minimal waiting time for a device to become supported by the latest release
would shrink to a one month. I think that it is worth considering.

- -- 
Best regards,
Alexey Loukianov                          mailto:mooroon2 at mail.ru
System Engineer,                            Mob.:+7(926)218-1320
*nix Specialist

Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/


More information about the Nut-upsdev mailing list