Hi Dammina, Bloodhound has a copy of Trac with several patches applied. I don't recall the last version of Trac that was merged into Bloodhound, but I think it was at least 1.0.2.
You'll need to grab a new copy of Trac and merge that into the Bloodhound codebase. Alternatively, you could rebase it by adding the new version of Trac and applying all the patches on top of it. To make things easier in the future you can propose changes to Trac that would make some of the patches unnecessary. I did some work on that when I merged a version of Trac into Bloodhound. Trac 1.2 should be released soon, so I'd make that the next target for merging into Bloodhound, although you could merge in Trac 1.0.12 first if you'd prefer to try for incremental progress. Trac 1.3.x releases are the development snapshots leading to the next major release (1), Trac 1.4. Trac will replace the Genshi with Jinja2 templating engine, so Bloodhound would need to adapt all it's templates to work with Trac 1.4. I'd approach the problem like this: * Fork Bloodhound on GitHub * Review the change history of the copy of Trac in Bloodhound and create a logical set of patches * Replace the copy of Trac in Bloodhound with Trac 1.2 * Apply each of the patches to the new copy * Review change history of the templates in Trac and apply the changes to the Bloodhound templates I could work with you to review the patches and see what might be backported to Trac. I don't anticipate doing any additional work directly in the Bloodhound codebase, but I'm happy to work with you guys to make your integration with Trac work as well as possible. I may also backport some of the Bloodhound plugins, such as ticket references, to Trac. - Ryan (1) https://trac.edgewall.org/wiki/RoadMap#MilestoneCategories On Fri, Sep 2, 2016 at 10:37 AM Dammina Sahabandu <[email protected]> wrote: > Hi Ryan, > > It seems like the latest Trac development release is Trac 1.3.1, and BH is > still using Trac 1.0.1. Even though you have suggested the migration even > before the release of Trac 1.2 I guess we are still not too late. So I > would be happy to do the migration if you can provide me some guidance. > > Thanks, > Dammina. > > > On Thu, Jan 21, 2016 at 6:43 AM, Ryan J Ollos <[email protected]> wrote: > > > On Wed, Jan 20, 2016 at 1:08 PM, Gary <[email protected]> wrote: > > > > > Hi everyone, > > > > > > For Kunaal's request to be viable we need to start getting some > momentum > > > back into development. In addition, although I expect to be able to > take > > > on all the responsibility for mentoring a student, I believe that we > > > would require a second mentor who is also on the PMC. As that suggests > > > such a person is required to ensure that a GSoC student is looked after > > > if the main mentor becomes unexpectedly unavailable. Of course, if the > > > second mentor wanted to be equally involved, that would be even better. > > > > > > So, if anyone is interested in helping out as a mentor, or has time to > > > make some progress with development, please let us know. > > > > > > Cheers, > > > Gary > > > > > > I don't foresee myself finding any time for Bloodhound given the > > commitments I have to other open source projects. > > > > For the Bloodhound project, an important step is to move to Trac 1.0.9, > and > > the soon-to-be-released Trac 1.2. If anyone can find time to work on > those > > migrations, I can lend advice since I'm very familiar with the changes > that > > have been made in Trac. > > > > - Ryan > > > > > > -- > Dammina Sahabandu > SSE, AdroitLogic (pvt) Ltd. > Committer, Apache Software Foundation > AMIE (SL) > Bsc Eng Hons (Moratuwa) > +94716422775 >
