Anant Narayanan wrote:
P.P.S. Maybe this is more suited for -project, but everyone knows that
nobody reads that list :-p
Only because nobody posts there. Knock it off. ;P
--
fonts,by design, by neglect
gcc-porting, for
Markus Ullmann wrote:
we had that in the past already yet it didn't solve one problem at hand:
users getting distacted and devs getting nervous b/c the process is
a) undocumented and
b) a bit complex as you have to keep $repo and gentoo-x86 in sync
So giving both (devs and users) an automated wa
Markus Ullmann kirjoitti:
So giving both (devs and users) an automated way of working with that
would help a lot IMHO.
like the user submits using
echangelog "My cool change"
repoman submit
then the dev gets a diff or whatever against current state and then just
does
repoman accept or
rep
Zhang Le schrieb:
IMO giving proxy-maintainer due credit and publicity, meaning make it a formal
position, could solve the very problem Anant's proposal intended to solve.
we had that in the past already yet it didn't solve one problem at hand:
users getting distacted and devs getting nervous b
Sunday, 2. March 2008, Richard Freeman Ви написали:
> George Shapovalov wrote:
> > The good thing about this approach is that it only requires an initial
> > investment of organizing and automating things but does not add any
> > regular work to the devs. In fact, if the "tested" category becomes
>
Hi,
"Santiago M. Mola" <[EMAIL PROTECTED]>:
> On Sat, Mar 1, 2008 at 7:45 PM, Christian Faulhammer
> <[EMAIL PROTECTED]> wrote:
> >
> > What we propose is proper testing and keywording by anyone
> > around...not just team members.
>
> Writing test plans like emacs team does really helps too. I
Richard Freeman wrote:
We might also aim to make it easy for users to mix-and-match levels of
stability by package. I know it is possible already, but perhaps it
could be improved, or pre-canned lists of packages that users might
typically want bleeding-edge vs stable could be compiled.
Tusnam
George Shapovalov wrote:
> The good thing about this approach is that it only requires an initial
> investment of organizing and automating things but does not add any regular
> work to the devs. In fact, if the "tested" category becomes popular enough,
> it can cut the work for stable testers,
On Sat, Mar 1, 2008 at 7:45 PM, Christian Faulhammer <[EMAIL PROTECTED]> wrote:
>
> What we propose is proper testing and keywording by anyone
> around...not just team members.
>
Writing test plans like emacs team does really helps too. I waste too
much time figuring out how to test properly so
Sunday, 2. March 2008, Steve Dibb Ви написали:
> Christian Faulhammer wrote:
> > What we propose is proper testing and keywording by anyone
> > around...not just team members.
>
> I agree... our main problem is manpower -- people actually working on
> the stable bugs. I've tried to do it myself a
Christian Faulhammer wrote:
What we propose is proper testing and keywording by anyone
around...not just team members.
I agree... our main problem is manpower -- people actually working on
the stable bugs. I've tried to do it myself a few times, but each time
it just burns me out to the po
Christian Faulhammer wrote:
>
> What we propose is proper testing and keywording by anyone
> around...not just team members.
>
Thanks for the info - inactive maintainers are obviously a problem.
Maybe the proper approach is for a more "Free-for-all" system like you
suggest, with arch teams focu
Hi,
Richard Freeman <[EMAIL PROTECTED]>:
> > Hope you're not referring to any of my arches because that's not
> > true :) In fact, if i did that, i wouldn't crash the alpha dev box
> > so often, right Tobias?
> I dunno - I just hit bug 211021 today while trying to clean out old
> bugs. Already st
Christian Faulhammer wrote:
[snip]
I agree 100%, thanks for explaining it better than me :P
--
gentoo-dev@lists.gentoo.org mailing list
Hi,
Richard Freeman <[EMAIL PROTECTED]>:
> Raúl Porcel wrote:
> >
> > So it would be cool if they accepted help from other devs who don't
> > have an amd64 system but have access to one and can test stuff. Cla
> > is willing to help.
[...]
> I don't keyword a package stable unless I've done at l
15 matches
Mail list logo
