Re: Planning betas and releases

[Peter Rosin]

On 2013-05-28 21:29, Stefano Lattarini wrote:
> Hi Peter.
> 
> On 05/28/2013 09:09 PM, Peter Rosin wrote:
>> On 2013-05-28 20:10, Stefano Lattarini wrote:
>>> +        <http://austingroupbugs.net/view.php?id=542>7
>>
>> You have a mysterious trailing 7 here...
>>
>> Cheers,
>> Peter
>>
> Oops, will remove.  Thanks.
> 
> BTW, I plan to release the beta for 1.13.3 tomorrow (planned
> release: 3 June) and the beta for 1.14 tomorrow or the day
> after (planned release: ~ 20 June).  So if you find something
> fishy in NEWS,

I did a quick read if NEWS in the master branch, and I wanted these
changes:

diff --git a/NEWS b/NEWS
index 5172150..6355bec 100644
--- a/NEWS
+++ b/NEWS
@@ -6,7 +6,7 @@ New in 2.0:
    object will *always* be put into the subdirectory named after the source
    file, rather than in the current directory.  For instance, 'src/file.c'
    and 'src/file.f90' will be compiled to 'src/file.o', and 'sub/dir/mu.cc'
-   will be compiled to 'sub/dir/mu.o'.  Put in another way, Automake 1.14
+   will be compiled to 'sub/dir/mu.o'.  Put in another way, Automake 2.0
    and later will *unconditionally* behave as older Automake versions did
    when the 'subdir-objects' option was given.

@@ -19,7 +19,7 @@ New in 2.0:
     hierarchy, a definition of the AM_PROG_VALAC macro found in file
     (say) '/usr/local/share/aclocal/my-vala.m4' should take precedence
     over the same-named automake-provided macro, as defined in file
-    '/usr/local/share/aclocal-1.14/vala.m4'.
+    '/usr/local/share/aclocal-2.0/vala.m4'.

 * Obsolescent features flagged:

@@ -275,7 +275,7 @@ New in 1.13.3:

 * Documentation fixes:

-  - The documentation no longer mistakenly report that the obsolete
+  - The documentation no longer mistakenly reports that the obsolete
     'AM_MKDIR_PROG_P' macro and '$(mkdir_p)' make variable are going
     to be removed in Automake 2.0.

@@ -288,7 +288,7 @@ New in 1.13.3:

   - The test cases no longer have the executable bit set.  This should
     make it clear that they are not meant to be run directly; as
-    explained in t/README, the can only be run through the custom
+    explained in t/README, they can only be run through the custom
     'runtest' script, or by a "make check" invocation.

   - The testsuite has seen the introduction of a new helper function
@@ -312,14 +312,14 @@ New in 1.13.2:

   - The long-deprecated but still supported two-arguments invocation form
     of AM_INIT_AUTOMAKE is documented once again.  This seems the sanest
-    thing to do, given that support for such an usage might need to remain
-    in place for a unspecified amount of time in order to cater for people
+    thing to do, given that support for such usage might need to remain
+    in place for an unspecified amount of time in order to cater to people
     who want to define the version number for their package dynamically at
     configure runtime (unfortunately, Autoconf does not yet support this
     scenario, so we cannot delegate the work to it).

   - The serial testsuite harness is no longer reported as "deprecated",
-    but as "discouraged".  We have no plan to remove it, not to make its
+    but as "discouraged".  We have no plan to remove it, nor to make its
     use cause runtime warnings.

   - The parallel testsuite is no longer reported as "experimental"; it

Sorry for not doing a better job of finding what branch each change
belong to, and for not committing it myself...

BTW, I also find your use of (sic!) strange, sic is normally used
when you are quoting something that is obviously wrong, and you
want to point out that it is indeed not a quoting mistake, but
instead some error that was present also in the quoted source. But
you are not even quoting anything, so the sic! mark makes no sense
at all.

>                 or has some lingering failures on Windows, feel
> free to speak up ASAP.

Testsuite is (still) running, so far cxx-demo has failed with
MSVC, and I guess it will fail for MinGW as well. From a cursory
look it appear that the expected output is written with an MSYS
bash and therefore has NL line endings, while the program output is
for a windows program with CRNL line endings. diff then barfs.
distcheck-pr10470.sh also fails, apparently since ./test-driver
isn't installed, here is a snippet from the log:

        + automake-1.99a --foreign -Werror -Wall
        parallel-tests: error: required file './test-driver' not found
        parallel-tests:   'automake --add-missing' can install 'test-driver'

I will do better failure reports later when the testsuite
has finished. BTW, this was from master, in hindsight I should have
tried micro first, but I'll let this run finish.

>                         As for 2.0, we must anyway wait an year
> or more, to give people time to be reached by new warnings and
> adjust, so no hurry there.
> 
> I'd like to speed things because I'm not going to be much
> available after the end of June (and I'm not sure for how long).
> So better tie loose ends and leave stuff in a consistent status.
> 
> Regards,
>   Stefano
>