Roadmap vs Milestone Components?

Hi All,

I am using Trac as the basis for a customized job tracking
system that 
we are developing for internal use.  I'm probably going to
(over time) 
replace a lot of the standard components with internal
versions, though 
I'm trying to avoid patches to the core code as much as
possible, and 
implement everything via template changes and/or plugins.

We think the milestone/roadmap parts map pretty well to our
requirements 
for "jobs", but I am not sure what the difference
is between the roadmap 
and the milestone components and why these are not just one
component. 
It appears to be somewhat historical.  Is there a practical
or 
functional reason for having them be separate?

As this project develops, I expect that I will be developing
some 
functionality which may be general-purpose, and I intend to
make that 
available either as core or as plugins, so I would
appreciate any 
feedback anyone may have.  I know we'll be doing some kind
of 
time-tracking interface (looking at the T&E plugin right
now).

Any guidance or hints on the purpose/relationship of these
two 
components would be appreciated.

Thanks in advance.

-Scott

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Trac Development" group.
To post to this group, send email to trac-devgooglegroups.com
To unsubscribe from this group, send email to
trac-dev-unsubscribegooglegroups.com
For more options, visit this group at http://
groups.google.com/group/trac-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Scott Sharkey wrote:
> Hi All,
>
> I am using Trac as the basis for a customized job
tracking system that 
> we are developing for internal use.  I'm probably going
to (over time) 
> replace a lot of the standard components with internal
versions, though 
> I'm trying to avoid patches to the core code as much as
possible, and 
> implement everything via template changes and/or
plugins.
>
> We think the milestone/roadmap parts map pretty well to
our requirements 
> for "jobs", but I am not sure what the
difference is between the roadmap 
> and the milestone components and why these are not just
one component. 
> It appears to be somewhat historical.  Is there a
practical or 
> functional reason for having them be separate?
>   

No, not really. The Roadmap module could easily get merged
in the 
Milestone one, and most of the work for displaying the
roadmap page 
could be done in a _render_list method.
The various ROADMAP_ are already considered obsolete, so
it'd be good to 
remove them at the same time (look up #3022: Remove
ROADMAP_ADMIN 
<http://trac.
edgewall.org/ticket/3022>).

> As this project develops, I expect that I will be
developing some 
> functionality which may be general-purpose, and I
intend to make that 
> available either as core or as plugins, so I would
appreciate any 
> feedback anyone may have.  I know we'll be doing some
kind of 
> time-tracking interface (looking at the T&E plugin
right now).
>   

Interesting, keep us informed and don't hesitate to read and
comment on 
the various TracDev/Proposals and tickets that may be
related to your work.

-- Christian


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Trac Development" group.
To post to this group, send email to trac-devgooglegroups.com
To unsubscribe from this group, send email to
trac-dev-unsubscribegooglegroups.com
For more options, visit this group at http://
groups.google.com/group/trac-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Christian Boos wrote:
> Scott Sharkey wrote:

>> I am using Trac as the basis for a customized job
tracking system that 
>> we are developing for internal use.  I'm probably
going to (over time) 
>> replace a lot of the standard components with
internal versions, though 
>> I'm trying to avoid patches to the core code as
much as possible, and 
>> implement everything via template changes and/or
plugins.
>>
>> We think the milestone/roadmap parts map pretty
well to our requirements 
>> for "jobs", but I am not sure what the
difference is between the roadmap 
>> and the milestone components and why these are not
just one component. 
>> It appears to be somewhat historical.  Is there a
practical or 
>> functional reason for having them be separate?
>>   
> No, not really. The Roadmap module could easily get
merged in the 
> Milestone one, and most of the work for displaying the
roadmap page 
> could be done in a _render_list method.

I suspected as much, but wasn't sure, so I thought I'd ask.
It's sort of like: Roadmap == Milestone List/Graphic, while
Milestone ==
Text list... in a way.

> The various ROADMAP_ are already considered obsolete,
so it'd be good to 
> remove them at the same time (look up #3022: Remove
ROADMAP_ADMIN 
> <http://trac.
edgewall.org/ticket/3022>).

I was looking at that... Probably will do that too.

>> As this project develops, I expect that I will be
developing some 
>> functionality which may be general-purpose, and I
intend to make that 
>> available either as core or as plugins, so I would
appreciate any 
>> feedback anyone may have.  I know we'll be doing
some kind of 
>> time-tracking interface (looking at the T&E
plugin right now).
>>   
> 
> Interesting, keep us informed and don't hesitate to
read and comment on 
> the various TracDev/Proposals and tickets that may be
related to your work.

I've been reading them for the past few days, and starting
to 'grok' 
what's going on.  As I get more comfortable with both the
trac internals 
and our requirements, I will do so.

THANKS!!!

-Scott


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Trac Development" group.
To post to this group, send email to trac-devgooglegroups.com
To unsubscribe from this group, send email to
trac-dev-unsubscribegooglegroups.com
For more options, visit this group at http://
groups.google.com/group/trac-dev?hl=en
-~----------~----~----~----~------~----~------~--~---