<div dir="ltr">+1<div>Like you said for the java bits, the process is quite clear and having a maven staging repo helps, let's use this thread to check what we could do for the other bits :</div><div><br></div><div>* JavaScript : We could maybe share a zip (somewhere doh) containing the release and give the link in a email on the ML "please test blabla, in 48hours this will be pushed on bower and <a href="http://ag.org">ag.org</a> ... + JIRA changelog" </div>
<div><br></div><div>* Cordova : We could point to the branch containing the release and again share this on the ML "please test blabla, in 48hours this will be pushed to master and cordova plugin repo will be updated ... + JIRA changelog" </div>
<div><br></div><div>* iOS : Anything to "stage" the pods ? </div><div><br></div><div>Once we have this, we should create a wiki page for each platform, like we did for Java.</div><div><br></div><div><br></div><div>
<br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Mar 11, 2014 at 10:00 AM, Matthias Wessendorf <span dir="ltr"><<a href="mailto:matzew@apache.org" target="_blank">matzew@apache.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><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)" target="_blank">https://github.com/aerogear/collateral/wiki/Release-Process-(Java)</a></div>
<span class="HOEnZb"><font color="#888888"><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>
</font></span></div>
<br>_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br></blockquote></div><br></div>