<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On Jul 23, 2014, at 11:22 AM, Matthias Wessendorf <<a href="mailto:matzew@apache.org">matzew@apache.org</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">Thanks for all the feedback !<div><br></div><div>I have added the Cordova and iOS processes to our wiki - linking to those from its landing page:</div><div><a href="https://github.com/aerogear/collateral/wiki">https://github.com/aerogear/collateral/wiki</a><br>
</div><div><br></div><div><br></div><div>Regarding plain JavaScrip, is this gist correct:</div><div><a href="https://gist.github.com/matzew/14f93693c8362b753782">https://gist.github.com/matzew/14f93693c8362b753782</a><br></div></div></blockquote><div><br></div><div>well, not sure about "JavaScrip", but that is pretty much what i do for the “JavaScript” stuff. i currently don’t sign the release, but do "git tag -a ‘x.y.z’ -m’x.y.z’”</div><div><br></div><div>while i create a branch for the new pending release, i also like to create a tag for it. so x.y.z-beta or something like that.</div><div><br></div><br><blockquote type="cite"><div dir="ltr"><div>
</div><div><br></div><div>if so, I will add a JS section - others, a JS centric fork of that document is more than welcome</div><div><br></div><div>-M</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jul 8, 2014 at 10:31 AM, Corinne Krych <span dir="ltr"><<a href="mailto:corinnekrych@gmail.com" target="_blank">corinnekrych@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class=""><br>
On 08 Jul 2014, at 10:29, Christos Vasilakis <<a href="mailto:cvasilak@gmail.com">cvasilak@gmail.com</a>> wrote:<br>
<br>
>><br>
>> On Jul 8, 2014, at 11:17 AM, Corinne Krych <<a href="mailto:corinnekrych@gmail.com">corinnekrych@gmail.com</a>> wrote:<br>
>><br>
>><br>
>> On 08 Jul 2014, at 10:12, Christos Vasilakis <<a href="mailto:cvasilak@gmail.com">cvasilak@gmail.com</a>> wrote:<br>
>><br>
>>>><br>
>>>> On Jul 8, 2014, at 10:07 AM, Matthias Wessendorf <<a href="mailto:matzew@apache.org">matzew@apache.org</a>> wrote:<br>
>>>><br>
>>>> Hi,<br>
>>>><br>
>>>> at the face2face we had a discussion about formalizing our release processes for non-java project.<br>
>>>> The Java guide is, IMO, still relevant and up-to-date:<br>
>>>> <a href="https://github.com/aerogear/collateral/wiki/Release-Process-(Java)" target="_blank">https://github.com/aerogear/collateral/wiki/Release-Process-(Java)</a><br>
>>>><br>
>>>><br>
>>>> For the non-java projects I started a few gists<br>
>>>><br>
>>>> * for Cordova and JavaScript, I think this could be used:<br>
>>>> <a href="https://gist.github.com/matzew/14f93693c8362b753782" target="_blank">https://gist.github.com/matzew/14f93693c8362b753782</a><br>
>>>><br>
>>>> Note: I am not sure if some extra steps are missing for things like npm oe bower<br>
>>>><br>
>>>> * for iOS, I think we can formalize on something like this:<br>
>>>> <a href="https://gist.github.com/matzew/941883df5bd0abcf1d61" target="_blank">https://gist.github.com/matzew/941883df5bd0abcf1d61</a><br>
>>><br>
>>> looks good +1<br>
>>> did some changes here [1] and modified the ‘Perform’ section adding cocoapods new approach to spec publish and the step to update the spec itself.<br>
>>><br>
>>> If we are fine with it, will go ahead and add it on our '<a href="https://github.com/aerogear/collateral/wiki" target="_blank">https://github.com/aerogear/collateral/wiki</a>'<br>
>>><br>
>><br>
>><br>
>> don’t we miss:<br>
>> - step 0: ‘send PR to cocoa pod’<br>
><br>
> this step was replaced from cocoa pods with the 'pod trunk push’ command, no need to send PR on their repo any more. That was my update on matzew gist :)<br>
<br>
<br>
</div>Ahhhh!<br>
Good to clarify with a doc actually :)<br>
<div class="HOEnZb"><div class="h5"><br>
><br>
><br>
>> - step 5: update all demo Podfile with relevant tag<br>
><br>
> +1, have updated my gist[1] with this step too<br>
><br>
> Thanks,<br>
> Christos<br>
><br>
><br>
><br>
><br>
>><br>
>>> Thanks<br>
>>> Christos<br>
>>><br>
>>> [1] <a href="https://gist.github.com/cvasilak/114c7280b627ae6bcd9f" target="_blank">https://gist.github.com/cvasilak/114c7280b627ae6bcd9f</a><br>
>>><br>
>>> [<br>
>>>><br>
>>>><br>
>>>> Greetings,<br>
>>>> Matthias<br>
>>>><br>
>>>><br>
>>>> --<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><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>
>>><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>
>><br>
>><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>
><br>
><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>
<br>
<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>
</div></div></blockquote></div><br><br clear="all"><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>
_______________________________________________<br>aerogear-dev mailing list<br><a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>https://lists.jboss.org/mailman/listinfo/aerogear-dev</blockquote></div><br></body></html>