Folks, I just want to notice a thing or two from my side that might be relevant for the OI (hipster).
What I've seen and consider really important is to implement a kind of release engineering. And here I do not want some complicated process with many approvals and stuff - rather a sleek and streamlined (hipster) release management. I've seen packages breaking builds because of incompatible versions (e.g. libmemcached bump made myself incompatible with php5.4, or ruby version breaking other stuff...). Is it feasible to organise a non-bureaucratic release management setting the priorities which packages should get updated first and then possibly check for defects produced by it? Just a thought - and willing to help with it. Let me know your thoughts. Cheers, Erol _______________________________________________ oi-dev mailing list [email protected] http://openindiana.org/mailman/listinfo/oi-dev
