[OM Cooker] We need to get rid of main-testing repo for Lx 3.02 RC and Final release.

Ben Bullard benbullard79 at cox.net
Wed May 10 22:38:44 EDT 2017


Apologies for personal e-mails but OM-whatever e-mails aren't working 
for me right now.

An issue I forgot in TC-meeting. This is a big issue as well. So far the 
Lx 3.02 ISO's have all been made with main-testing repo enabled. So that 
sorta means that users/testers need to enable it to update their 
systems. In fact there have been times when updating would not work 
without main-testing or manual intervention. This won't work with 
non-tech-savvy users. And we got 'em. We should be wanting more of them 
shouldn't we?

I see huge problems with a Public release needing any testing repo. In 
fact I'm running in to things just testing where I'm inclined and stop 
till we get this squared away. For one do I test with or without 
main-testing enabled and as I mentioned sometimes you can't update 
without it.

1. I need main-testing to be gone from the RC ISO for final *thorough* 
testing. I'm running in to many instances of "what am I testing packages 
in main-updates or main-testing". Surely we're not expected to test both 
and if we did imagine the nightmare of lib and dependency packages. 
Frankly I'm not tech-savvy enough myself to do that. And this is exactly 
why I just stopped testing something and wrote this e-mail.

2. I damn sure don't want to be the person that has to answer questions 
on the forum about "Why bad packages", "Why packages not signed", after 
this hits SourceForge and DistroWatch. That's where I go disappear in 
the swamps of Louisiana.


-- 

Ben Bullard
ben79
--------------------
OpenMandriva-QA Team

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://ml.openmandriva.org/pipermail/om-cooker_ml.openmandriva.org/attachments/20170510/dd9f0555/attachment-0001.html>


More information about the OM-Cooker mailing list