public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Stephen P. Becker" <geoman@gentoo.org>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] Please follow keywording policy
Date: Wed, 09 Mar 2005 11:37:45 -0500	[thread overview]
Message-ID: <422F2659.4080005@gentoo.org> (raw)
In-Reply-To: <422F0D2E.1040301@gentoo.org>

> Ok, I could understand that none of the mips team are online when I 
> want, but how about the bug mentioned above? One month I 
> waited/begged/threat!!! For what? For some lousy script updates, which 
> is not arch dependent anyway!

There are lots of open bugs, sometimes they slip under the radar.  And 
*never* assume scripts are arch independant.  See more below...

> Not every package that I maintain is tested by me! How can I test a dsl 
> driver when I have no such device!

Do you have somebody in your herd test it that does have such a device? 
  If not, you shouldn't be maintaining it.

> I apply the good old rule that if a package has no open bugs for a 
> month, it will be marked as stable.

This if fine if you can vouch that it works.  None of us could say 
rp-pppoe works.  What is more, just because it works on x86 doesn't mean 
there aren't problems with other arches.  Even things like 
perl/python/<insert favorite scripting language here> scripts are 
included in this statement.  If I remember correctly, ciaran even ran 
into a non-portable vim script at one point.

That said, since you are the package maintainer, you should be 
practically the world's expert on this package.  You should know if 
there are potential endian problems.  You should be talking to upstream 
to find these sorts of things out.  If you have full confidence that it 
should be stable on our arch, mark it stable.  Seeing as you see fit to 
break policy and mark your dsl driver package stable even though you 
can't test it, then how is this any different?  Keep in mind that I'm 
pretty sure there are developer machines available for (almost) every 
arch now.  Package maintainers should use this resource for testing 
purposes.

> If I would do things you way, in this moment net-dialup would have at 
> least 100 opened bugs with no one carrying about them. I urge you to 
> look in bugzilla to see how many rightfully complaints are there 
> regarding my work. Not as if I consider less about a dev who made a 
> mistake (only who do nothing, does no mistakes)...

You are missing the point.

> It is OK to want to make more than a simple compile test, but from this 
> to doing nothing when a fellow dev ask you to IS a big distance! A 
> convenient excuse, nothing more...

Convenient excuse for what?  Do you think we singled you out and said, 
"hey, I don't like that mrness...we're just going to ignore his package" ?

> I didn't wanted to get so involved in this bug, but invalid bug reports 
> started by the transition from -r2 are killing me. In rest, what do I 
> care that your arch is outdated!

I don't quite see what the big deal is anyway.  When I looked, the last 
stable version of that package was from last november or so.  If we were 
a year out of date or something, that might be a different story.  We do 
have a script that emails all of the mips team with outdated packages 
from time to time, however we have a shortage of devs and time, so 
non-crucial stuff that none of the mips team uses like rp-pppoe 
typically gets pushed back.

Steve



--
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2005-03-09 16:37 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-09  1:55 [gentoo-dev] Please follow keywording policy Jason Wever
2005-03-09  2:00 ` Hasan Khalil
2005-03-09  7:38 ` Alin Nastac
2005-03-09 13:39   ` Stephen P. Becker
2005-03-09 14:50     ` Alin Nastac
2005-03-09 16:22       ` Ciaran McCreesh
2005-03-09 17:38         ` Alin Nastac
2005-03-09 18:38           ` Ciaran McCreesh
2005-03-09 18:56             ` Alin Nastac
2005-03-09 19:10               ` Stefan Schweizer
2005-03-09 19:10                 ` Stefan Schweizer
2005-03-09 21:30                 ` Luis F. Araujo
2005-03-09 22:57                 ` Alin Nastac
2005-03-09 23:27                   ` Stephen P. Becker
2005-03-10  0:50                     ` Donnie Berkholz
2005-03-10  0:18                       ` Daniel Goller
2005-03-09 23:36                   ` Jason Wever
2005-03-09 23:42                   ` Aron Griffis
2005-03-10  7:54                     ` Alin Nastac
2005-03-10  8:27                       ` Ciaran McCreesh
2005-03-10 15:54                         ` Chris Gianelloni
2005-03-10 15:52                       ` Chris Gianelloni
2005-03-10  4:34                   ` Grant Goodyear
2005-03-10  8:36                     ` Alin Nastac
2005-03-10 13:14                       ` Ciaran McCreesh
2005-03-10 16:00                       ` Chris Gianelloni
2005-03-10 19:00                         ` Alin Nastac
2005-03-10 19:33                           ` Chris Gianelloni
2005-03-10 21:25                             ` John Myers
2005-03-10 15:38                   ` Chris Gianelloni
2005-03-09 19:18               ` Patrick Lauer
2005-03-09 19:43                 ` Stefan Schweizer
2005-03-09 19:56                   ` Patrick Lauer
2005-03-10  0:55               ` Jon Portnoy
2005-03-10  8:07                 ` Alin Nastac
2005-03-09 19:20             ` Chris Gianelloni
2005-03-09 16:37       ` Stephen P. Becker [this message]
2005-03-09 16:43   ` Chris Gianelloni
2005-03-09 17:40     ` Alin Nastac

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=422F2659.4080005@gentoo.org \
    --to=geoman@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    --cc=gentoo-dev@robin.gentoo.org \
    /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