[prev in list] [next in list] [prev in thread] [next in thread] 

List:       fedora-test-list
Subject:    Re: Fedora Media Writer release schedule (was Re: Validation test proposal: mediawriter testing tabl
From:       Martin Bříza <mbriza () redhat ! com>
Date:       2017-01-16 10:28:50
Message-ID: op.yt5l2cgptrc8xl () dhcp-4-209 ! brq ! redhat ! com
[Download RAW message or body]

On Mon, 16 Jan 2017 10:52:28 +0100, Kamil Paral <kparal@redhat.com> wrote:

>> 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).

I'm testing the releases myself, yes. Usually I focus on the stuff I  
changed and then just try writing and erasing a drive, so nothing too  
complicated.

I see another problem with the release process now though: pulling new  
non-Fedora releases. There is no rigid process of getting the releases to  
websites. The process now is I put up a new release and ping dgilmore to  
compile it. He then, when he has time, compiles it and puts it somewhere  
and notifies websites to pull it or he puts it there himself.

For example for 4.0.8 which was released about a week ago there has been  
no activity yet - meanwhile, f25 package is already stable.

All I can do is ping the people over and over and hope one day the version  
get pushed there. There is very limited feedback in regards to what the  
status is now, if it compiles and there is no testing besides mine.
_______________________________________________
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-leave@lists.fedoraproject.org

[prev in list] [next in list] [prev in thread] [next in thread]