testing for releases - what does it entail?

[walterw]

I am wondering what is involved for testing releases such as the upcoming 1.4 release?  Is it manual by the user base, automated, etc.?  How can we help out?

 

Thanks,

Walter

[walterw]

So, if I understand correctly, testing is based on the end user manually follows above steps and reporting any issues?  Can any tasks be automated?

[walterw]

I am just curious - what is the manual effort that Daniel and team perform?  It seems there is some testing around that, can that by automated is what I'm getting at?  Why can't there be rolling releases?  I'm not complaining about the release process, but am trying to understand when the infra team prepares 1.3 or 1.4, what are they doing?  Why must they do it by hand?  I understand that Funtoo packages is a collection of software all developed at a different pace and that ebuilds have to be maintained to keep up with those packages.

 

I'm looking for, how can we improve infrastructure to make this process better, more robust, etc.