Re: core-update scope

2024-12-14 Thread Maxim Cournoyer
Hello, Andreas Enge writes: > Hello Leo, > > Am Sat, Sep 07, 2024 at 01:47:03PM -0400 schrieb Leo Famulari: >> I agree, we don't have to have a team for this. I'm not sure anyone else >> cares about the "media" packages as a whole. But if there is interest, >> that's good too. > > as an outsider

Re: core-update scope

2024-09-08 Thread Andreas Enge
Hello Leo, Am Sat, Sep 07, 2024 at 01:47:03PM -0400 schrieb Leo Famulari: > I agree, we don't have to have a team for this. I'm not sure anyone else > cares about the "media" packages as a whole. But if there is interest, > that's good too. as an outsider, I would just like to chime in that I lik

Re: core-update scope

2024-09-07 Thread Leo Famulari
On Wed, Sep 04, 2024 at 10:01:28AM +0100, Christopher Baines wrote: > It doesn't seem like a core package to me, but also every branch doesn't > need a team. It's fine to have a ffmpeg or ffmpeg-update branch and just > bump that one package. > > There's a balance to be struck in grouping packages

Re: core-update scope

2024-09-04 Thread Christopher Baines
Andy Tai writes: > Hi, shall changes to non-core packages like ffmpeg still be in the > scope of core-updates? > > ffmpeg, for example, is no where near the core of the GNU system like > glibc, but still it is widely dependent upon. But it would make no > sense to have a ffmpeg-team because it

Re: core-update scope

2024-09-02 Thread Leo Famulari
On Sat, Aug 31, 2024 at 02:32:01PM -0700, Andy Tai wrote: > Hi, shall changes to non-core packages like ffmpeg still be in the > scope of core-updates? > > ffmpeg, for example, is no where near the core of the GNU system like > glibc, but still it is widely dependent upon. But it would make no >