Re: [aerogear-dev] Cordova: question on recent Push Plugin release

On Mon, Mar 24, 2014 at 5:36 PM, Matthias Wessendorf <matzew(a)apache.org&gt;wrote: > I am fine in keeping master up-to-date w/ the latest greatst of our > Android/iOS. > > But my question was really: Why are there two different 0.0.3 versions > being released (our offical one on GH, and some four week old one on > crodova.io (can we remove/update that piece)? > ah! check: http://plugins.cordova.io/#/org.jboss.aerogear.cordova.push it shows the recent version. yay! > > > > On Mon, Mar 24, 2014 at 5:20 PM, Sebastien Blanc <scm.blanc(a)gmail.com&gt;wrote: > >> In the same spirit, I think that the plugin version in our master should >> always be bumped in comparison to the current released version. Like we do >> in the other projects. >> So, for now master should be 0.4-dev / or 0.4-snapshot, not sure what >> cordova supports. Because when we will merge PRs , can be confusing for the >> users. >> >> >> >> On Fri, Mar 21, 2014 at 3:10 PM, Matthias Wessendorf <matzew(a)apache.org&gt;wrote: >> >>> Hello, >>> >>> a few days ago, the 0.0.3 version of our Cordova Push Plugin was >>> released (see [1]). >>> >>> Now, on our github 'releases' folder we see the release was made >>> available on March 17th (as of now it says "4 days ago"). >>> >>> Great! >>> >>> Looking at the Cordova Plugin Registry, I see it's there since four >>> weeks: >>> http://plugins.cordova.io/#/org.jboss.aerogear.cordova.push >>> >>> That's incorrect, as we officially released it a few days ago (see [1]). >>> >>> Also they are not exactly the same (in download size and content (just >>> do a diff on the PushPlugin.m file). >>> >>> Anyways, I am wondering if it is possible to update the version on the >>> Cordova Registry, so that we: >>> a) ship the official release >>> b) have both downloads (GH and Cordova.io) being the same >>> >>> Thanks! >>> Matthias >>> >>> >>> [1] >>> http://lists.jboss.org/pipermail/aerogear-dev/2014-March/006926.html >>> >>> -- >>> 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 > -- 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