Does anybody know why this list is private and password protected? It would be nice to see progress, but it appears that part of the development is completely locked down and not open source.
centos-bounces@centos.org wrote:
Does anybody know why this list is private and password protected? It would be nice to see progress, but it appears that part of the development is completely locked down and not open source.
For (x = 0; x < REALLY_LARGE_NUMBER; x++) { system("echo "IS IT DONE YET?""); system("echo "WHY ISN'T IT DONE YET?""); system("echo "WHEN WILL IT BE DONE?""); }
That's my guess...
Insert spiffy .sig here: Life is complex: it has both real and imaginary parts. Life is not measured by the number of breaths we take, but by the moments that take our breath away.
//me ******************************************************************* This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept for the presence of computer viruses. www.Hubbell.com - Hubbell Incorporated**
On 05/13/2011 10:52 AM, Steven Crothers wrote:
Does anybody know why this list is private and password protected? It would be nice to see progress, but it appears that part of the development is completely locked down and not open source.
We have made the QA tracker open for viewing here:
http://qaweb.dev.centos.org/qa/
We need the communication channels to be very high signal to noise when we are testing.
We also need to limit/control the distribution of packages that have not been QA'ed for "Branding Compliance" to the smallest group possible to get the job done.
We do not want bad packages out in the wild (either bad from a "Branding Compliance" perspective or from a "it breaks your install" perspective).
When we have verified that the packages meet our standards, we will release them.