HostedRedmine.com has moved to the Planio platform. All logins and passwords remained the same. All users will be able to login and use Redmine just as before. Read more...
Task #896778
Inspect new bug/patch tracker options, potentially migrate
0%
Description
We can't have new users to hostedredmine reporting bugs after it became part of planio. Inspect our options, and migrate.
Plan is to look at this after 2.6.2.1 and 3.0.0-alpha5 releases are out of the way. Hopefully things are settled already before 2.6.3 release, so we can advertise correct BUG_URL at it.
Related issues
History
#1
Updated by Marko Lindqvist over 1 year ago
- Related to Feature #894573: Resolve BUG_URL for near future added
#2
Updated by Marko Lindqvist over 1 year ago
- Related to Task #765919: Enable issues in GitHub added
#3
Updated by Marko Lindqvist over 1 year ago
- Sprint/Milestone changed from 2.6.3 to 2.6.4
One of the options is https://osdn.net/
#4
Updated by Marko Lindqvist over 1 year ago
- Status changed from New to In Progress
#5
Updated by Marko Lindqvist over 1 year ago
Things of interest to us that osdn and github are lacking.
OSDN;
- Only open/closed status, no way to indicate "Review Period"
- No relations between tickets - no metatickets
github:
- No way to indicate "Review Period"
- No relations between tickets - no metatickets
- Doesn't work well for non-code related project management Task tickets
- No components
- No types (bug/patch/task/milestone/deliverable)
(I sort of gave up with github at this point of the evaluation, so didn't really think through what else it lacks)
So, osdn is not good, but by far better than github.
#6
Updated by Marko Lindqvist over 1 year ago
My proposal for OSDN ticketing system pilot test:
#7
Updated by Marko Lindqvist over 1 year ago
- File 0002-Update-BUG_URL-to-point-to-osdn.patch 0002-Update-BUG_URL-to-point-to-osdn.patch added
- Category set to General
- Status changed from In Progress to Resolved
Patch to document osdn as the tracking site to use in S2_6 too.
#8
Updated by Marko Lindqvist over 1 year ago
- Update ticketing system link in doc/TODO
#9
Updated by Marko Lindqvist about 1 year ago
Marko Lindqvist wrote:
Patch to document osdn as the tracking site to use in S2_6 too.
Are we now convinced enough with osdn to push this patch in, and to release 2.6.4 with documentation pointing to osdn as the bug tracker?
#10
Updated by Sveinung Kvilhaugsvik about 1 year ago
Marko Lindqvist wrote:
Marko Lindqvist wrote:
Patch to document osdn as the tracking site to use in S2_6 too.
Are we now convinced enough with osdn to push this patch in, and to release 2.6.4 with documentation pointing to osdn as the bug tracker?
I have not seen a dependency between issue marker to document why a small, apparently independent change was done in osdn. (Maybe we should keep a pre draft of the release notes in Git so we can document it there? With the understanding that anything there can be completely rewritten or even dropped when the real release notes a re created?) I have also experienced that patch files refuse to upload to osdn for a while but it will start working again. While osdn isn't ideal it is what we have where users without existing hrm accounts can post. I therefore vote yes.
#11
Updated by Marko Lindqvist about 1 year ago
- Status changed from Resolved to Closed
- Assignee set to Marko Lindqvist