Lol, I can't imagine anyone diving into the 2.x resolution code again.
Punt them to 3.x
On Mon, Dec 28, 2009 at 8:22 PM, Jason van Zyl wrote:
> Then anything I see I will just move to 3.x because I honestly don't think
> anyone is going to fix them in 2.x and the code is too different now to
>
Then anything I see I will just move to 3.x because I honestly don't think
anyone is going to fix them in 2.x and the code is too different now to
backport any of it.
On 2009-12-28, at 8:13 PM, Brett Porter wrote:
> If they are fixed in 3.x, it'd be good to just close them out. Ideally, point
If they are fixed in 3.x, it'd be good to just close them out. Ideally, point
them at the issue that resolves them though as superceded / duplicate. Folks
will keep coming across them at a later date searching for something in the 2.x
line.
- Brett
On 28/12/2009, at 8:11 AM, Jason van Zyl wrot
Is anyone planning on actually doing any bug fixing in the 2.x artifact
resolution code?
Lots of this stuff has been fixed in 3.x and I was just going to push any bugs
I saw in JIRA to 3.x and validate as fixed and for the ones that aren't
schedule them to be fixed.
I don't think at this poin