<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Dec 15, 2014 at 2:15 PM, Sebastien Blanc <span dir="ltr"><<a href="mailto:scm.blanc@gmail.com" target="_blank">scm.blanc@gmail.com</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">+1 to not duplicate the work regarding jiras/the roadmap on the website.<div>But in the same time, I think it's important to keep on the site some info for the future releases, less concrete, more like our "vision" / themes that we would like to cover. Can be resumed to only 3 or 4 bullets points.</div></div></blockquote><div><br></div><div>yes, I was not saying remove all of the roadmaps.</div><div><br></div><div><br></div><div>The plan is to re-org. the current structure. Turn it more into something that is feature based</div><div><br></div><div><div>* AeroGear OAuth2 - 1.0.0 (Janurary)</div><div><br></div><div>LINK to details</div><div><br></div><div><div>* AeroGear Sync - 1.0.0 (April)</div><div><br></div><div>LINK to details</div><div><div><br></div><div>* AeroGear SOME_FEATURE - 1.0.0 (SOME MONTH)</div><div><br></div><div>LINK to details</div><div><br></div></div></div></div><div><br></div><div><br></div><div>That will give an understand of what's coming, overall.</div><div><br></div><div><br></div><div>The remove of the duplicating roadmap docs is just one thing</div><div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div> </div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="h5">On Mon, Dec 15, 2014 at 2:09 PM, Matthias Wessendorf <span dir="ltr"><<a href="mailto:matzew@apache.org" target="_blank">matzew@apache.org</a>></span> wrote:</div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div><div class="h5"><div dir="ltr"><div>Hi team,<br></div><div><br></div><div>while thinking about restructuring our roadmaps, I was wondering about our existing roadmaps on [1]. Overall I'd like to have the AG roadmaps more feature driven, but that requires some more thoughts/changes?</div><div><br></div><div>However, here is what I am wondering about...</div><div><br></div><div>Most of our roadmaps we link to from [1], are really just pointing to different JIRAs.<br></div><div><br></div><div><br></div><div>Let's take one example, UPS:</div><div><a href="https://aerogear.org/docs/planning/roadmaps/UnifiedPush/" target="_blank">https://aerogear.org/docs/planning/roadmaps/UnifiedPush/</a></div><div><br></div><div>Basically all info on the above page is present in JIRA (including the 'archived' roadmap of older releases). Since JIRA should be the central tool for planing releases, features and future versions, I think that our roadmap docs are not adding too much value, since they repeat info that is available on a different place (JIRA).</div><div><br></div><div>Also, maintaining the roadmaps is tedious: You make a change on the actual JIRA (e.g. move the date of a release or add a new feature). To keep the roadmap up-to-date, you put the same info on the roadmap doc and send a PR.</div><div><br></div><div><br></div><div>Can we remove these roadmap docs?</div><div><br></div><div>For UPS that would mean, that the link on [1] would go against:</div><div><a href="https://issues.jboss.org/browse/AGPUSH?selectedTab=com.atlassian.jira.jira-projects-plugin:versions-panel" target="_blank">https://issues.jboss.org/browse/AGPUSH?selectedTab=com.atlassian.jira.jira-projects-plugin:versions-panel</a></div><div><br></div><div>instead of here:</div><div><a href="https://aerogear.org/docs/planning/roadmaps/UnifiedPush/" target="_blank">https://aerogear.org/docs/planning/roadmaps/UnifiedPush/</a></div><div><br></div><div>-Matthias</div><div><br></div><div>[1] <a href="https://aerogear.org/docs/planning/" target="_blank">https://aerogear.org/docs/planning/</a></div><span><font color="#888888"><div><br></div><div><br></div>-- <br><div>Matthias Wessendorf <br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a></div>
</font></span></div>
<br></div></div>_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br></blockquote></div></div>
<br>_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br></blockquote></div><br clear="all"><div><br></div>-- <br><div class="gmail_signature">Matthias Wessendorf <br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a></div>
</div></div>