Tim , Robert,
Can we leverage OpenSUSEs OBS project for building trinity?
> My intention was to keep the build farm running until R14 was released, then see if any donations came in to cover some of the costs. However, this morning the main chiller was destroyed due to sudden power brownouts/surges, forcing the build farm offline. As I do not have the funds to replace this chiller, and with the onset of spring/warmer temperatures here, I cannot restart the build farm at this time.<
How much money is needed? I am admittedly spending almost all of my money on political expenses right now and may be too broke to do anything until May or June.
Could we make a formal appeal for cash for expenses for getting 14.0.0 out the door, with a specific target, if it's larger than what this list alone could be hoped to raise? It would be very good to at least get the older deployments support for 14 before dropping some of them off.
Do we know which releases are more commonly deployed organizationally? I would assume the LTS releases, but such obvious assumptions prove incorrect all the time -- one sufficiently large deployment using, say, Meerkat, could make that a higher priority for us than Lucid. Do we have statistics on which versions get hit up for updates most frequently? Is there a better measure than that that we might use, given that many deployments might not update frequently at all?
James Gholston
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net
For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting