[piccolo2d-dev] Re: Issue 160 in piccolo2d: endless calls to PSwing's ComponentListener
Updates: Status: Verified Comment #10 on issue 160 by cmal...@pixelzoom.com: endless calls to PSwing's ComponentListener http://code.google.com/p/piccolo2d/issues/detail?id=160 I verified that r965 fixes the example and our application. Marking this issue as verified. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
[piccolo2d-dev] Re: Release Piccolo2D.Java 1.3 failed
All 1.3-rc1 issues that I reported have been resolved. Many thanks! What is the timeline for 1.3-rc2, and are there any other issues still pending that must be resolved? Chris On Feb 1, 4:09 pm, cmal...@pixelzoom.com cmal...@pixelzoom.com wrote: See issue 160 for the endless series of events issue. All problems we've identified are now in the issues database. 158 and 159 are resolved. 160 is open. Chris On Feb 1, 11:03 am, cmal...@pixelzoom.com cmal...@pixelzoom.com wrote: An update on where we're at with the PSwing issues... Issue 158 was resolved by Allain last week, and fixed a couple of our problems. Issue 159 was opened a few minutes ago, and is related to PSwing transform/picking problems. I am still investigating one additional issue, where a PSwing Component is receiving an endless series of events that toggle its visibility on and off. As soon as I isolate, I'll create an issue. That summarizes all of the problems we've encountered with 1.3-rc1. Chris On Jan 28, 12:29 pm, Michael Heuer heue...@gmail.com wrote: The following people voted on release 1.3rc1: Michael Heuer +1 Allain Lalonde +1 Chris Malley -1 The vote failed since it did not receive at least three +1 binding votes and no -1 binding votes. New issues related to PSwing were discovered and are being addressed. Another release candidate (1.3rc2) will be created when these issues are closed and validated. On behalf of the Piccolo2D developers, michael -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
Re: [piccolo2d-dev] Re: Release Piccolo2D.Java 1.3 failed
Chris wrote: All 1.3-rc1 issues that I reported have been resolved. Many thanks! What is the timeline for 1.3-rc2, and are there any other issues still pending that must be resolved? If no new issues are reported this week, I should be able to have 1.3-rc2 ready by Friday. Looking ahead to deploying the 1.3 release to the maven central repository, it would be useful if we as developers could create a KEYS file and discuss how we might be able to sign each others' keys. http://www.apache.org/dev/openpgp.html http://www.apache.org/dev/release-signing.html At a minimum, the release artifacts uploaded to maven central will need to be signed by my key, acting as release manager. michael -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
[piccolo2d-dev] Re: Issue 160 in piccolo2d: endless calls to PSwing's ComponentListener
Updates: Labels: Milestone-1.3 Comment #11 on issue 160 by heue...@gmail.com: endless calls to PSwing's ComponentListener http://code.google.com/p/piccolo2d/issues/detail?id=160 (No comment was entered for this change.) -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
Re: [piccolo2d-dev] how is source control handled for release candidates?
Chris wrote: Are release candidates created from trunk, or is there a release branch? For example... Is there a 1.3 branch, used to generate 1.3 release candidates? Or is each 1.3 release candidate generated from trunk? Since 1.3-rc1 failed, I'm trying to plan for evaluation of 1.3-rc2, and what type of testing we'll need to do. Might rc2 have new problems, or will the only changes be fixes for rc1? Do we need to do thorough testing, or just regression testing of rc1 issues? The release checklist is at http://code.google.com/p/piccolo2d/wiki/ReleaseChecklist That document is a work in progress though, since the 1.3 release will the first one handled start-to-finish by the Piccolo2D community. To answer your questions, 1.3-rc2 will be generated from trunk and svn copied to a release tag tags/release-1.3-rc2. The only differences between 1.3-rc1 and 1.3-rc2 will be fixes for Verified issues 158, 159, and 160 and some updates to the release notes. I need to leave issue 146 open in case changes need to be made to the poms for uploading to maven central. Issue 126 is still in Fixed status and should be Verified by a developer other than me. michael -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
