<div dir="ltr">Would tagging all repos with the same version number as the jira version number on a release work?<div>--</div><div>Gorkem</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, May 27, 2014 at 10:51 AM, Erik Jan de Wit <span dir="ltr"><<a href="mailto:edewit@redhat.com" target="_blank">edewit@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">That is a very good point… so if we keep them as separate repos how do we manage multiple versions / releases in jira<div>
<div class="h5"><div><br><div><div>On 27 May,2014, at 16:28 , Gorkem Ercan <<a href="mailto:gorkem.ercan@gmail.com" target="_blank">gorkem.ercan@gmail.com</a>> wrote:</div><br><blockquote type="cite"><div dir="ltr">
On the practical side, it makes it a bit harder to install a Cordova plugin from a git repo (because you need to point to a subdir) via Eclipse Thym and Cordova CLI.<div>--</div><div>Gorkem</div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Tue, May 27, 2014 at 10:21 AM, Erik Jan de Wit <span dir="ltr"><<a href="mailto:edewit@redhat.com" target="_blank">edewit@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">We get a release of AeroGear Cordova and all it’s components. I know if you want to find out what changed for each plugin and version, that will be less ideal. If you have a suggestion to have it tracked better I’m all ears<div>
<div><br><div><div>On 27 May,2014, at 16:16 , Matthias Wessendorf <<a href="mailto:matzew@apache.org" target="_blank">matzew@apache.org</a>> wrote:</div><br><blockquote type="cite"><div dir="ltr"><br>
<div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, May 27, 2014 at 4:13 PM, Erik Jan de Wit <span dir="ltr"><<a href="mailto:edewit@redhat.com" target="_blank">edewit@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
Now Cordova has it’s own jira project and therefore it’s own version number, but in github the plugins have their own repository. Would it make sense to move all the plugins into one central github repository and when making a release to release all of them?<br>
</blockquote><div><br></div><div><br></div><div>That means we get a few new release of the geo-plugin, while we really have just changed things on the push-plugin (as an example) ? </div><div><br></div><div>-Matthias</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Wdyt?<br>
Erik Jan<br>
_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">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><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></div>
_______________________________________________<br>aerogear-dev mailing list<br><a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">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></blockquote>
</div><br></div></div></div><br>_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">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>
_______________________________________________<br>aerogear-dev mailing list<br><a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">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></blockquote>
</div><br></div></div></div></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>