Hi,
we have 6 open issues, still.
123 needs attention. Who has a "old" machine to test it on? We could
also release RC, and have it tested there.
-> 412 relates to this, too
377 is in progress. Should be resolved tomorrow.
383, who can rename the group ids?
403 successful generation of poms after clicking on Cancel button,
*Unassigned*, reported by Liit
Liit, what is to be done to resolve this issue?
412 Execuable path for Windows 7 SDK is not auto-detected when
npanday-settings.xml is generated, resgen.exe not found
John, I need input from you here.
398 MojoGenerator can't generate .NET-Mojos referencing a newer
NPanday.Plugin.dll
Joe, you wanted to take care of this. What is the status?
_
Lars
Hi,
we have only six todos left:
383 groupid to org.apache.npanday, *unassigned*, reported by liit
377 hardcoded path in registry-config.xml, *liit*
387 Improve checking of mirror repos, *Unassigned*, reported by Joe
389 MojoGenerator can't generate .NET-Mojos referencing a newer
NPanday.Plugin.dll, *Joe*, reported by Lars
403 successful generation of poms after clicking on Cancel button,
*Unassigned*, reported by Liit
123 building without path, *Brett* (testing and fixes?)
1) When should we do 383? After "code/feature freeze" as part of
release preparation?
2) Who will take care of 403?
3) Which dates should we target for "code/feature freeze"? I'd suggest
Apr. 27th - one week from now.
4) Who will take care of the release preparations? What date should we
target for the first RC? I'd suggest April 29th or May 2nd.
_
Lars
