Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Bumping packages: some comments/suggestions
Date: Tue, 15 Oct 2013 09:34:44 +0200	[thread overview]
Message-ID: <20131015093444.4ef3fa17@skate> (raw)
In-Reply-To: <525C6845.50803@mind.be>

Dear Arnout Vandecappelle,

On Mon, 14 Oct 2013 23:55:17 +0200, Arnout Vandecappelle wrote:

> > What I wanted to add in this discussion is this: if there are people
> > out there that have time for some buildroot development but they have
> > no clear goal of their own, they can among others choose between
> > package bumps and fixing autobuild failures.
> > While there certainly is value in package bumping, I hope that not all
> > of these people jump onto the bump-train and instead help with the
> > autobuild failures. We still hope to get to 0 failures at some point,
> > and bumping packages all the time will most of the time only add new
> > problems.
> 
>   I'm also not too hot on version bumping just for the sake of bumping. 
> Version bumps should be done when they're useful for someone, e.g. 
> because a feature or bugfix is added. If it's useful to you, then you'll 
> obviously test if it still works correctly.

I understand this point of view, but on the other hand, it's not really
nice to have packages that have very old versions. For "core" stuff
that isn't necessarily very easy to bump (think Qt, Gtk, X.org and
things like that), it's quite important that the core Buildroot
community keeps that up to date, because this is difficult to do for
newcomers, and this is what people will look at to see if Buildroot is
well-maintained and active.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2013-10-15  7:34 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-13  9:42 [Buildroot] Bumping packages: some comments/suggestions Thomas Petazzoni
2013-10-13 10:44 ` Axel Lin
2013-10-13 13:42   ` Thomas Petazzoni
2013-10-13 15:01     ` Thomas De Schampheleire
2013-10-13 15:06       ` Thomas Petazzoni
2013-10-13 21:04 ` Jerzy Grzegorek
2013-10-14  7:09   ` Thomas Petazzoni
2013-10-14  7:40     ` Jeremy Rosen
2013-10-14  9:30       ` Thomas Petazzoni
2013-10-14  9:38         ` Jeremy Rosen
2013-10-14 10:02           ` Thomas De Schampheleire
2013-10-14 10:04             ` Thomas Petazzoni
2013-10-14 12:58               ` arnaud aujon
2013-10-14 13:56                 ` Thomas Petazzoni
2013-10-14 17:11                   ` arnaud aujon
2013-10-14 21:55             ` Arnout Vandecappelle
2013-10-15  7:34               ` Thomas Petazzoni [this message]
2013-10-15 19:55                 ` Arnout Vandecappelle
2013-10-14 13:45         ` rjbarnet at rockwellcollins.com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20131015093444.4ef3fa17@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox