Hi,
I just merged several patches into the 1.0 branch. I am going to be
working on fixing any 1.0 blockers, I am largely targeting
regressions, and would not be against making another 1.0 release
should there be more fixes in the 1.0 branch. Many distros are already
patching around the SIP API breaks.
I will be aiming to tag early next week if possible, but please let me
know about release blockers. We already have quite a few unreleased
fixes in the 1.0 branch that should be tagged sooner rather than
later.
Marcus
Marcus D. Hanwell, Ph.D.
R&D Engineer, Kitware Inc.
(518) 881-4937
Hi,
On Fri, Jan 28, 2011 at 02:29:00PM -0500, Marcus D. Hanwell wrote:
I will be aiming to tag early next week if possible, but please let me
know about release blockers. We already have quite a few unreleased
fixes in the 1.0 branch that should be tagged sooner rather than
later.
Maybe have a release candidate for a few days so people can easily
verify their bugs are indeed fixed.
Michael
On Sun, Jan 30, 2011 at 11:22 AM, Michael Banck mbanck@gmx.net wrote:
Hi,
On Fri, Jan 28, 2011 at 02:29:00PM -0500, Marcus D. Hanwell wrote:
I will be aiming to tag early next week if possible, but please let me
know about release blockers. We already have quite a few unreleased
fixes in the 1.0 branch that should be tagged sooner rather than
later.
Maybe have a release candidate for a few days so people can easily
verify their bugs are indeed fixed.
Good suggestion, I was thinking of doing that. I will create a
1.0.2_rc0 once most of the patches are merged into 1.0.
Marcus