You are viewing a plain text version of this content. The canonical link for it is here.
Posted to npanday-dev@incubator.apache.org by Lars Corneliussen <me...@lcorneliussen.de> on 2011/04/20 09:00:36 UTC
Get the release out the door
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
Re: Status for 1.3.1-incubating
Posted by John Fallows <jo...@kaazing.com>.
NPANDAY-412 input is coming later today.
tc,
-john.
On Sun, May 1, 2011 at 3:27 PM, Lars Corneliussen <me...@lcorneliussen.de>wrote:
> 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
>>
>>
>>
>
--
>|< Kaazing Corporation >|<
John Fallows | CTO | +1.650.960.8148
444 Castro St, Suite 1100 | Mountain View, CA 94041, USA
Status for 1.3.1-incubating
Posted by Lars Corneliussen <me...@lcorneliussen.de>.
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
>
>
Re: Get the release out the door
Posted by Lars Corneliussen <me...@lcorneliussen.de>.
Am 20.04.11 16:05, schrieb Brett Porter:
> On 20/04/2011, at 7:00 PM, Lars Corneliussen wrote:
>
>> 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?)
> I added some comments already. I don't have enough time to dig into the code to find out why it's generated the wrong settings file for me right now.
Hm. Who has a similar setup then? I think on your machine we just have
to lookup some additional registry paths.
With screensharing we'll need 10-15 minutes to find out whats wrong.
>> 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
>>
>>
> --
> Brett Porter
> brett@apache.org
> http://brettporter.wordpress.com/
> http://au.linkedin.com/in/brettporter
>
>
>
>
Re: Get the release out the door
Posted by Brett Porter <br...@apache.org>.
On 20/04/2011, at 7:00 PM, Lars Corneliussen wrote:
> 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?)
I added some comments already. I don't have enough time to dig into the code to find out why it's generated the wrong settings file for me right now.
>
> 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
>
>
--
Brett Porter
brett@apache.org
http://brettporter.wordpress.com/
http://au.linkedin.com/in/brettporter