On Mon, Jun 26, 2023 at 10:21 AM Sumantro Mukherjee
wrote:
> Thanks a lot Kamil and Adamw!!
> Can I go and publish this under the Beta criteria? :)
> @Kamil Paral it will be awesome, if you can point me
> to the correct criteria template , please?
>
Thumbs up from me. Here's the criterion
On Tue, Jun 20, 2023 at 4:14 PM Adam Williamson
wrote:
> On Tue, 2023-06-20 at 12:30 +0200, Kamil Paral wrote:
> > On Tue, Jun 20, 2023 at 12:07 PM Adam Williamson <
> adamw...@fedoraproject.org>
> > wrote:
> >
> > > ~
> > > For any release-blocking deliverable whose default
On Tue, 2023-06-20 at 12:30 +0200, Kamil Paral wrote:
> On Tue, Jun 20, 2023 at 12:07 PM Adam Williamson
> wrote:
>
> > ~
> > For any release-blocking deliverable whose default deployment includes
> > Toolbx, the {{command|toolbox}} CLI must be able to list existing
> >
On Tue, Jun 20, 2023 at 12:07 PM Adam Williamson
wrote:
> ~
> For any release-blocking deliverable whose default deployment includes
> Toolbx, the {{command|toolbox}} CLI must be able to list existing
> containers.
One nitpick, it's not clear whether "list" means listing
On Fri, 2023-06-09 at 09:24 +0530, Sumantro Mukherjee wrote:
> The new proposed criteria taking Kamil's and Adam's suggestions goes as
> follows :
>
> Once people are okay with it, I can go ahead and add this to the criterion?
>
> ~
> For any release-blocking deliverable
The new proposed criteria taking Kamil's and Adam's suggestions goes as
follows :
Once people are okay with it, I can go ahead and add this to the criterion?
~
For any release-blocking deliverable whose default deployment includes
Toolbx,
the toolbox CLI must be able to list
On Thu, Jun 8, 2023 at 7:07 AM Sumantro Mukherjee
wrote:
> FESCo has approved[0] this changeset and now the criterion needs to be in
> place. I will gather all the knowledge and the corrections that have been
> talked about in this thread and start a fresh one for voting?
>
> [0]
On Tue, May 2, 2023 at 4:46 PM Kamil Paral wrote:
> On Tue, May 2, 2023 at 4:48 AM Sumantro Mukherjee
> wrote:
>
>> Debarshi and I decided to re-write the whole thing as a changeset[0].
>>
>
> Great, I think this is the best approach.
>
>
>> The revised criterion I have now stands as:
>>
>
>
On Wed, 2023-05-03 at 15:08 +0200, Kamil Paral wrote:
>
> > and must keep
> > being updated like for branchpoints, beta and final. Missing images or
> > broken images, will be blocking the release.
> >
>
> I think this is just assumed, as described above, for each release-blocking
> artifact.
On Fri, May 5, 2023 at 6:39 AM Sumantro Mukherjee
wrote:
> Adam & Kamil, since my criteria starts with"for each release-blocking
> artifact", do you folks think its a good idea to site the criterion? or at
> least have it? I am not able to find it as well.
>
You mean "cite", right? :-) Cite
On Wed, May 3, 2023 at 6:38 PM Kamil Paral wrote:
> On Tue, May 2, 2023 at 4:48 AM Sumantro Mukherjee
> wrote:
>
>> The revised criterion I have now stands as:
>>
>>
>> For any release-blocking deliverable whose default deployment includes
>> toolbx, the toolbox CLI must be able to list
On Tue, May 2, 2023 at 4:48 AM Sumantro Mukherjee
wrote:
> The revised criterion I have now stands as:
>
>
> For any release-blocking deliverable whose default deployment includes
> toolbx, the toolbox CLI must be able to list existing containers,
>
toolbx -> Toolbx
to denote you're
On Tue, 2023-05-02 at 14:20 -0700, Kevin Fenzi wrote:
> On Tue, May 02, 2023 at 08:18:07AM +0530, Sumantro Mukherjee wrote:
> > Hello
> >
> >
> > This has been silent for a long time now but here's the update.
> > Debarshi and I decided to re-write the whole thing as a changeset[0].
> > We DO
On Tue, May 02, 2023 at 08:18:07AM +0530, Sumantro Mukherjee wrote:
> Hello
>
>
> This has been silent for a long time now but here's the update.
> Debarshi and I decided to re-write the whole thing as a changeset[0].
> We DO care about not just the rpm but also the OCI image that we ship
> with
On Tue, May 2, 2023, 16:46 Kamil Paral wrote:
> On Tue, May 2, 2023 at 4:48 AM Sumantro Mukherjee
> wrote:
>
>> Debarshi and I decided to re-write the whole thing as a changeset[0].
>>
>
> Great, I think this is the best approach.
>
>
>> The revised criterion I have now stands as:
>>
>
> Does
On Tue, May 2, 2023 at 4:48 AM Sumantro Mukherjee
wrote:
> Debarshi and I decided to re-write the whole thing as a changeset[0].
>
Great, I think this is the best approach.
> The revised criterion I have now stands as:
>
Does it make sense to wait for the FESCo approval before we finalize
On Tue, May 2, 2023 at 12:00 AM Sumantro Mukherjee wrote:
>
>
>
> On Tue, May 2, 2023 at 9:04 AM Neal Gompa wrote:
>>
>> On Mon, May 1, 2023 at 10:48 PM Sumantro Mukherjee
>> wrote:
>> >
>> > Hello
>> >
>> >
>> > This has been silent for a long time now but here's the update.
>> > Debarshi and
On Tue, May 2, 2023 at 9:04 AM Neal Gompa wrote:
> On Mon, May 1, 2023 at 10:48 PM Sumantro Mukherjee
> wrote:
> >
> > Hello
> >
> >
> > This has been silent for a long time now but here's the update.
> > Debarshi and I decided to re-write the whole thing as a changeset[0].
> > We DO care about
On Mon, May 1, 2023 at 10:48 PM Sumantro Mukherjee wrote:
>
> Hello
>
>
> This has been silent for a long time now but here's the update.
> Debarshi and I decided to re-write the whole thing as a changeset[0].
> We DO care about not just the rpm but also the OCI image that we ship
> with Toolbx.
Hello
This has been silent for a long time now but here's the update.
Debarshi and I decided to re-write the whole thing as a changeset[0].
We DO care about not just the rpm but also the OCI image that we ship
with Toolbx. As a result, we filed a releng ticket[1] where
we justified the
>
> ~
> For any release-blocking deliverable whose default deployment includes
> toolbox, it must be
> possible to list existing containers, enter them, and create a new one.
>
>
> Footnote - "What does this cover?":
> Toolbox
On Mon, Apr 17, 2023 at 2:44 PM Kamil Paral wrote:
> On Wed, Apr 12, 2023 at 5:57 AM Sumantro Mukherjee
> wrote:
>
>> There is a push from the
>> Dekstop team to have toolbox as a default app in the installer iso as
>> well.
>
>
> The 'toolbox' package is already installed by default. Or do you
On Wed, Apr 12, 2023 at 5:57 AM Sumantro Mukherjee
wrote:
> There is a push from the
> Dekstop team to have toolbox as a default app in the installer iso as
> well.
The 'toolbox' package is already installed by default. Or do you mean some
related GUI app?
>
> Toolbox aka Toolbx
On Wed, 2023-04-12 at 09:00 -0400, Ben Cotton wrote:
>
> > Footnote - "What does this cover?":
> > Toolbox's general functionality as covered by this test cases
> > https://fedoraproject.org/wiki/QA:Testcase_toolbox
>
> The test case seems to be much narrower than the text of the criterion
>
On Tue, Apr 11, 2023 at 11:56 PM Sumantro Mukherjee wrote:
>
> Toolbox aka Toolbx should be usable.
As a style matter, let's just cut this sentence. "usable" is vague and
the next sentence offers more clarity.
> Toolbox should be able to list,
> create and provide the desired containerized
Related to a recently proposed blocker [0], I propose a new release
criterion which would cover that case. There is a push from the
Dekstop team to have toolbox as a default app in the installer iso as
well. Here it is:
Toolbox aka Toolbx should be usable. Toolbox should be able to
26 matches
Mail list logo
