On 2014-08-08, Matthias Wessendorf wrote:Releases on demand? IMO this is wrong, even for bug fixes we should plan
> On Thu, Aug 7, 2014 at 9:52 PM, Bruno Oliveira <bruno@abstractj.org> wrote:
>
> > I also think that our roadmap should reflect the reality:
> > http://staging.aerogear.org/docs/planning/roadmaps/AeroGearCordova/
>
>
>
> Not sure about the other plugins, but for push the reality is that it is
> stable and releases are only needed on demand.
> After 0.6.0 we had some bug-fixes, but no new features. That still
> qualifies the original request for a 0.7.0 release, but I think it is hard
> to 'plan' bug-fix releases.
when it will be fixed.
Regarding, releasing (not fixing) on demand, I think common sense rules here.
Example:
We have 1.0.0 out in August and next is planed late October. But in early September a lot of critical items came up, why ever. They got fixed. IMO it would be a demand to do a release before the original planed late October release.
In that case the roadmap needs to be updated and reflect that, I fully agree. I think we are on the same page here.
-Matthias
>
> -Matthias
>
>
> >
> >
> > Erik any thoughts? Otherwise I will consider to do a full review of
> > Cordova and
> > take over it.
> >
> > On 2014-08-06, Matthias Wessendorf wrote:
> > > Due to silence for quite a while, I have the impression there is no new
> > > release of our "Cordova Push Plugin" needed :-)
> > >
> > >
> > > That's fine, but please keep in mind that for the UPS 1.0.0, the versions
> > > of the different client SDKs need to go to 1.0.0 as well
> > >
> > >
> > >
> > > On Tue, Jul 29, 2014 at 11:55 PM, Matthias Wessendorf <matzew@apache.org
> > >
> > > wrote:
> > >
> > > > Hi,
> > > >
> > > > looked at the change log of the Cordova Plugin and there were some
> > fixes
> > > > since the last 0.6.0 release.
> > > >
> > > > Before we run the Beta2 of UPS (around 6th of August, depends a bit on
> > > > Keycloak's beta4) I'd like to get a 0.7.0 release out.
> > > >
> > > > Any thoughts?
> > > >
> > > > Thanks,
> > > > Matthias
> > > >
> > > > --
> > > > 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@lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
> >
> > --
> >
> > abstractj
> > PGP: 0x84DC9914
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev@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@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
abstractj
PGP: 0x84DC9914
_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev