[aerogear-dev] AeroGear.org - a first thought on changing our roadmap docs
Matthias Wessendorf
matzew at apache.org
Mon Dec 15 08:09:23 EST 2014
Hi team,
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?
However, here is what I am wondering about...
Most of our roadmaps we link to from [1], are really just pointing to
different JIRAs.
Let's take one example, UPS:
https://aerogear.org/docs/planning/roadmaps/UnifiedPush/
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).
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.
Can we remove these roadmap docs?
For UPS that would mean, that the link on [1] would go against:
https://issues.jboss.org/browse/AGPUSH?selectedTab=com.atlassian.jira.jira-projects-plugin:versions-panel
instead of here:
https://aerogear.org/docs/planning/roadmaps/UnifiedPush/
-Matthias
[1] https://aerogear.org/docs/planning/
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141215/468e547a/attachment.html
More information about the aerogear-dev
mailing list