On Thu, 2023-04-06 at 15:59 +0200, Kamil Paral wrote:
> On Tue, Apr 4, 2023 at 6:05 PM Adam Williamson
> wrote:
>
> > On Tue, 2023-04-04 at 15:21 +0200, Kamil Paral wrote:
> > > On Mon, Apr 3, 2023 at 5:34 PM Kamil Paral wrote:
> > >
> > > > At today's QA meeting, nobody had any further
On Tue, Apr 4, 2023 at 6:05 PM Adam Williamson
wrote:
> On Tue, 2023-04-04 at 15:21 +0200, Kamil Paral wrote:
> > On Mon, Apr 3, 2023 at 5:34 PM Kamil Paral wrote:
> >
> > > At today's QA meeting, nobody had any further objections. If there's no
> > > additional feedback, I'll push it live
On Tue, 2023-04-04 at 15:21 +0200, Kamil Paral wrote:
> On Mon, Apr 3, 2023 at 5:34 PM Kamil Paral wrote:
>
> > At today's QA meeting, nobody had any further objections. If there's no
> > additional feedback, I'll push it live tomorrow.
> >
>
> This is now live:
>
On Mon, Apr 3, 2023 at 5:34 PM Kamil Paral wrote:
> At today's QA meeting, nobody had any further objections. If there's no
> additional feedback, I'll push it live tomorrow.
>
This is now live:
https://fedoraproject.org/w/index.php?title=Basic_Release_Criteria=revision=673055=650015
On Wed, Mar 22, 2023 at 8:57 AM Kamil Paral wrote:
> Here's a second draft. I took feedback here and also from the QA meeting
> [1]. The split between the milestones makes this harder to read and
> compare. If you have better ideas on how to do it, please tell me :-)
>
>
> == Basic
On Wed, Mar 22, 2023 at 1:17 PM pmkel...@frontier.com
wrote:
>
>
> On 3/22/23 03:57, Kamil Paral wrote:
> > Here's a second draft. I took feedback here and also from the QA meeting
> > [1]. The split between the milestones makes this harder to read and
> > compare. If you have better ideas on
On Wed, Mar 22, 2023 at 3:58 AM Kamil Paral wrote:
>
> Here's a second draft. I took feedback here and also from the QA meeting [1].
> The split between the milestones makes this harder to read and compare. If
> you have better ideas on how to do it, please tell me :-)
I like it.
--
Ben
On 3/22/23 03:57, Kamil Paral wrote:
Here's a second draft. I took feedback here and also from the QA meeting
[1]. The split between the milestones makes this harder to read and
compare. If you have better ideas on how to do it, please tell me :-)
The only suggestion I have is for the foot
Here's a second draft. I took feedback here and also from the QA meeting
[1]. The split between the milestones makes this harder to read and
compare. If you have better ideas on how to do it, please tell me :-)
== Basic milestone ==
For each release-blocking desktop, the desktop
On Fri, Mar 17, 2023 at 1:59 PM Ben Cotton wrote:
> On Fri, Mar 17, 2023 at 5:48 AM Kamil Paral wrote:
> >
> > The desktop environment must work correctly when displaying common
> application content - that includes regular application windows, video
> output, games and possibly other common
I could probably live with both versions, the Ben's one working a little
more straightforward to me.
On Fri, Mar 17, 2023 at 1:59 PM Ben Cotton wrote:
> On Fri, Mar 17, 2023 at 5:48 AM Kamil Paral wrote:
> >
> > The desktop environment must work correctly when displaying common
> application
On Fri, Mar 17, 2023 at 5:48 AM Kamil Paral wrote:
>
> The desktop environment must work correctly when displaying common
> application content - that includes regular application windows, video
> output, games and possibly other common content. Regular operations like
> windows
On Fri, Mar 17, 2023 at 5:48 AM Kamil Paral wrote:
>
> Related to a recently proposed blocker [1][2], I propose a new release
> criterion which would cover such cases. Here it is:
>
>
> The desktop environment must work correctly when displaying common
> application content - that
Related to a recently proposed blocker [1][2], I propose a new release
criterion which would cover such cases. Here it is:
The desktop environment must work correctly when displaying common
application content - that includes regular application windows, video
output, games and
14 matches
Mail list logo
