Christian Boos wrote:
Well, the custom query module is your friend... you have many ways to figure out by yourself what are the tickets that are both important (usually priority set to high or highest) and related to your areas of interest (by filtering on the component or adding a few keywords).
Yes, I've tried a few queries, but most of the time I wasn't able to differentiate important issues from less important ones. I'll try again now, after having followed trac-dev for a few weeks I should be able to do better.
The recently-installed voting feature on t.e.o should also help there.
A few wiki pages can help as well:
I had found the first one, but not the other two. Should have worn my glasses, probably. I'll look into them, and see how I can apply that. Thanks for the pointers.
Also, we should have less populated milestones, as it helps to get the focus on the more important or urgent issues. That's what I did for 0.11.1, by moving first all the previously assigned tickets to 0.11.2, so that we have a better visibility about what should go in the next release and what is simply scheduled for a given development line. I think we could eventually do the same for 0.12, first moving everything to 0.13, then selectively reschedule a few for 0.12.
You know, I hadn't even thought of looking at the roadmap... That probably comes from the fact that I use it neither at home nor at work. It definitely looks like exactly the information I was looking for.
Sometimes the ticket already contains some guidance, but if not, it's always possible to propose a solution (eventually with an initial patch to make the proposal more concrete) and ask for feedback, in the ticket itself. If there's no feedback there after a while, feel free to bug people here on Trac-dev about it.
That's where I would like to be as efficient as possible. If the ticket doesn't give me a clear idea of how to proceed, I'll probably bug people on trac-dev *before* starting. I am pretty sure that at least some core developers already have a good idea how to fix most of the issues, or at least where to look, and I'd like to get that knowledge before starting.
There are tons of problems of intermediate size related to multirepos branch. I should probably document them on the corresponding wiki page, but here are a few examples:
Thanks, I'll look into these issues and find a few others with the pointers you provided. And hopefully I'll be able to get started. I have two weeks of vacation coming up soon, so this is the right time :-)
Thanks! -- Remy
signature.asc
Description: OpenPGP digital signature
