On Wed, 2010-04-21 at 04:54 -0400, Kamil Paral wrote: > ----- "Adam Williamson" <awilliam@xxxxxxxxxx> wrote: > > > Hi, all. At the last blocker meeting, we realized there are no > > release > > criteria regarding remote-accessible installs. If you can't install > > Fedora to be remote-accessible out of the box, some sysadmins will > > have > > a lot of trouble. So I propose we add this to the criteria: > > > > "With the correct install configuration, it should be possible to > > make > > an installed system immediately remotely accessible (you should be > > able > > to install with a secure remote access service active and unblocked > > by > > firewall-type mechanisms)" > > Will that also cover > https://bugzilla.redhat.com/show_bug.cgi?id=572489 ? I would be glad > if we could use that criterion to mark such bugs as blockers. It depends on whether 'network doesn't come up on boot' applies to a typical remote-accessible install, I guess. I wouldn't want to say, I'd rather ask someone with real-world experience of doing such installs. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
