+1

I like the idea of using JIRA's to note places where future work has to
happen.... good traceability.
This is obviously different from plonking a change history at the top of a
file; which I don't think anyone is advising (that's what SVN is for).

John

On 21/11/06, Martin Ritchie <[EMAIL PROTECTED]> wrote:

That is what I was meaning... a simple //todo QPID-XX.

Just thought it might make the location easier to track from the JIRA.
Although I'm sure a reference to the code by method name from the JIRA
would be enough.

On 21/11/06, Marnie McCormack <[EMAIL PROTECTED]> wrote:
> I'm not sure about littering JIRA refs in the codebase - is that what
you
> mean ?
>
> Apologies if I've misunderstood :-)
>
> Marnie
>
>
> On 11/21/06, Martin Ritchie <[EMAIL PROTECTED]> wrote:
> >
> > Might be good to simply update the /todo in the code base so we can
> > have a reference in the code as a starting point.
> >
> > On 21/11/06, Marnie McCormack <[EMAIL PROTECTED]> wrote:
> > > All,
> > >
> > > I'm planning to create JIRAs for each TODO in the java codebase and
then
> > > remove them from the code, in order to make tasks trackable/visible.
> > >
> > > Any objections ?
> > >
> > > Marnie
> > >
> > >
> >
> >
> > --
> > Martin Ritchie
> >
>
>


--
Martin Ritchie

Reply via email to