Although SVN provides a direct route to testing patches for the next 3.5.13 release, I want to propose making tarballs available too.
Many people are motivated to test newer versions but do not have the bandwidth, computer horsepower, or inclination to support SVN.
I propose providing directories just like those for downloading the 3.5.12 tarballs. The directories would be explicitly named 3.5.13-testing or something similar.
When 3.5.13 goes live and official, all we should need do is just change the name of the directory.
Darrell
The idea works well from the user perspective as long as a new tarball gets generated every time a patch gets generated. This may work if the Trinity server(s) can handle the extra load, but until we know this, I'm cautious about supporting the idea.
On 10/16/10, Darrell Anderson humanreadable@yahoo.com wrote:
Although SVN provides a direct route to testing patches for the next 3.5.13 release, I want to propose making tarballs available too.
Many people are motivated to test newer versions but do not have the bandwidth, computer horsepower, or inclination to support SVN.
I propose providing directories just like those for downloading the 3.5.12 tarballs. The directories would be explicitly named 3.5.13-testing or something similar.
When 3.5.13 goes live and official, all we should need do is just change the name of the directory.
Darrell
On Sat, Oct 16, 2010 at 11:47, Darrell Anderson humanreadable@yahoo.com wrote:
Although SVN provides a direct route to testing patches for the next 3.5.13 release, I want to propose making tarballs available too.
Many people are motivated to test newer versions but do not have the bandwidth, computer horsepower, or inclination to support SVN.
I propose providing directories just like those for downloading the 3.5.12 tarballs. The directories would be explicitly named 3.5.13-testing or something similar.
When 3.5.13 goes live and official, all we should need do is just change the name of the directory.
I'd rather have the patches.