Hi! > > Either that or it remains open till committed to both. > > Any views? > > My suggestion: > - Assign the issues that will go to 0.26.1 to the 0.26.1 milestone. > - Commit to trunk. Preferrably a single commit per issue, stating for > each issue is related in the log comment. > - Mark the issue as closed (so I know that anything else needs to be done) > > Once closed, I'll test the patch and commit to the branch.
I'd prefer to put it on resolved fixed iff it is fixed in both branch and trunk. As soon as you've committed to the branch, you can put it on resolved fixed. But I'm OK with your suggestion, because you trace the issues by target anyway. I leave it open. Do we have a decision? Thomas -- GMX Kostenlose Spiele: Einfach online spielen und Spaß haben mit Pastry Passion! http://games.entertainment.gmx.net/de/entertainment/games/free/puzzle/6169196 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
