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: Mon, 14 Oct 2013 11:30:00 +0200	[thread overview]
Message-ID: <20131014113000.73ca82bf@skate> (raw)
In-Reply-To: <1959407319.8772723.1381736446742.JavaMail.root@openwide.fr>

Dear Jeremy Rosen,

On Mon, 14 Oct 2013 09:40:46 +0200 (CEST), Jeremy Rosen wrote:

> two ideas that might or might not be good ideas but are worth discussing
> early :
> 
> * try to automatically build the new version to see if it is an "easy
> bump" or a "hard bump" and document the result
> 
> * ping the last person(s) that touch the package (git has facilities to
> find them, I think it's called git-contribute) when a new version is
> available
> 
> both have good and bad sides, thus worth discussing...

Agreed. But all of this first requires the ability to detect that a new
version is available.

I must say I'm not a big fan of the automatic build, which may
encourage people to do "careless" bump, i.e version bumps without
looking at least a little bit at what changed, and taking a set back by
looking at the version number, or the project web site, to see if the
version bump is small, or major.

For the second one, I agree. We have discussed a few times having the
notion of package maintainers. Probably something that will be worth
discussing at this time.

Best regards,

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

  reply	other threads:[~2013-10-14  9:30 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 [this message]
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
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=20131014113000.73ca82bf@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