<div dir="ltr"><div>Hello,</div><div><br></div><div>for the Java bits we do have a solid release process ([1]). The main benefit is we stage the artifacts on a repo and give the community a heads-up for testing. Based on this vote we release (or may not release). This is a great way to engage the entire community to double check and give feedback. The release process is a shared thing inside of the community.</div>
<div><br></div><div><br></div><div>For the other bits we currently do not have a similar process (my feeling). I'd actually prefer if we establish something like that on all the other platforms as well. This gives the community a chance to test the bits before we push them to the repos. </div>
<div><br></div><div>IMO, if we start 'silently' release bits to the actual repositories it's kinda bypassing the community's feedback on a particular release candiate. Sure all the projects have tests, but manual testing, by the community is IMO a very positive thing</div>
<div><br></div><div>-Matthias</div><div><br></div><div>[1] <a href="https://github.com/aerogear/collateral/wiki/Release-Process-(Java)">https://github.com/aerogear/collateral/wiki/Release-Process-(Java)</a></div><div><br>
</div><div><br></div>-- <br>Matthias Wessendorf <br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>
twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a>
</div>