[Netarchivesuite-devel] Tip for relating commits to JIRA issues

[Mikis Seth Sørensen]

Hi Nicolas

Thanks for the positive feedback.

Note that we are also planning the following additional migrations to SBForge: NetarchiveSuite migration<https://sbforge.org/jira/browse/NAS-51>.


One thing which might also be relevant for BNF, was a switch to using git<http://git-scm.com/> for source control management. Git is a Distributed Source Control Management, so it provides much better support for local repositories, branching and merging than Subversion (in return for a bit of extra complexity). Have a look at the concept and consider whether this would be of value to you.

~Mikis

From: Nicolas Giraud <nikokode at gmail.com<mailto:nikokode at gmail.com>>
Reply-To: "netarchivesuite-devel at lists.gforge.statsbiblioteket.dk<mailto:netarchivesuite-devel at lists.gforge.statsbiblioteket.dk>" <netarchivesuite-devel at lists.gforge.statsbiblioteket.dk<mailto:netarchivesuite-devel at lists.gforge.statsbiblioteket.dk>>
Date: Fri, 1 Apr 2011 11:14:27 +0200
To: "netarchivesuite-devel at lists.gforge.statsbiblioteket.dk<mailto:netarchivesuite-devel at lists.gforge.statsbiblioteket.dk>" <netarchivesuite-devel at lists.gforge.statsbiblioteket.dk<mailto:netarchivesuite-devel at lists.gforge.statsbiblioteket.dk>>
Subject: Re: [Netarchivesuite-devel] Tip for relating commits to JIRA issues

Hi Mikis,

Switching to Jira is definitely a huge improvement in the project's daily life, I'm extremely happy with it, and I will make a presentation to my coworkers at BnF. I'd like to set up a kind of "Jira incubator" at BnF, because the "official" BnF tracker is a really old and crappy one (that's my opinion here ;p).

Congratulations for that great work of moving from GForge to Jira!

Nicolas

2011/3/31 Mikis Seth Sørensen <mss at statsbiblioteket.dk<mailto:mss at statsbiblioteket.dk>>
Hi

Because we are now using JIRA for our issue management, we can starting relating svn changesets to specific JIRA issue by including the key of the JIRA issue in the commit message. This means that an issue will list all related change sets (that is commits with the issue key included in the commit message) under the 'Source' tab at the bottom of the issue page.

This will also enable us to create Crucible reviews directly from the 'Source' list under the issue. Reviews created this way will the appear under the 'Reviews' tab. Note that we should use this feature before the switch to SBForge Crucible has been completed (in a week or two).

See <https://sbforge.org/jira/browse/BITMAG-41?page=com.atlassian.jirafisheyeplugin%3Afisheye-issuepanel#issue-tabs> h<https://sbforge.org/jira/browse/BITMAG-41?page=com.atlassian.jirafisheyeplugin%3Afisheye-issuepanel#issue-tabs>ere<https://sbforge.org/jira/browse/BITMAG-41?page=com.atlassian.jirafisheyeplugin%3Afisheye-issuepanel#issue-tabs> for an example of a issue with a rich source and review context.

See the SBForge JIRA<https://sbforge.org/display/APP/JIRA> documentation for further documentation on using JIRA's issue model from different tools.

Have fun
Mikis

_______________________________________________
Netarchivesuite-devel mailing list
Netarchivesuite-devel at lists.gforge.statsbiblioteket.dk<mailto:Netarchivesuite-devel at lists.gforge.statsbiblioteket.dk>
https://lists.gforge.statsbiblioteket.dk/mailman/listinfo/netarchivesuite-devel




--
Nicolas Giraud
---------------------------------------------------------------------------------------------
Développeur Archives du Web - Bibliothèque Nationale de France
Web Archiving Developper - National Library of France
---------------------------------------------------------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://ml.sbforge.org/pipermail/netarchivesuite-devel/attachments/20110401/554bada3/attachment-0002.html>