On Tue, Feb 17, 2009 at 5:46 PM, Steve Borho <[email protected]> wrote: > Hello, > > It had been my intention to keep separate issue tracking instances for > -stable and -crew, but I've changed my mind and decided to use a > single issue tracking instance on -stable that convers both > repositories. There were two primary reasons for this: > > 1) I wasn't looking forward to moving issues at release time > 2) Bitbucket now supports issue commands in commit messages, so issues > in the -stable tracker will automatically get updated when we push > properly annotated changes to the -stable repository. > > The issue commands would not work correctly if crew had it's own issue > tracker, so I've disable the crew tracker (it had no issues in it > yet). > > I've updated the contributing guidelines on the wiki to describe how > this works. Essentially, if your patch fixes issue #1 in the -stable > issue tracker, you should include 'fixes #1' in the commit message. When
Is this "#1" a syntax required by BB to in order for some systems to work? Else, I would recommend something like "BB#1" to distinctively differentiate them from SF trackers. > your patch is applied to the -stable repository, that issue will get > updated automagically. It also supports 'closes' and 'reopens'. > > http://bitbucket.org/tortoisehg/crew/wiki/contributing > > I've requested a new feature for Bitbucket, to be able to preview > issue changes that are pending in a fork, so we can easily see what > changes are fixed on crew, for instance. > > One last note: When you create a new issue, it assigns that issue to > the tortoisehg user by default. Please leave that assignment in place > as it causes all updates to that issue to be forwarded to thg-dev. > > Thanks, > > -- > Steve > > ------------------------------------------------------------------------------ > Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA > -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise > -Strategies to boost innovation and cut costs with open source participation > -Receive a $600 discount off the registration fee with the source code: SFAD > http://p.sf.net/sfu/XcvMzF8H > _______________________________________________ > Tortoisehg-develop mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/tortoisehg-develop > ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Tortoisehg-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss
