> This is related to validation tests, but different enough that I wanted > a new thread. While we *can* release new versions of FMW on > getfedora.org at Fedora GA, there's no reason to tie the two together — > and really, some good ones to *not* double up: > > * we can fix bugs without waiting > * we can add new functionality whenever > * and we don't have to worry about surprise failures due to regressions > on GA release day affecting the rush of people Sure, makes sense. > > I have a feature request (use a distinct user-agent for ISO downloads > so we can tell when FMW is being used) which I'd love to not wait for > June/July to get live. > > Do we want to go through validation and update the website whenever > Martin cuts a new release upstream? Or do we want to have > regularly-scheduled times to do it? Or whenever there's a particular > reason to do it and leave it alone otherwise? Or something else? Martin should be probably the one to tell websites team when to pull new version (once it is tested, not every one needs to be pulled). We'll probably not be able to test every each upstream release he does, especially on all platforms. During Branched release cycle, it will be easier, since we're testing FMW all the time anyway. Outside of the release cycle, he can ping us if we have time to do that, or he can wait until some feedback is available in Bodhi and act based on that (however, that does not include feedback for non-Fedora systems, but I think he said he performs a few smoke tests every time on his test machines, so that should be probably fine). _______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
