From 2dcb68dfc5ea1c816f3eee84b2d989ab227c59da Mon Sep 17 00:00:00 2001 From: Damien Goutte-Gattat Date: Sat, 20 Jun 2020 15:53:45 +0100 Subject: [PATCH] Update README. --- README.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/README.md b/README.md index e5c839ab..b9e773a5 100644 --- a/README.md +++ b/README.md @@ -12,13 +12,13 @@ version of Slackware. Normally, only one branch is “active” at any given tim the branch for whatever version of Slackware I am currently using—I do not maintain my SlackBuilds for other versions. -The current active branch is *current-20191101*. This branch targets a -snapshot of Slackware-current taken on 1 November 2019. Note that I do not -*track* -current: those SlackBuilds will *not* be regularly updated to reflect -changes happening on -current. Instead, after an arbitrarily defined period of -time, I will take another snapshot of -current and use that as the new target -version, and progressively update all the SlackBuilds accordingly. I will -repeat that until Slackware-15.0 is released. +The current active branch is *current-20200608*. This branch targets a +snapshot of Slackware-current taken on 8 June 2020. Note that I do not *track* +-current: those SlackBuilds will *not* be regularly updated to reflect changes +happening on -current. Instead, after an arbitrarily defined period of time, I +will take another snapshot of -current and use that as the new target version, +and progressively update all the SlackBuilds accordingly. I will repeat that +until Slackware-15.0 is released. The *slackware-14.2* branch is now mostly inactive as I have switched to -current. However, as an exception to the above rule about maintaining