View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0000453 | Composr build tools | [All Projects] General / Uncategorised | public | 2012-05-02 15:10 | 2012-05-25 21:48 |
Reporter | Chris Graham | Assigned To | Chris Graham | ||
Severity | Feature-request | ||||
Status | resolved | Resolution | fixed | ||
Summary | 0000453: Automatic bugfix push | ||||
Description | Scrap the bugs catalogue, and instead use the tracker. Create a simple script that does the following: - Asks for a tracker issue number (optional) - Asks for a forum post ID number (optional) - Asks for a bug explanation - Asks for what files are changed (but automatically scans the filesystem to give a good guess) - If no tracker issue number was given, one is made - A tar of fixed files is uploaded to the tracker issue (correct relative file paths intact) - A diff is also uploaded - If a forum post ID was given, an automatic reply is given pointing to the tracker issue - The tracker issue gets closed - A git commit and push happens on the changed files, with the ID number of the tracker issue in it The release scripts would need modifying a bit to point to the tracker rather than the old bugs database. | ||||
Tags | No tags attached. | ||||
Time estimation (hours) | 8 | ||||
Sponsorship open | |||||
|
Ideally Composr would provide inbuilt support for detection of these hotfixes, with links to apply them, and to revert them. It would need to be intelligent enough to look at file modification times, to not apply old fixes. |
|
Done, with small changes: - Link to github for diffing purposes - Bugs catalogue renames, as a neat list of links into the tracker for notable issues - Inbuilt hotfix application not needed due to the bug catalogue remaining - that works for similar purposes; a little less automated, but that is safer |
Date Modified | Username | Field | Change |
---|---|---|---|
2023-02-26 18:29 | Chris Graham | Category | General => General / Uncategorised |