Brett Porter wrote:
Jason van Zyl wrote:
For design, I believe it should go with the project itself, targetted at
the same release as it is aimed for.
Not sure if all of them would align with a release, but more importantly
it's not easy to see the priorities in design vs scheduled work given
t
Jason van Zyl wrote:
>> For design, I believe it should go with the project itself, targetted at
>> the same release as it is aimed for.
>
> Not sure if all of them would align with a release, but more importantly
> it's not easy to see the priorities in design vs scheduled work given
> the way JI
Brett Porter wrote:
Initial thoughts are -1.
To me, the Maven dev process is a function of the whole project and can
easily be dealt with in MPA.
The dev process will be applied to all the projects in the Maven TLP
yes, but I'm specifically talking about a JIRA project for scheduled
work li
Initial thoughts are -1.
To me, the Maven dev process is a function of the whole project and can
easily be dealt with in MPA. I don't think there'll be a lot of "issues"
to raise there, especially nothing requiring scheduling.
For design, I believe it should go with the project itself, targetted
Hi,
I was just looking over our discussion and without a separate project
for the dev process and design JIRA doesn't make it very easy to look at
the popular issues. So it would definitely be easier for reporting to
have a separate project but it might also be good to separate
design/process
