Opened 11 years ago
Last modified 10 years ago
#11588 new enhancement
Backport Apache Bloodhound resource neighborhood implementation
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | undecided |
Component: | general | Version: | 1.1.1dev |
Severity: | normal | Keywords: | resources, integrations |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
Resource neighbourhoods are aimed to connect Trac instances to external resource managers (issue trackers , build systems , …) . This ticket is aimed at :
- Proposing back ports for this feature into the Trac core
- Providing a basic implementation of neighbourhoods for sibling Trac environments .
Attachments (0)
Change History (5)
comment:1 by , 11 years ago
comment:2 by , 11 years ago
This longer test run seems to confirm that there are no regressions after applying the patch .
$ python trac/tests/__init__.py SKIP: versioncontrol/tests/functional.py (no svn bindings) ........................................................................................................................................................................................................................................................................................................................... ---------------------------------------------------------------------- Ran 315 tests in 328.642s OK
follow-up: 4 comment:3 by , 11 years ago
comment:4 by , 11 years ago
Replying to rblank:
I would appreciate a bit more detail on resource neighborhoods and what problems they solve. Are they somehow related to InterTrac and InterWiki?
Somehow , yes … InterTrac and InterWiki is about linking to another web site using WikiFormatting . Neighnorhoods are about integrating external resources (relative to the current environment) so you also get a title , a meaningful description and so on …. plus everything that can be done with resources of course .
comment:5 by , 10 years ago
Milestone: | → undecided |
---|
milestone:undecided for now, but I'll look at it during milestone:1.1.3.
There is a patch available . Initial test results seem to be ok .