Re: [aerogear-dev] [datasync] JIRA component name

instead of storing all sync items underneath the AEROGEAR instance, we could have a AGDATASYNC JIRA instance. I think this makes it nicer to organize, especially with releases. That's what we did with AGPUSH for the 'push feature', which obviously is available across platforms. -Matthias On Tue, Nov 11, 2014 at 6:38 AM, Daniel Bevenius < daniel.bevenius(a)gmail.com&gt; wrote: > Hi All, > > we have created JIRA tasks for the data sync roadmaps [1][2]. > > While creating them we noticed that we are using different component > names in JIRA for the our projects: > > AEROGEAR: > Uses 'data-sync' as the component name: > https://issues.jboss.org/issues/?filter=12322676 > > AGIOS > Uses 'sync' as the component name: > https://issues.jboss.org/issues/?filter=12322678 > > AGDROID > Uses 'datasync' as the component name: > https://issues.jboss.org/issues/?filter=12322677 > > AGJS > Uses 'data-sync' as the component name: > https://issues.jboss.org/issues/?filter=12322679 > > I would be nice to makes these consistent across the projects. Let me > know which you prefer and I'll make the changes needed. > > I'm personally +1 for 'datasync' > > [1] http://aerogear.org/docs/planning/roadmaps/AeroGearDataSync > [2] http://aerogear.org/docs/planning/roadmaps/AeroGearConflictResolution > > _______________________________________________ > 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