From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jason Self" Subject: Upstream Release Monitoring Date: Thu, 11 Sep 2014 20:31:00 -0700 (PDT) Message-ID: <1410492660.18719@bluehome.net> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="bound1410492660" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:39120) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XSHZm-0004f7-Q6 for guix-devel@gnu.org; Thu, 11 Sep 2014 23:31:16 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XSHZg-0002wK-Mk for guix-devel@gnu.org; Thu, 11 Sep 2014 23:31:10 -0400 Received: from q-static-134-174.avvanta.com ([206.124.134.174]:47535 helo=bluehome.net) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XSHZg-0002wC-GI for guix-devel@gnu.org; Thu, 11 Sep 2014 23:31:04 -0400 List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: guix-devel@gnu.org This is a multi-part message in MIME format. --bound1410492660 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit With the number of packages available using Guix (and it seems to keep increasing) keeping up on the latest upstream versions manually is gonna be a pain. :) Shouldn't the checking be automated in some way? One idea might be to create a bug in the GNU Bug Tracker when a new upstream release is detected. --bound1410492660--