Re: [aerogear-dev] JIRA instances for Push...

this sounds reasonable. Would we go back and rename previous AGPUSH releases to ups-* and also recreate the current old sps releases in AGPUSH?

> On Jan 5, 2015, at 6:53 AM, Bruno Oliveira <bruno(a)abstractj.org&gt; wrote: > > I think makes sense having all of them under AGPUSH and creating > components: ups, sps and wps and manage it with the release field. > > +1 > > On 2015-01-05, Matthias Wessendorf wrote: >> Hi, >> >> right now we have three different types of 'push servers': >> * UPS >> * SimplePush >> * WebPush Server >> >> The first two ones each have their own JIRA, but I was wondering if we use >> the AGPUSH jira for all three. >> >> To manage releases and bugs, we will go with different/more components, and >> for the releases, we could do what we do successfully on our Cordova >> project. We can, in JIRA, have releases like: >> >> ups-1.3.0 >> sps-1.0.0 >> wps-0.2.0 >> >> That way would have all push (server) bits on the same JIRA and >> differentiation is simply done using components and versions as discussed >> above. >> >> Any thoughts ? >> >> >> -- >> 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 > > > -- > > abstractj > PGP: 0x84DC9914 > _______________________________________________ > 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