Re: [Tcllib-devel] Upcoming vacation, Tcllib Trunk Commit Access

[Andreas K. <aku...@sh...>]

The current head of Tcllib trunk ([e6742077ec]), committed and pushed
yesterday evening PST, passed the entire testsuite for me now, against
Tcl core versions:

   8.4.20 - [649ee985ae] 2013-06-03 18:08 UTC
   8.5.19 - [523e36b232] 2019-01-28 16:12 UTC
   8.6.9  - [60d2391840] 2019-02-18 20:38 UTC

I dropped doing tests against 8.7 for the moment. While an old a2
reported test failures I have issues with installing the current
[fc1de63689], something related to the new zipfs and its
initialization. As it is still marked as an alpha I decided that it is
ok to go without it.

As my commit and push of the testsuite fixes implies, I have opened
the trunk to commits by myself now. (Much later than I wanted).

The next steps are to go over a number of pending branches, test them,
and merge. I will start with the older branches first, with thanks to
their authors for waiting patiently.

After that comes updating and modernizing the "README.developer" file,
and adding a file about communication. On a branch, of course, so that
we can discuss the changes before committing to them (by merging to
trunk).

Where `we` will be as many of Tcllib maintainers and developers as can
be found (Good thing that the accounts come with email addresses).

> In recent days a lot of sparks have flown in the Tcler's chat about
> breakage in the Tcllib trunk branch, named "trunk" (what a surprise,
> not), standard conformity, breaking the trunk, backward compatibility,
> etc.

[...]

-- 
See you,
	Andreas Kupries <aku...@sh...>
			<http://core.tcl.tk/akupries/>
	Developer @	SUSE (MicroFocus Canada LLC)
		  	<and...@su...>

EuroTcl 2019, Jun 29-30, Nuernberg/DE, http://eurotcl.eu/
-------------------------------------------------------------------------------