Re: [hylafax]: the umlauts thing

On 04/17/2018 06:51 AM, Carsten wrote:
>
>
> Am 17.04.2018 um 12:15 schrieb Max Mothwurf:
>> Hello Carsten
>
>> I think we need to clarify what hylafax version you are really 
>> using...I have
>> to admit I did not check it when writing my answer
>>
>>> hylafax-server:
>>>     Installed: 3:6.0.6-6
>>
>> the 6.0.6 may point to the lastest release from hylafax.org, dated 
>> back to
>> 2012. Quite surprised that this is still in use...but thats a 
>> different story.
>> In this case - no. Hylafax uses a completely different localization than
>> hylafax+, where the patch refers to.
>>
>
> Ah, ok, I never thought about the EOL and Version History in this.
> So from what I understand right now, HylaFax is not updated since 2012 
> anymore?

To be accurate...

http://git.hylafax.org/

... the last commit was 2014-07-31.  The commit previous to that was 
2012-08-28.

> And Hylafax+ ist somehow its own branch from the original Hylafax but 
> is updated further?

The forking discussions are out there in the mailing list archives. In a 
nutshell, I was doing too much development for others to be comfortable, 
and so I felt like a fork would allow both sides to have what they 
wanted.  I had hoped that the fork would be "collaborative"... and that 
HylaFAX+ code development would make its way to the hylafax.org 
repository over time when those maintainers felt comfortable with it.

> To which point in time? I see
> "...
> Feb 22 2017:    Announcing HylaFAX+
> ..."
> on the web page at http://hylafax.sourceforge.net
> Even so it is not that outdated as the "original" it still seems to 
> got stuck over a year ago. Am I right?

To be accurate...

https://sourceforge.net/p/hylafax/HylaFAX+/HEAD/tree/

... the last commit was 2018-02-22.  The commit previous to that was the 
day previous.  But, hopefully you can see that the development is active.

There hasn't been a release for a year because the released code is 
quite stable.  I don't want to disrupt stable releases without reason 
benefiting the general base of users.

>
> Is there some living branch of it?

What do you mean by living?

> Is it reliable at all to count on Hylafax(+) if it goes to future 
> developement?

Open source software is yours to do with whatever you choose.  If you 
rely on others' decisions then you should get informed so that you know 
what you can rely on and what you can't.

Thanks,

Lee.



____________________ HylaFAX(tm) Users Mailing List _______________________
  To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
 On UNIX: mail -s unsubscribe [email protected] < /dev/null
  *To learn about commercial HylaFAX(tm) support, mail [email protected].*