On 8 Jul,2014, at 9:24 , Matthias Wessendorf <matzew(a)apache.org> wrote:
On Tue, Jul 8, 2014 at 9:16 AM, Sebastien Blanc <scm.blanc(a)gmail.com> wrote:
On Tue, Jul 8, 2014 at 9:07 AM, Matthias Wessendorf <matzew(a)apache.org> wrote:
Hi,
at the face2face we had a discussion about formalizing our release processes for non-java
project.
The Java guide is, IMO, still relevant and up-to-date:
https://github.com/aerogear/collateral/wiki/Release-Process-(Java)
For the non-java projects I started a few gists
* for Cordova and JavaScript, I think this could be used:
https://gist.github.com/matzew/14f93693c8362b753782
+1 but we need also instructions on the release process on the cordova plugin repo
isn't that just doing a TAG on our gh repo? If not, indeed, we would need this extra
info in there
So for Cordova there are 2 extra steps needed, change the version number in the plugin.xml
file and push the plugin to plugins.cordova.io with plugman.
And one more thing is update the site (
aerogear.org) to change the download link
Note: I am not sure if some extra steps are missing for things like npm oe bower
* for iOS, I think we can formalize on something like this:
https://gist.github.com/matzew/941883df5bd0abcf1d61
Greetings,
Matthias
--
Matthias Wessendorf
blog:
http://matthiaswessendorf.wordpress.com/
sessions:
http://www.slideshare.net/mwessendorf
twitter:
http://twitter.com/mwessendorf
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
Matthias Wessendorf
blog:
http://matthiaswessendorf.wordpress.com/
sessions:
http://www.slideshare.net/mwessendorf
twitter:
http://twitter.com/mwessendorf
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev