On Wed, Sep 26, 2018 at 12:38 AM Matthew Miller
wrote:
> On Tue, Sep 25, 2018 at 04:35:09PM -0400, Ben Cotton wrote:
> > With today's Beta release, the release announcement post for Fedora
> > Magazine was not ready. As a result, the announcement went out a
> > little late and then only due to a
At the second Fedora 25 Alpha Go/No-Go Meeting [1][2] that just ended,
it has been agreed by QA, Release Engineering and Development to go live
with the Fedora 25 Alpha.
Fedora 25 Alpha release will be publicly available on August 30, 2016.
Meeting details can be seen here:
[1] Minutes:
https://
On Tue, May 10, 2016 at 4:53 PM, Nikos Roussos
wrote:
> On 05/10/2016 03:12 PM, Ankur Sinha wrote:
> > Hi,
> >
> > I just had an email from someone that installed F23 on a box with an
> > hidpi screen. Apparently, even using the window scaling etc doesn't
> > quite "make it look OK" - has anyone
On Mon, Aug 10, 2015 at 9:19 PM, Adam Williamson
wrote:
> On Mon, 2015-08-10 at 14:43 +0200, Jaroslav Reznik wrote:
>
>> Also for KDE theming, final wallpapers packages has to
>> exist
>> before (it's not that important these days, as we do not change
>> design
On Mon, Aug 10, 2015 at 5:27 PM, Paul W. Frields wrote:
> On Fri, Aug 07, 2015 at 01:23:10PM -0400, Matthew Miller wrote:
>> On Fri, Aug 07, 2015 at 10:03:34AM -0700, Adam Williamson wrote:
>> > The blocker process is not a tool for the rest of the project to use as
>> > a reminder system. It does
On Fri, Aug 7, 2015 at 8:32 PM, Matthew Miller wrote:
>
> On Fri, Aug 07, 2015 at 02:03:31PM -0400, Stephen Gallagher wrote:
> > > Here's a thought: maybe the Fedora background logo GNOME Shell plugin
> > > could detect if running on an Alpha/Beta release (or on Rawhide) and
> > > change appropria
- Original Message -
>
> libappindicator-gtk3 breaks virt-manager's systray functionality, precisely:
> click on virt-manager's systray icon via left mice button -should- quickly
> show or hide Virtual Machine Manager window.
That's a bug and should be fixed.
> If remember correctly, I h
At the Fedora 22 Final Go/No-Go Meeting #2 that just occurred, it was
agreed to Go with the Fedora 22 Final by Fedora QA, Release Engineering
and Development.
Fedora 22 Final will be publicly available on Tuesday, May 26, 2015.
Meeting details can be seen here:
Minutes: http://bit.ly/1Bh2pH1
Log:
Hi!
Today at Fedora 22 Final Go/No-Go meeting it was decided that Fedora 22
Final is No-Go. More details in meeting minutes [1].
As both bugs we accepted as blocker bugs today are already fixed and RC3
compose is requested, we will try to sign-off the final release tomorrow.
If you are willing to
Join us on irc.freenode.net in #fedora-meeting-2 for this important
meeting, wherein we shall determine the readiness of the Fedora 22.
Thursday, May 21, 2015 17:00 UTC (1 PM EDT, 10 AM PDT, 19:00 CEST)
"Before each public release Development, QA and Release Engineering meet
to determine if the r
Fedora 22 Final Release Readiness Meeting.
date: 2015-05-21 place: irc.freenode.net in #fedora-meeting-2
time: 19:00 UTC (3 PM EDT, 12 noon PDT, 21:00 CEST)
This Thursday, May 21, we will meet to make sure we are coordinated
and ready for the Final release of Fedora 22 on Tuesday, May 26, 2015.
P
- Original Message -
> Hi folks.
>
> I'm currently testing the KDE live TC3.
>
> While performing "QA:Testcase_base_startup", I saw that there isn't a
> KSplash theme with artworks from Fedora. The standard 'breeze' is used
> instead. I would not call it a fail, but if I remember right, p
- Original Message -
> > # F22 Blocker Review meeting
> > # Date: 2015-04-28
> > # Time: 1600 UTC
> > # Location: #fedora-blocker-review on irc.freenode.net
> >
> > Sorry for the mix-up yesterday - apparently we do have blockers to
> > review! So I'm proposing we do it at the usual time to
At the Fedora 22 Beta Go/No-Go Meeting #2 that just occurred, it was
agreed to Go with the Fedora 22 Beta by Fedora QA, Release Engineering
and Development.
Fedora 22 Beta will be publicly available on Tuesday, April 21, 2015.
Meeting details can be seen here:
Minutes: http://bit.ly/1HxYmvU
Log:
Join us on irc.freenode.net in #fedora-meeting-2 for this important
meeting, wherein we shall determine the readiness of the Fedora 22 Beta.
Thursday, April 16, 2015 17:00 UTC (1 PM EDT, 10 AM PDT, 19:00 CEST)
"Before each public release Development, QA and Release Engineering meet
to determine i
Today at Go/No-Go meeting it was decided to slip Fedora 22 Beta release
by one week due to unresolved blocker bug [1]. More details in meeting
minutes [2].
As a result, ALL MAJOR MILESTONES, and their dependent tasks, will be
pushed out by one week [3].
The next Go/No-Go meeting is on Thursday, A
Join us on irc.freenode.net in #fedora-meeting-2 for this important
meeting, wherein we shall determine the readiness of the Fedora 22 Beta.
Thursday, April 09, 2015 17:00 UTC (1 PM EDT, 10 AM PDT, 19:00 CEST)
"Before each public release Development, QA and Release Engineering meet
to determine i
Fedora 22 Beta Release Readiness Meeting.
date: 2015-04-09 place: irc.freenode.net in #fedora-meeting-2
time: 19:00 UTC (3 PM EDT, 12 noon PDT, 21:00 CEST)
This Thursday, April 09, we will meet to make sure we are coordinated
and ready for the Beta release of Fedora 22 on Tuesday, April 14, 2015.
- Original Message -
> I am running what I think is an updated F22 system, and as far as I
> can tell, I have screen saver turned off. But if I am away, for not
> sure how long it takes, my workstation goes to a screen for me to
> enter my password to get back to my desktop.
>
> I don't w
At the Fedora 22 Alpha Go/No-Go Meeting #2 that just occurred, it was
agreed to Go with the Fedora 22 Alpha by Fedora QA, Release Engineering
and Development.
Fedora 22 Alpha will be publicly available on Tuesday, March 10, 2015.
Meeting details can be seen here:
Minutes: http://bit.ly/17Y8Je5
Lo
Hi!
Today at Fedora 22 Alpha Go/No-Go meeting it was decided that Fedora 22
Alpha is No-Go as no release candidate is available. More details in
meeting minutes [1].
But as we're looking pretty good and RC1 compose is undergoing right
now (estimate delivery is 3:00 UTC on Friday), we decided to tr
Join us on irc.freenode.net in #fedora-meeting-2 for this important
meeting, wherein we shall determine the readiness of the Fedora 22 Alpha.
Thursday, March 05, 2015 17:00 UTC (12 noon EST, 9 AM PST, 18:00 CET)
"Before each public release Development, QA and Release Engineering meet
to determine
Fedora 22 Alpha Release Readiness Meeting.
date: 2015-03-05 place: irc.freenode.net in #fedora-meeting-2
time: 19:00 UTC (2 PM EST, 11 AM PST, 20:00 CET)
This Thursday, March 05, we will meet to make sure we are coordinated
and ready for the Alpha release of Fedora 22 on Tuesday, March 10, 2015.
- Original Message -
> On 12/12/2014 01:16 PM, Adam Williamson wrote:
> >
> > The other path you can take is to try and convince wwoods to have
> > fedup do distro-sync. The bug reports for that are
> > https://bugzilla.redhat.com/show_bug.cgi?id=892061 and h
> > ttps://github.com/wgwoods/
At the Fedora 21 Final Go/No-Go Meeting that just occurred, it was
agreed to Go with the Fedora 21 Final by Fedora QA, Release Engineering
and Development.
Fedora 21 will be publicly available on Tuesday, December 09, 2014.
Meeting details can be seen here:
Minutes: http://bit.ly/1yjG357
Log: htt
Join us on irc.freenode.net in #fedora-meeting-2 for this important
meeting, wherein we shall determine the readiness of the Fedora 21.
Thursday, December 04, 2014 17:00 UTC (12 AM EST, 9 AM PST, 18:00 CET)
"Before each public release Development, QA and Release Engineering meet
to determine if t
Fedora 21 Final Release Readiness Meeting.
date: 2014-12-04 place: irc.freenode.net in #fedora-meeting-2
time: 19:00 UTC (2 PM EST, 11 AM PST, 20:00 CET)
This Thursday, December 04, we will meet to make sure we are coordinated
and ready for the Final release of Fedora 21 on Tuesday, December 09,
At the Fedora 21 Beta Go/No-Go Meeting #3 that just occurred, it was
agreed to Go with the Fedora 21 Beta by Fedora QA, Release Engineering
and Development.
Fedora 21 Beta will be publicly available on Tuesday, November 04, 2014.
Meeting details can be seen here:
Minutes: http://bit.ly/1tmPWzw
Lo
Join us on irc.freenode.net in #fedora-meeting-2 for this important
meeting, wherein we shall determine the readiness of the Fedora 21 Beta.
Thursday, October 30, 2014 17:00 UTC (1 PM EDT, 10 AM PDT, 18:00 CET)
Reminder: Europe already moved from summer time, winter is coming!
"Before each publi
Today at Go/No-Go meeting it was decided to slip Fedora 21 Beta release
by one week due to unresolved blocker bugs [1]. More details in meeting
minutes [2].
As a result, ALL MAJOR MILESTONES, and their dependent tasks, will be
pushed out by one week [3].
The next Go/No-Go meeting is on Thursday,
Today at Go/No-Go meeting it was decided to slip Fedora 21 Beta release
as we did not have release candidate (RC) available in time. However we
will try one day slip.
The next Go/No-Go meeting is on Friday, Oct 24, the same time at
#fedora-meeting-2 channel.
Any help with release validation once
Join us on irc.freenode.net in #fedora-meeting-2 for this important
meeting, wherein we shall determine the readiness of the Fedora 21 Beta.
Thursday, October 23, 2014 17:00 UTC (1 PM EDT, 10 AM PDT, 19:00 CEST)
"Before each public release Development, QA and Release Engineering meet
to determine
Fedora 21 Beta Release Readiness Meeting.
date: 2014-10-23 place: irc.freenode.net in #fedora-meeting-2
time: 19:00 UTC (3 PM EDT, 12 PM PDT, 21:00 CEST)
This Thursday, October 23, we will meet to make sure we are coordinated
and ready for the Beta release of Fedora 21 on Tuesday, October 28, 201
- Original Message -
>
>
>
> On Mon, 2014-10-06 at 17:02 -0700, Adam Williamson wrote:
> > On Mon, 2014-10-06 at 11:21 -0400, Stephen Gallagher wrote:
> >
> > This is somewhat hard to read as it doesn't diff against the previous
> > text. A mail which just specified what you actually in
At the Fedora 21 Alpha Go/No-Go Meeting #3 that just occurred, it was
agreed to Go with the Fedora 21 Alpha by Fedora QA, Release Engineering
and Development.
Fedora 21 Alpha will be publicly available on Tuesday, September 23, 2014.
"That's one small step for mankind but one giant leap for Fedor
Join us on irc.freenode.net in #fedora-meeting-2 for this important
meeting, wherein we shall determine the readiness of the Fedora 21 Alpha.
Thursday, September 18, 2014 17:00 UTC (1 PM EDT, 10 AM PDT, 19:00 CEST)
"Before each public release Development, QA and Release Engineering meet
to determ
Today at Go/No-Go meeting it was decided to slip Fedora 21 Alpha release
by one week due to unresolved blocker bugs [1] and no release candidate
available. More details in meeting minutes [2].
Quoting Adam, we are moderately optimistic we could possibly actually be
done next week if the netinst st
Join us on irc.freenode.net in #fedora-meeting-2 for this important
meeting, wherein we shall determine the readiness of the Fedora 21 Alpha.
Thursday, September 11, 2014 17:00 UTC (1 PM EDT, 10 AM PDT, 19:00 CEST)
"Before each public release Development, QA and Release Engineering meet
to determ
Today at Go/No-Go meeting it was decided to slip Fedora 21 Alpha release
by one week due to unresolved blocker bugs [1] and no release candidate
available. More details in meeting minutes [2].
As a result, ALL MAJOR MILESTONES, and their dependent tasks, will be
pushed out by one week [3].
The n
==
#fedora-meeting-2: F21 Alpha Readiness Meeting
==
Meeting started by jreznik at 19:01:15 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting-2/2014-09-04/f21-alpha-readiness-
Fedora 21 Alpha Release Readiness Meeting.
date: 2014-09-04 place: irc.freenode.net in #fedora-meeting-2
time: 19:00 UTC (3 PM EDT, 12 PM PDT, 21:00 CEST)
This Thursday, September 04, we will meet to make sure we are coordinated
and ready for the Alpha release of Fedora 21 on Tuesday, September 0
Join us on irc.freenode.net in #fedora-meeting-2 for this important
meeting, wherein we shall determine the readiness of the Fedora 21 Alpha.
Thursday, September 04, 2014 17:00 UTC (1 PM EDT, 10 AM PDT, 19:00 CEST)
"Before each public release Development, QA and Release Engineering meet
to determ
Greetings,!
as you probably noticed, Fedora 21 is still not frozen (Alpha Change
Deadline was planned for this Tuesday, 2014-07-22), due to several
issues we hit while working on the Alpha release (incomplete test
composes etc).
There's also Flock being held in the beginning of August (2014-08-06
- Original Message -
> On Tue, Jul 08, 2014 at 06:20:43PM -0600, Mike Ruckman wrote:
> > # F21 Blocker Review meeting #1
> > # Date: 2014-07-09
> > # Time: 17:00 UTC (13:00 EST, 10:00 PST)
> > # Location: #fedora-blocker-review on irc.freenode.net
>
> Hmmm. This is right at the same time a
- Original Message -
>
>
> On 02/19/2014 02:03 PM, Adam Williamson wrote:
> > There's some significant stuff in this week's FESCo minutes, so I
> > thought it wouldn't hurt to forward it to make people aware. Among the
> > key bits:
> >
> >
> > "AGREED: Open up F21 for ordinary Change pro
> >> So really, I'm fairly convinced at this point that what's needed is
> >> feature chop, it's just a matter of how much which depends on what
> >> quality level expectations the WGs decide upon.
> >
> > What's your plan for moving forward with this?
>
> No plan. But I question whether WG membe
- Original Message -
> On Mon, 2014-02-10 at 01:28 -0500, Matthew Miller wrote:
> > On Sun, Feb 09, 2014 at 06:59:27PM -0800, Adam Williamson wrote:
> > > Oh, couple of things: if anyone feels strongly about the EOL debate
> > > currently happening on devel@, we could meet to talk about tha
- Original Message -
> > Greetings,
> >
> > TL;DR: If you host/manage a meeting in a Fedora channel
> > (#fedora-meeting, #fedora-meeting-1, #fedora-meeting-2), please add it
> > to Fedocal and the Wiki at:
> > https://apps.fedoraproject.org/calendar/fedora-meeting-2/add/
> > https://fedor
At the Fedora 20 Final Go/No-Go Meeting that just occurred, it was
agreed to Go with the Fedora 20 by Fedora QA and Fedora Development.
Fedora Release Engineering to be notified.
"#agreed Fedora QA and Fedora Development are both Go; Fedora Release
Engineering to be notified (with possibility to r
Join us on irc.freenode.net in #fedora-meeting-2 for this important
meeting, wherein we shall determine the readiness of the Fedora 20.
Thursday, December 12, 2013 17:00 UTC (12 PM EST, 9 AM PST, 18:00 CET)
"Before each public release Development, QA and Release Engineering meet
to determine if t
- Original Message -
> # F20 Final Blocker Review meeting #4.5
> # Date: 2013-12-09
> # Time: 17:00 UTC (12:00 EST, 09:00 PST), or directly after QA meeting
> # Location: #fedora-blocker-review on irc.freenode.net
>
> Yes folks, it's time for more Monday blocker review - just like last
> w
- Original Message -
> On 09.12.2013 12:41, Adam Pribyl wrote:
> > On Mon, 9 Dec 2013, Jaroslav Reznik wrote:
> >
> >> - Original Message -
> >>> On 12/08/13 12:05, Christopher Meng wrote:
> >>>> Target to f21:
> >>>
- Original Message -
> On 12/08/13 12:05, Christopher Meng wrote:
> > Target to f21:
> >
> > http://fedoraproject.org/wiki/Changes/SDDMinsteadOfKDM
>
> Thanks I thought the target was F20 since it was in all the previous
> test releases. I guess this is a good explanation
>
> S
Today at Go/No-Go meeting it was decided to slip Fedora 20 Final release
by one week due to unresolved blocker bugs [1] not being fixed and no RC
available by the time of the meeting . The new GA date is now Dec 17.
You can find more details in meeting minutes [2].
The next Go/No-Go meeting is on
Join us on irc.freenode.net in #fedora-meeting-2 for this important
meeting, wherein we shall determine the readiness of the Fedora 20.
Thursday, December 05, 2013 17:00 UTC (12 PM EST, 9 AM PST, 18:00 CET)
"Before each public release Development, QA and Release Engineering meet
to determine if t
At the Fedora 20 Beta Go/No-Go Meeting that just occurred, it was
agreed to Go with the Fedora 20 Beta by Fedora QA and Fedora
Development (with silent approval from me ;-).
Fedora 20 Beta will be publicly available on Tuesday, November 12,
2013.
!!!Schedule adjustment!!!
Due to possible collisi
Join us on irc.freenode.net in #fedora-meeting-2 for this important
meeting, wherein we shall determine the readiness of the Fedora 20 Beta.
This is the third attempt to release Fedora 20 Beta. Currently, RC5 is
under validation, please help if you can [1]. Two new blocker bugs are
proposed.
Thur
Today at Go/No-Go meeting it was decided to slip Fedora 20 Beta release
by one week due to unresolved blocker bugs not being fixed by the time of
meeting.
Due to constrained schedule, shorter slip was considered but with limited
QA resources availability, it was decided to slip for a full week. FE
Join us on irc.freenode.net in #fedora-meeting-2 for this important
meeting, wherein we shall determine the readiness of the Fedora 20 Beta.
This is the second attempt to release Fedora 20 Beta. Currently, we're
waiting for possible RC1 compose.
Thursday, October 31, 2013 17:00 UTC (1 PM EDT, 10
- Original Message -
> * Open Floor (tflink, 17:22:39)
> * ACTION: tflink to discuss pungi fix with dgilmore (tflink,
> 17:23:43)
> * Next blocker review meeting will be 2013-10-30 @ 16:00 UTC (tflink,
> 17:28:35)
Sorry I wasn't able to attend yesterday, I was tempted to joi
Today at Go/No-Go meeting it was decided to slip Fedora 20 Beta release
by one week due to unresolved blocker bugs, see the blocker tracking app [1].
More details in meeting minutes [2].
As a result, ALL MAJOR MILESTONES, and their dependent tasks, will be
pushed out by one week [3]. The new Fedor
Join us on irc.freenode.net in #fedora-meeting-2 for this important
meeting, wherein we shall determine the readiness of the Fedora 20 Beta.
Thursday, October 24, 2013 17:00 UTC (1 PM EDT, 10 AM PDT, 19:00 CEST)
"Before each public release Development, QA and Release Engineering meet
to determine
- Original Message -
> Did an F20 install with KDE. When I went to System Settings to set auto
> login like I always do, it was missing.
>
> So I discovered ssdm was the display manager, and kdm not even
> installed. So I installed KDM, configured auto-login as usual, it still
> wouldn't
- Original Message -
> Adam Williamson (awill...@redhat.com) said:
> > On Tue, 2013-09-24 at 19:51 -0700, Chuck Forsberg WA7KGX wrote:
> > > On 09/24/2013 07:46 PM, Adam Williamson wrote:
> > > > On Tue, 2013-09-24 at 17:08 -0400, Bill Nottingham wrote:
> > > >> Łukasz Posadowski (m...@luka
At the Fedora 20 Alpha Go/No-Go Meeting #2 that just occurred, it was
agreed to Go with the Fedora 20 Alpha by Fedora QA, Release Engineering
and Development.
Fedora 20 Alpha will be publicly available on Tuesday, September 24, 2013.
Meeting details can be seen here:
Minutes: http://bit.ly/16chiA
Join us on irc.freenode.net in #fedora-meeting-2 for this important
meeting, wherein we shall determine the readiness of the Fedora 20 Alpha.
This is the second attempt to release Fedora 20 Alpha.
Thursday, September 19, 2013 17:00 UTC (1 PM EDT, 10 AM PDT, 19:00 CEST)
"Before each public relea
- Original Message -
> On Thu, Sep 12, 2013 at 04:46:17PM -0500, Dennis Gilmore wrote:
> > ami-1bb5fc72 : us-east-1 image for i386
>
> This still doesn't boot. (We're working on it.)
Matt,
any news on this?
Thanks
Jaroslav
> --
> Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁
> --
>
- Original Message -
> Dne neděle, 8. září 2013 2:09:38 CEST, Sandro Mani napsal(a):
>
> > On 08.09.2013 01:52, Ed Greshko wrote:
> >> I just installed F20-TC4 from DVD selecting the KDE desktop.
> >> To my surprise there was no kdm installed. Instead, I found
> >> sddm running.
> >>
>
Today at Go/No-Go meeting it was decided to slip Fedora 20 Alpha release
by one week due to two unresolved blocker bugs, see the blocker tracking app
[1].
Otherwise we think we have pretty solid foundation for Alpha. More details in
meeting minutes [2].
As a result, ALL MAJOR MILESTONES, and the
Join us on irc.freenode.net in #fedora-meeting-1 for this important
meeting, wherein we shall determine the readiness of the Fedora 20 Alpha.
Thursday, September 12, 2013 17:00 UTC (1 PM EDT, 10 AM PDT, 19:00 CEST)
"Before each public release Development, QA and Release Engineering meet
to determ
- Original Message -
> On Mon, 2013-08-26 at 15:56 +0300, Vasilis Keramidas wrote:
> > I believe the second suggestion is the best. In this way:
> > a) A different wallpaper will be used to avoid confusion (the F19
> > supplementary wallpapers sounds as a good idea)
> > b) The design team w
Hi,
due to bad communication, the deadline for F20 name was extended to
this Friday but this means the decision will probably come too late
for Design team to create artwork for Alpha and it's one of the
blocking criterion. The idea is to have different artwork to the
previous releases, so users a
- Original Message -
> On Fri, 2013-07-19 at 07:32 -0400, Kamil Paral wrote:
> > > "A working mechanism to create a user account must be clearly presented
> > > during installation and/or first boot of the installed system.
> > >
> > > A system installed with a release-blocking desktop mus
- Original Message -
> On 2013-06-21 10:41, Kevin Fenzi wrote:
> > On Fri, 21 Jun 2013 10:37:01 -0700
> > Adam Williamson wrote:
> >
> >> So, just a phrasing thing, the criteria are mostly written in the form
> >> 'XXX must be the case', not 'XXX is added to the blocker list'. So
> >> per
At the Fedora 19 Final Go/No-Go Meeting that just occurred, it was
agreed to Go with the Fedora 19 by Fedora QA, development, release
engineering and FPM.
Fedora 19 will be publicly available on Tuesday, July 02, 2013.
Thank you everyone for heroic effort on this release!
Meeting details can be
Join us on irc.freenode.net in #fedora-meeting-2 for this important
meeting, wherein we shall determine the readiness of the Fedora 19.
Thursday, June 27, 2013 17:00 UTC (1 PM EDT, 10 AM PDT, 19:00 CEST)
"Before each public release Development, QA and Release Engineering meet
to determine if the
- Original Message -
> - Original Message -
> > On Sat, 2013-06-22 at 22:17 -0700, Adam Williamson wrote:
> > > On Sat, 2013-06-22 at 11:00 -0400, Matthias Clasen wrote:
> > > > On Fri, 2013-06-21 at 14:14 -0700, Adam Williamson wrote:
> > > >
> > > > >
> > > > > https://bugzilla.
- Original Message -
> On Sat, 2013-06-22 at 22:17 -0700, Adam Williamson wrote:
> > On Sat, 2013-06-22 at 11:00 -0400, Matthias Clasen wrote:
> > > On Fri, 2013-06-21 at 14:14 -0700, Adam Williamson wrote:
> > >
> > > >
> > > > https://bugzilla.redhat.com/show_bug.cgi?id=958426 - "19 Fin
- Original Message -
> > On Thu, 2013-06-20 at 09:19 -0400, Kamil Paral wrote:
> > > Based on Josef's script, this is the list of test cases that really need
> > > testing (not tested at all during Final, or tested long time ago):
> > >
> > > QA:Testcase_USB_stick_Live_luc
> >
> > The fac
- Original Message -
> On Fri, 14 Jun 2013 16:33:50 -0700
> Adam Williamson wrote:
>
> > Many thanks to tflink, who is working on a little script to do this. I
> > won't post it until he thinks it's ready, but we can provide the list.
>
> Yeah, the script is really user unfriendly right
- Original Message -
> On Wed, 2013-05-22 at 00:42 -0400, Andre Robatino wrote:
> > NOTE: The 64-bit Live LXDE is over its size target (700 MiB) and will
> > not fit on a standard 700 MiB CD.
> >
> > As per the Fedora 19 schedule [1], Fedora 19 Beta Release Candidate 3
> > (RC3) is now ava
Join us on irc.freenode.net in #fedora-meeting-2 for this important
meeting, wherein we shall determine the readiness of the Fedora 19 Beta.
Thursday, May 23, 2013 17:00 UTC (1 PM EDT, 10 AM PDT, 19:00 CEST)
"Before each public release Development, QA and Release Engineering meet
to determine if
- Original Message -
>
> # F19 Beta Blocker Review meeting #5
> # Date: 2013-05-13
> # Time: 16:00 UTC (12:00 EDT, 09:00 PDT) (after QA meeting)
> # Location: #fedora-blocker-review on irc.freenode.net
I'll hope I'll make at least blocker review today but I can't promise it
as I'll be tra
Hi!
In the Alpha times, we had some disputes in terms of how to handle secondary
architecture's blockers (in that case PPC). If we should grant the freeze
exception same way as we do for all other composes that falls under
"non-release-blocking image" or if secondary arches are a different
beasts
- Original Message -
> On 05/06/2013 05:44 AM, Igor Gnatenko wrote:
> > https://bugzilla.redhat.com/show_bug.cgi?id=903136
> > This bug affected ALL ThinkPads of 2012!
> > Can you add in blocker release bugs ?
>
> Screen brightness is not considered a blocker + you should be testing
> this
- Original Message -
> # Fedora Quality Assurance Meeting
> # Date: 2013-04-29
> # Time: 15:00 UTC
> (https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
> # Location: #fedora-meeting on irc.freenode.net
>
> Greetings testers!
>
> It's meeting time again today/tomorrow! We'll start cy
- Original Message -
> On Sat, 20 Apr 2013 12:46:29 -0500
> Bruno Wolff III wrote:
>
> > On Sat, Apr 20, 2013 at 10:59:10 -0600,
> >Kevin Fenzi wrote:
> > >
> > >What other items were you hoping for? :)
> >
> > Another odd area is things that were pulled in during the freeze.
> > Th
- Original Message -
> On 04/18/2013 01:49 AM, Michael Cronenworth wrote:
> >
> > I cannot run any application, including anaconda. Perhaps if I let it
> > sit overnight anaconda might display, but then I'd have to wait a week
> > for it to install at this pace.
> >
> > I managed to get SSH
Join us on irc.freenode.net in #fedora-meeting-2 for this important
meeting, wherein we shall determine the readiness of the Fedora 19 Alpha.
Thursday, April 18, 2013 17:00 UTC (1 PM EDT, 10 AM PDT, 19:00 CEST)
"Before each public release Development, QA and Release Engineering meet
to determine
Today at Go/No-Go meeting it was decided to slip Fedora 19 Alpha release
by one week due to unresolved UEFI bugs, see the blocker tracking app [1].
Otherwise we think we have pretty solid foundation for Alpha, please help
us to identify the real impact of the UEFI issues. More details in meeting
- Original Message -
> Hi folks! Time for the first blocker status mail of the Fedora 19 cycle.
> The tl;dr summary:
Hi Adam,
thanks for summary. Updates follows.
> Input needed from blocker voters and developers on:
>
> * https://bugzilla.redhat.com/show_bug.cgi?id=947142
Three more ar
Join us on irc.freenode.net in #fedora-meeting-1 for this important
meeting, wherein we shall determine the readiness of the Fedora 19 Alpha.
Thursday, April 11, 2013 17:00 UTC (1 PM EDT, 10 AM PDT, 19:00 CEST)
"Before each public release Development, QA and Release Engineering meet
to determine
- Original Message -
> Hi, folks. Just to let everyone know - it didn't seem worth
> requesting a
> TC1 today. bcl and I have been building test images all day and have
> a
> decent handle on the current status. bcl's latest test boot.iso:
Thanks for heads up.
> https://alt.fedoraproject.
- Original Message -
> Hey, folks. CCing anaconda list on this one due to the changes to the
> partitioning requirements (see below) - please send replies to test@,
> though, to avoid a thread fork.
>
> Further to my previous mail -
> https://lists.fedoraproject.org/pipermail/test/2013-Mar
- Original Message -
> Just a heads-up: abrt for F19 is currently busted for two reasons.
> Numero Uno:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=922433
>
> seriously, why the hell did we not figure this release name was going
> to
> break the world?
Well, we joked about it but yea
- Original Message -
> Hey folks! So I had an action item from the meeting on Monday:
>
> "adamw to draft up changes to the test day process docs to
> accommodate
> test days being on any day, test day co-ordinator to ensure they're
> balanced out"
>
> In fact, though, looking at the wiki
- Original Message -
> Hi, folks. There was some discussion of this at the meeting on
> Monday,
> but no-one really gave much input, so I wanted to run these ideas by
> the
> list before we commit to them. Let's look at the image compose
> schedule
> for F19.
>
> As things stand, the F19 c
- Original Message -
> On 21/02/13 01:11 AM, Jaroslav Reznik wrote:
> > - Original Message -
> >> We discussed a few possible changes to the blocker bug meeting
> >> process
> >> at the QA meeting this week. It was agreed that I'd draft up t
- Original Message -
> - Original Message -
> > Hey, Jaroslav - sorry I didn't catch this before, but can you edit
> > the
> > F19 QA schedule and move all the blocker review meetings to
> > Wednesdays?
> > We started doing the meetings on Wednesdays in the last cycle and
> > it
> >
Hi all! (and sorry for post to sooo many lists)
As we already have a final schedule (for a three weeks now) and we're
getting closer to release windmills - I'd like to make the schedule
easy to use for everyone (and that means for me too), to be sure
it makes sense etc. And inform you about recent
1 - 100 of 151 matches
Mail list logo
