[Test-Announce] Fedora 22 Alpha status is Go, release on March 10, 2015

[Jaroslav Reznik]

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
Log: http://bit.ly/1Em9JXo

Thanks everyone! It's pretty solid Alpha release and on time :).
Jaroslav
_______________________________________________
test-announce mailing list
test-announce(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/test-announce

[Chuck Forsberg WA7KGX]

Testing of today's netinst:   64 bit wine still broken
        32 bit wine works on older machine
        32 bit netinst no X on 3770-k/GTX970


On 03/06/2015 07:55 AM, Jaroslav Reznik wrote:
>  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
>  Log: http://bit.ly/1Em9JXo
>
>  Thanks everyone! It's pretty solid Alpha release and on time :).
>  Jaroslav
>  _______________________________________________
>  test-announce mailing list
>  test-announce(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/test-announce 
-- 
      Chuck Forsberg WA7KGX   caf(a)omen.com   www.omen.com
Developer of Industrial ZMODEM(Tm) for Embedded Applications
   Omen Technology Inc      "The High Reliability Software"
10255 NW Old Cornelius Pass Portland OR 97231   503-614-0430

[Michael Schwendt]

On Fri, 6 Mar 2015 10:55:53 -0500 (EST), Jaroslav Reznik wrote:

>  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
>  Log: http://bit.ly/1Em9JXo 
"404 Not Found" for both!

These work:

http://meetbot.fedoraproject.org/fedora-meeting-2/2015-03-06/
 ->
http://meetbot.fedoraproject.org/fedora-meeting-2/2015-03-06/f22_alpha_go...

| 15:31:31 * nirik sees another bug mentioned on list.

Good.

| 15:31:51 <nirik> but no one bothered to propose it...

No good.  Anaconda maintainers not either? D'oh!

| 15:32:01 <nirik> https://bugzilla.redhat.com/show_bug.cgi?id=1196397
| 15:32:36 <nirik> ok, it looks like a weird case...

Not at all.

| 15:32:43 <nirik> trying to reuse some existing preformatted /

_Unformatted_ in my case. As mentioned in the ticket. A typical
install scenario.

>  Thanks everyone! It's pretty solid Alpha release and on time :).
LOL! It failed to install here. :(

I only hope it will install to a primary partition at least.

[Adam Williamson]

On Fri, 2015-03-06 at 20:09 +0100, Michael Schwendt wrote:
>  On Fri, 6 Mar 2015 10:55:53 -0500 (EST), Jaroslav Reznik wrote:
>  
>  > 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
>  > Log: http://bit.ly/1Em9JXo
>  
>  "404 Not Found" for both!
>  
>  These work:
>  
>  http://meetbot.fedoraproject.org/fedora-meeting-2/2015-03-06/
>   -> 
>
> http://meetbot.fedoraproject.org/fedora-meeting-2/2015-03-06/f22_alpha_go...
>  
>  > 15:31:31 * nirik sees another bug mentioned on list.
>  
>  Good.
>  
>  > 15:31:51 <nirik> but no one bothered to propose it...
>  
>  No good.  Anaconda maintainers not either? D'oh!
>  
>  > 15:32:01 <nirik> 
>  >  https://bugzilla.redhat.com/show_bug.cgi?id=119639715:32:36 
>  > <nirik> ok, it looks like a weird case...
>  
>  Not at all.
>  
>  > 15:32:43 <nirik> trying to reuse some existing preformatted /
>  
>  _Unformatted_ in my case. As mentioned in the ticket. A typical 
>  install scenario.
>  
>  > Thanks everyone! It's pretty solid Alpha release and on time :).
>  
>  LOL! It failed to install here. :(
>  
>  I only hope it will install to a primary partition at least. 
Any form of install to a previously-existing partition, container or 
anything along those lines is out of scope at Alpha. Alpha's storage-
ish requirements are, intentionally, quite minimal:

"The installer must be able to complete an installation to a single 
disk using automatic partitioning.

"Details! [hide]

...well, so long as the disk is big enough, of course. It must work 
whether the disk is formatted or not and whether or not it contains 
any existing data - but since this is an Alpha, it's OK if it can only 
install to a disk with existing data by overwriting it."

i.e., so long as you can successfully install to a single disk on the 
guided 'wipe all data on the selected disk' path, Alpha is good.

The requirements tighten up quite a lot at Beta.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net

[James Hogarth]

On 6 March 2015 at 20:08, Adam Williamson <adamwill(a)fedoraproject.org&gt; wrote:
>  On Fri, 2015-03-06 at 20:09 +0100, Michael Schwendt wrote:
> > On Fri, 6 Mar 2015 10:55:53 -0500 (EST), Jaroslav Reznik wrote:
> >
> > > 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.
> > >
> > > 
I imagine on Tuesday with the Alpha announcement there will be some
people who want to update to it.

Might be worth on the announcement reminding people that fedup working
is beta, not alpha, criteria and there is a known issue.

> From testing (1185604) I've got to the workaround of disabling
selinux, rebooting, fedup to f22, enabling selinux and relabelling as
a way to carry out the update for now.

James