On Fri, Jul 3, 2015 at 11:02 AM, Greg Grossmeier wrote:
> I would prefer, instead, to have canonical eg #201516-Q1 projects that
> are for tracking quarterly goals across teams (with columns for either
> ETA month or status (in-progress/done)). I know some teams already do
> something like this e
>
> From what I read here, the current roadmap software is difficult to use and
> is not being used consistently;
In fact, until this thread, I didn't even know that people were making
a roadmap in phab...
--
bawolff
___
Wikitech-l mailing list
Wikitec
As an outside observer, I'm a bit concerned about the deprecation of one of
the few tools used to give a "big picture" overview of what is coming, who
is scheduling what, and the ability to identify conflicting or competing
priorities. Engineering has done some outstanding work, but there have
als
Hi Gergo,
First: Thanks for your reply. I always appreciate your ability to point
out things people have missed/forgotten.
> I don't think all (or even the main) use cases of #roadmap are covered by
> the proposal.
>
> * #user-notice is much more noisy. A #roadmap task is "describing a
> signif
+teampractices
On Thu, Jul 2, 2015 at 4:17 PM, Greg Grossmeier wrote:
> Hello all,
>
> First, some history and context:
>
> The #roadmap project[0] in our Phabricator instance was set up by Erik M
> as a trial way of tracking upcoming releases, deployments, and generally
> "new things of note",
On Thu, Jul 2, 2015 at 4:17 PM, Greg Grossmeier wrote:
> Let me know if you have any concerns,
I don't think all (or even the main) use cases of #roadmap are covered by
the proposal.
* #user-notice is much more noisy. A #roadmap task is "describing a
significant new piece of user-facing functi
