"If the Yetus PMC is aware of regular use of our project in non-released form we need to take action to stop it."
I'm not sure I understand that part though - is that specific to Yetus, or is it something ASF-level? Let's take Hadoop as an example. I could build it from trunk's HEAD once a week and deploy on production cluster, nobody can/should stop me from doing that, right? On Wed, Mar 2, 2016 at 12:26 PM, Sean Busbey <[email protected]> wrote: > The conversation around the demand for such a service should come from who? > > PMCs that want to use Yetus, I think? > > -Sean > > On Wed, Mar 2, 2016 at 2:05 PM, Andrew Bayer <[email protected]> > wrote: > > Speaking with my infra hat on - > > > > I'd like to see us end up going in that direction. But yeah, it'll need > > committed resources from infra, meaning cycles from paid infra staff and > > those staff being able to handle the work without needing to resort to > > volunteer assistance for day to day activities. Starting a discussion > with > > infra about the possibility would be a good idea. > > > > A. > > On Mar 2, 2016 12:00, "Sean Busbey" <[email protected]> wrote: > > > >> Another option would be to request that infra@asf provide "yetus based > >> precommit testing" as an SLA governed service. Then they could > >> maintain configuration management of running the tests with known good > >> versions and rolling them out across projects. > >> > >> AFAIK, the backlog on infra is pretty severe though, so requests are > >> likely to get backlogged if they don't come with a volunteer. > >> > >> > -- Thanks, Michael Antonov
