Hylafax Mailing List Archives
|
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
Re: [hylafax-users] [hylafax-devel] Re: Re: new community site
http://thread.gmane.org/gmane.comp.telephony.fax.hylafax.devel/4315
Matt,
Oh, THAT one ;-)
That was the single most contentions discussion I can recollect ever having
about any issue. I believe you may have been promoting two development
branches principally to address the batching issue? As I mentioned in my
previous email and in that thread, I don't personally favor two development
branches now that 4.2.x is mature. The 4.1.x "maintenance release" idea for
which there _was_ concensus was implemented but it withered on the vine and
never saw a release. Only Aidan, myself (and maybe patrice) ever backported
bugfixes to it, and we quietly gave up maintaining it.
If there was a concensus to change the development process that arose from
that thread and I missed it, I apologize. Perhaps you could summarize what
it was for me, and we can look to move in that direction?
The discussion arose from a position Aidan and I originally proposed in a
bug report - that HylaFAX ship with the batching feature set to only send
one job per batch, so that the default behaviour of HylaFAX would not change
and operators could choose to activate multi-job batching as an 'advanced
feature'. We supported our position by pointing out problems with the
current code - some of which still have not been fixed. I guess we muddied
the waters by trying to make two arguments at once:
a) that batching was a big change in behaviour, perhaps best "turned on"
deliberately by an admin
b) that the current batching implementation had scaling and security
problems
We were met with extreme hostility in that bug and associated threads
(including this one), and so we completely withdrew from the discussion and
completely withdrew our objection to batching. As a consequence, batching
was enabled by default in the next release, and we support that now because
there was clearly rough concensus that it be done that way.
Democracy is messy but it works.
-Darren
____________________ HylaFAX(tm) Users Mailing List _______________________
To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null
*To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*