| Re: [mylar-dev] issue-tracking repositories proposal |
Michael Valenta wrote:
With regard to repository/bug system integration, here are some of the possibilities we identified in our research: 2) Commit (or other Team operations such a branching) triggers change in a bug (e.g. RESOLVED FIXED on commit)These two outlined in comments to Mylar's ussue https://bugs.eclipse.org/bugs//show_bug.cgi?id=106862 3) Annotate bug with links to comitted files for repositories that do not have atomic commits (e.g. CVS). With repository support the user could then see the exact diff that was committed.I wonder how this could be implemented. You'll have to either scan/index/index entire CVS commit log or attach links to committed files to bug report (either to server or to local Mylar's copy). 4) Link from a commit comment to a bugOutlined in Team/CVS issue at https://bugs.eclipse.org/bugs/show_bug.cgi?id=58646 There are probably other possibilities but those are the only ones we discussed.It looks like there is a need to specify issue tracking repository per-CVS/SVN repository , as well as per-project or even per-CVS/SVN module/subcomponent. Second case would allow to define exeptions for projects that are not using common issue tracking repository which is a common case on apache CVS/SVN repositories (some of them are using bugzilla and others - various external JIRA installations). regards, Eugene |