On 10/07/2013 08:28 PM, Adam Williamson wrote:
* viking-ice suggested pushing to have anaconda development cycle adjusted to stabilize earlier in the cycle
As I suggested on the meeting I have started that discussion with the
Anaconda developers and the thread for that can be found here [¹]
Now what we need to do to be able to implement this from our end is to
for example move the installer criteria bit out of the general criteria
into a targeted installer release criteria since in essence it would be
on a release cycle different then from those of the product(s).
Another thing is to formulate a test strategy to cover the installer
like for example coming up with an specific installer testing team that
tests as well as triage the installer to giving the developers enough
time to focus on valid reports and fixing those issues..
Thoughts and comments?
JBG
1.
https://www.redhat.com/archives/anaconda-devel-list/2013-October/msg00005.html
--
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
