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

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

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.

No agreements seems to be reached, the fire is still crackling.

I am now clamping down so that when I am back from my upcoming
vacation things will not have devolved into a worse shape than things
currently are.

Wrt the vacation, some more notes: I will be on vacation coming
Saturday, Dec 15, till Jan 3. That means that my free time in the
evenings of the coming week is spent prepping for that.

Add to that that at work I am currently working on a complex version
bump of our code to sync to a more recent release of the complex
upstream project we are using.

I do not really have the time and mind and brain cycles to mediate
this, nor even to review changes.

Despite the evermore clear need that I will have to.

Thus, here are the rules coming down from me in my role as the main
admin for Tcllib:

(1) The current head of the trunk branch of Tcllib is

    https://core.tcl-lang.org/tcllib/info/63590365a7174ad1

(2) The trunk branch is now __closed__ to any and all commits and
    merges from anybody.

    For the next 4 weeks __nothing__ shall happen on trunk (see above
    about my vacation).

    When I am back from the vacation, and hopefully well rested I am
    opening the trunk to merges. By me. Then I will start and check
    the state of trunk with respect to tests, and such, and go over
    commits in contention.

    Yes, this makes me a bottleneck, i.e. merges are done as I am able
    to review the incoming proposed changes. While I dislike that, it
    looks to be that such a gate is needed.

    Please take the time to either come to an agreeable settlement, or
    to prepare your respective cases of what you believe should
    happen.

(3) Development work can still be done while I am away, however it
    __must__ be done in branches.

    When the work in the branch is considered complete

    - make a ticket and assign to me
    - send me mail
    - both

    I will then review, possibly bounce back to fix whatever I find,
    possibly make my own changes to make it acceptable, if they are
    small enough.

    As a general note I believe that short, focused (feature) branches
    are better than long-running (variant) branches.


For the record, it might also be the time to take the disagreement to
here, the tcllib-devel mailing list

Air it here in the more open than the Tcler's Chat, and connected
#tcl, and slack [1]. 

Actually, discussion about packages and modules to put on the chopping
block ... Tcllib-devel shall be the official place for that. Ditto for
discussions about larger changes of direction for the whole thing.

[1] https://tcl-lang.slack.com/messages/CB29QE8UR/

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