Based on these issues/epics, I will create the roadmap.
On Tue, May 28, 2013 at 4:28 PM, Matthias Wessendorf <matzew(a)apache.org>wrote:
Added AGPUSH-71 for examples/quickstarts ...
On Tue, May 28, 2013 at 4:10 PM, Matthias Wessendorf <matzew(a)apache.org>wrote:
> Oh, all these epics are referenced in
>
https://issues.jboss.org/browse/AGPUSH-46
>
>
> On Tue, May 28, 2013 at 4:06 PM, Matthias Wessendorf <matzew(a)apache.org>wrote:
>
>> Hi,
>>
>> now that our AGPUSH JIRA instance is up, I was creating some _base_
>> Epics, which have different sub-tasks.
>>
>> For our first release (~August), I thought about the following Epics:
>>
>> - Specifications:
AGPUSH-63<https://issues.jboss.org/browse/AGPUSH-63>
>> - Client SDKs: AGPUSH-70 <
https://issues.jboss.org/browse/AGPUSH-70>
>> - Admin UI: AGPUSH-66 <
https://issues.jboss.org/browse/AGPUSH-66>
>> - PushNetwork Integration:
AGPUSH-60<https://issues.jboss.org/browse/AGPUSH-60>
>> - RESTful Endpoints:
AGPUSH-57<https://issues.jboss.org/browse/AGPUSH-57>
>> - Documentation and Guides:
AGPUSH-61<https://issues.jboss.org/browse/AGPUSH-61>
>>
>>
>>
>> Note, these epics have already sub-tasks, which cover the real work.
>> Some of these sub-tasks are just "references" for linking to other
JIRAs
>> (e.g. to AGSEC, AGDROID or AGIOS).
>>
>>
>> Any thoughts on these epics, and their sub-tasks ?
>>
>>
>> Greetings,
>> 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
>
--
Matthias Wessendorf
blog:
http://matthiaswessendorf.wordpress.com/
sessions:
http://www.slideshare.net/mwessendorf
twitter:
http://twitter.com/mwessendorf