For WebPush I also created versions on AGPUSH (wps-alpha.1, wps-alpha.2,
wps-beta.1, wps-beta.2 and wps-future)
-Matthias
On Thu, Jan 15, 2015 at 7:16 PM, Matthias Wessendorf <matzew(a)apache.org>
wrote:
Hi,
all SPS tickets have been migrated to AGPUSH. I also created a JIRA admin
ticket for Jay to get rid of the (now) empty AGSMPLPUSH instance.
-M
On Fri, Jan 9, 2015 at 10:38 AM, Daniel Bevenius <
daniel.bevenius(a)gmail.com> wrote:
> +1 Sounds good.
>
> On 9 January 2015 at 10:36, Matthias Wessendorf <matzew(a)apache.org>
> wrote:
>
>> anyone else ?
>>
>> On Tue, Jan 6, 2015 at 11:52 AM, Daniel Passos <daniel(a)passos.me> wrote:
>>
>>> +1 for the same Jira project, and use components
>>>
>>> -- Passos
>>>
>>>
>>> On Mon, Jan 5, 2015 at 1:21 PM, Karel Piwko <kpiwko(a)redhat.com> wrote:
>>>
>>>> +1. Less JIRA instances, the better imho.
>>>>
>>>> Karel
>>>>
>>>> On Mon, 2015-01-05 at 11:32 +0100, 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
>>>>
>>>>
>>>> _______________________________________________
>>>> 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
>>
>> _______________________________________________
>> 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