On 21 Jul 2016 22:15, Julien ÉLIE wrote:
> I would personally be interested in a release of Autoconf 2.70 with
> updated config.sub and config.guess helper scripts. As a matter of
> fact, there are recent systems where I cannot configure Autoconf because
> of obsolete config.{sub,guess}; I
On 20 July 2016 at 22:31, Zack Weinberg wrote:
> I'm also interested in seeing a release in the near future. Is there
> any way people without commit rights (e.g. me) can help?
The obvious answer would be for you to get commit rights. Hopefully
you could agree with the Autoconf
Hi Erik,
How much time it takes to make a release? For the outsider there's
not many obviously needed steps that take a lot of time. Does making a
RC take as much time as full release, or could we have RC for testing
both autoconf and the build systems of projects that use it?
The biggest
On 07/21/2016 12:25 AM, Marko Lindqvist wrote:
> On 21 July 2016 at 00:06, Eric Blake wrote:
>> On 07/20/2016 11:21 AM, Craig Andrews wrote:
>>>
>>> what's
>>> blocking a release?
>>
>> Lack of free time from someone with commit rights.
>
> How much time it takes to make a
On 21 July 2016 at 00:06, Eric Blake wrote:
> On 07/20/2016 11:21 AM, Craig Andrews wrote:
>>
>> what's
>> blocking a release?
>
> Lack of free time from someone with commit rights.
How much time it takes to make a release? For the outsider there's
not many obviously needed
On Wed, Jul 20, 2016 at 5:06 PM, Eric Blake wrote:
> On 07/20/2016 11:21 AM, Craig Andrews wrote:
>> There have been a number commits made to autoconf since 2.69 was
>> released on April 24, 2012. FWIW, I'm particularly interested in the
>> runstatedir change.
>>
>> Is it
On 07/20/2016 11:21 AM, Craig Andrews wrote:
> There have been a number commits made to autoconf since 2.69 was
> released on April 24, 2012. FWIW, I'm particularly interested in the
> runstatedir change.
>
> Is it possible to make a 2.70 release in the near future? If not, what's
> blocking a