Rene Rivera wrote:
Guillaume Melquiond wrote:
I have not followed the discussion closely, so I am probably missing something, but why a new milestone? Unless I'm mistaken, issues that are "fixed", "closed", and with a "1.35" milestone, are precisely issues that will be fixed in the release (unless the relevant patches are reverted). So I don't understand the need for a new milestone.
For exactly the "unless the relevant patches are reverted" situation.
Right: currently when something assigned to me was targeted for 1.35 I closed it once it was fixed in the Trunk: otherwise there's no way to tell what's been dealt with already :-) So I would actually be in favour of either a "pending merge to release" state, or else a new milestone for "1.35 Release Branch". Regards, John.