Re: [Bf-committers] Blender 2.59 release AHOY!
Hello, While I was packaging this last Blender version for Debian, I noticed there is no svn tag for 2.59 . I use this tag in my preparation-for-build script to create the upstream tarball. Cheers On 10 August 2011 18:22, Campbell Barton ideasma...@gmail.com wrote: Hi devs, I've been keeping an eye on the tracker for new reports since our 2.59RC release and am happy we don't have any real show stoppers. Thomas committed the splash, we have version bumped so think its time to build! Since there is some secret to tagging trunk, lib extensions that Nathan isn't around to impart, for now just build from revisions. Trunk: r39263 Extensions: r2241 I'll be available tomorrow to help with getting the uploads copied to the download dir and update changelog typo3 pages. Really happy with this release :), thanks to everyone for you're contributions! - Campbell ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] Blender 2.59 release AHOY!
Why don't you just shift the release date (by one week for example), fix the issues as needed and keep trunk frozen for that period ? Wouldn't that help to get out an excellent release and avoid to push out 2.59b one week after 2.59 was released ? Am 12.08.2011 07:52, schrieb Sergey I. Sharybin: Hi, I've got fix for grease pencil in mu branch [1], but it's really that kind of changes which shouldn't be applied in last minute (at least there are several possible issues i wanted to check), so let's limit GP a bit for 2.59. About reloading scripts and so. I've been working on UI in my branch after merging ghash changes there and haven't found any bad sides of this change. About more clear release next time. I'm not sure why this release is so crazy. Is it our lag, lag of coordination or so.. [1] http://projects.blender.org/scm/viewvc.php?view=revroot=bf-blenderrevision=39313 P.S. linux 32/64 bit would be available soon. Campbell Barton wrote: Hi, woke up to find a re-release from a revision that contains changes I made that were *not* intended to be in a stable release - switching operators and menus to hash lookups. We should have branched at r39259 stable and applied patches there before re-releasing. There is also the issue with grease pencil session - where the operator points to data that can be freed on 'Global Undo' (as opposed to the crasher with the modal operators own *fake* undo, fixed 39237 and double undos fixed 39235). Sergey's fix means you can't move the viewport while grease pencil session is enable so the option is now not at all working as it was meant. *Sigh* Since there were 3 fairly bad bugs in this tool (2 crashers), my impression is that option isn't used all that much. A correct fix isn't some small edit, the operator must store data differently, this should have been picked up during normal development, IMHO we should not attempt to sort this out as a last-minute, show-stopper fix. There is the remaining issue: Do we use current bsd/linux/mac builds from r39304 (and wait on win build before announcing), Or re-branch from 39259 and apply a few fixes there and rebuild on all platforms. By not re-branching we break our own guidelines - to unfreeze quick but use a branch for fixes and it feels very sloppy to me. On the other hand my change of moving operators/menu's into a hash isn't that big a deal and works with scripts reloading, freeing, re-registering operators etc - I would expect any bugs here would be obvious and break blender immediately, so I *think* they are safe. Suggest to go ahead with r39304, but next release be more clear with release tag/branch, and the following unfreeze. - Campbell On Fri, Aug 12, 2011 at 3:58 AM, Kent Meinm...@cs.umn.edu wrote: In reply to Sergey I. Sharybin (g.ula...@gmail.com): Didn't know OSX still have got issues with non-trunk verison. I've just commited patch from Jens to solve this problems. We prefer to keep revisions synced for all platforms, so please use Trunk: r39307 Extensions: r2241 Updated tarball of the source and md5sum are in incoming on ftp.blender.org Kent ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] Blender 2.59 release AHOY!
This issue (IMHO) is not worth holding back the release for, we can review Sergey's fix and have it ready for next release. We now have 200 bugs in the tracker, so unless new bugs are found that are regressions from previous releases we're better off sticking to a more strict release cycle, 2.59 release we have now fixes ~140 bugs since 2.58 so IMHO users are still better off with the update and not waiting longer. On Fri, Aug 12, 2011 at 8:22 PM, Jass gaia.cl...@machinimatrix.org wrote: Why don't you just shift the release date (by one week for example), fix the issues as needed and keep trunk frozen for that period ? Wouldn't that help to get out an excellent release and avoid to push out 2.59b one week after 2.59 was released ? Am 12.08.2011 07:52, schrieb Sergey I. Sharybin: Hi, I've got fix for grease pencil in mu branch [1], but it's really that kind of changes which shouldn't be applied in last minute (at least there are several possible issues i wanted to check), so let's limit GP a bit for 2.59. About reloading scripts and so. I've been working on UI in my branch after merging ghash changes there and haven't found any bad sides of this change. About more clear release next time. I'm not sure why this release is so crazy. Is it our lag, lag of coordination or so.. [1] http://projects.blender.org/scm/viewvc.php?view=revroot=bf-blenderrevision=39313 P.S. linux 32/64 bit would be available soon. Campbell Barton wrote: Hi, woke up to find a re-release from a revision that contains changes I made that were *not* intended to be in a stable release - switching operators and menus to hash lookups. We should have branched at r39259 stable and applied patches there before re-releasing. There is also the issue with grease pencil session - where the operator points to data that can be freed on 'Global Undo' (as opposed to the crasher with the modal operators own *fake* undo, fixed 39237 and double undos fixed 39235). Sergey's fix means you can't move the viewport while grease pencil session is enable so the option is now not at all working as it was meant. *Sigh* Since there were 3 fairly bad bugs in this tool (2 crashers), my impression is that option isn't used all that much. A correct fix isn't some small edit, the operator must store data differently, this should have been picked up during normal development, IMHO we should not attempt to sort this out as a last-minute, show-stopper fix. There is the remaining issue: Do we use current bsd/linux/mac builds from r39304 (and wait on win build before announcing), Or re-branch from 39259 and apply a few fixes there and rebuild on all platforms. By not re-branching we break our own guidelines - to unfreeze quick but use a branch for fixes and it feels very sloppy to me. On the other hand my change of moving operators/menu's into a hash isn't that big a deal and works with scripts reloading, freeing, re-registering operators etc - I would expect any bugs here would be obvious and break blender immediately, so I *think* they are safe. Suggest to go ahead with r39304, but next release be more clear with release tag/branch, and the following unfreeze. - Campbell On Fri, Aug 12, 2011 at 3:58 AM, Kent Meinm...@cs.umn.edu wrote: In reply to Sergey I. Sharybin (g.ula...@gmail.com): Didn't know OSX still have got issues with non-trunk verison. I've just commited patch from Jens to solve this problems. We prefer to keep revisions synced for all platforms, so please use Trunk: r39307 Extensions: r2241 Updated tarball of the source and md5sum are in incoming on ftp.blender.org Kent ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers -- - Campbell ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] Blender 2.59 release AHOY!
I don't think way of fixing discovered bug _so_ bad. There were several crashes there in 2.58 and there was no report in tracker about this -- users simply not using this tool much or using them in safe way. And disabling things which can be unstable ,we can be sure there's no hidden problems and this allows to make release more stable. Jass wrote: Why don't you just shift the release date (by one week for example), fix the issues as needed and keep trunk frozen for that period ? Wouldn't that help to get out an excellent release and avoid to push out 2.59b one week after 2.59 was released ? -- With best regards, Sergey I. Sharybin ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] Blender 2.59 release AHOY!
As painful as this attitude seems, I'd have to agree with it. The idea here is to modify expectations -- mostly on the developers part. Umgiven that the next number is to be 6.0 I wouldn't mind seeing that 200 bugs turn into 0 bugs in the near future rather than have to learn new UI. It's really nice when round numbers mean pretty product. On Fri, Aug 12, 2011 at 6:45 AM, Campbell Barton ideasma...@gmail.com wrote: This issue (IMHO) is not worth holding back the release for, we can review Sergey's fix and have it ready for next release. We now have 200 bugs in the tracker, so unless new bugs are found that are regressions from previous releases we're better off sticking to a more strict release cycle, 2.59 release we have now fixes ~140 bugs since 2.58 so IMHO users are still better off with the update and not waiting longer. On Fri, Aug 12, 2011 at 8:22 PM, Jass gaia.cl...@machinimatrix.org wrote: Why don't you just shift the release date (by one week for example), fix the issues as needed and keep trunk frozen for that period ? Wouldn't that help to get out an excellent release and avoid to push out 2.59b one week after 2.59 was released ? Am 12.08.2011 07:52, schrieb Sergey I. Sharybin: Hi, I've got fix for grease pencil in mu branch [1], but it's really that kind of changes which shouldn't be applied in last minute (at least there are several possible issues i wanted to check), so let's limit GP a bit for 2.59. About reloading scripts and so. I've been working on UI in my branch after merging ghash changes there and haven't found any bad sides of this change. About more clear release next time. I'm not sure why this release is so crazy. Is it our lag, lag of coordination or so.. [1] http://projects.blender.org/scm/viewvc.php?view=revroot=bf-blenderrevision=39313 P.S. linux 32/64 bit would be available soon. Campbell Barton wrote: Hi, woke up to find a re-release from a revision that contains changes I made that were *not* intended to be in a stable release - switching operators and menus to hash lookups. We should have branched at r39259 stable and applied patches there before re-releasing. There is also the issue with grease pencil session - where the operator points to data that can be freed on 'Global Undo' (as opposed to the crasher with the modal operators own *fake* undo, fixed 39237 and double undos fixed 39235). Sergey's fix means you can't move the viewport while grease pencil session is enable so the option is now not at all working as it was meant. *Sigh* Since there were 3 fairly bad bugs in this tool (2 crashers), my impression is that option isn't used all that much. A correct fix isn't some small edit, the operator must store data differently, this should have been picked up during normal development, IMHO we should not attempt to sort this out as a last-minute, show-stopper fix. There is the remaining issue: Do we use current bsd/linux/mac builds from r39304 (and wait on win build before announcing), Or re-branch from 39259 and apply a few fixes there and rebuild on all platforms. By not re-branching we break our own guidelines - to unfreeze quick but use a branch for fixes and it feels very sloppy to me. On the other hand my change of moving operators/menu's into a hash isn't that big a deal and works with scripts reloading, freeing, re-registering operators etc - I would expect any bugs here would be obvious and break blender immediately, so I *think* they are safe. Suggest to go ahead with r39304, but next release be more clear with release tag/branch, and the following unfreeze. - Campbell On Fri, Aug 12, 2011 at 3:58 AM, Kent Meinm...@cs.umn.edu wrote: In reply to Sergey I. Sharybin (g.ula...@gmail.com): Didn't know OSX still have got issues with non-trunk verison. I've just commited patch from Jens to solve this problems. We prefer to keep revisions synced for all platforms, so please use Trunk: r39307 Extensions: r2241 Updated tarball of the source and md5sum are in incoming on ftp.blender.org Kent ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers -- - Campbell ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers -- No essence. No permanence. No perfection. Only action. ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] Blender 2.59 release AHOY!
Just so I'm not confused as a platform builder... are the 39307 builds ok, or are we building again? lol On Fri, Aug 12, 2011 at 8:59 AM, Jim Williams sphere1...@gmail.com wrote: As painful as this attitude seems, I'd have to agree with it. The idea here is to modify expectations -- mostly on the developers part. Umgiven that the next number is to be 6.0 I wouldn't mind seeing that 200 bugs turn into 0 bugs in the near future rather than have to learn new UI. It's really nice when round numbers mean pretty product. On Fri, Aug 12, 2011 at 6:45 AM, Campbell Barton ideasma...@gmail.com wrote: This issue (IMHO) is not worth holding back the release for, we can review Sergey's fix and have it ready for next release. We now have 200 bugs in the tracker, so unless new bugs are found that are regressions from previous releases we're better off sticking to a more strict release cycle, 2.59 release we have now fixes ~140 bugs since 2.58 so IMHO users are still better off with the update and not waiting longer. On Fri, Aug 12, 2011 at 8:22 PM, Jass gaia.cl...@machinimatrix.org wrote: Why don't you just shift the release date (by one week for example), fix the issues as needed and keep trunk frozen for that period ? Wouldn't that help to get out an excellent release and avoid to push out 2.59b one week after 2.59 was released ? Am 12.08.2011 07:52, schrieb Sergey I. Sharybin: Hi, I've got fix for grease pencil in mu branch [1], but it's really that kind of changes which shouldn't be applied in last minute (at least there are several possible issues i wanted to check), so let's limit GP a bit for 2.59. About reloading scripts and so. I've been working on UI in my branch after merging ghash changes there and haven't found any bad sides of this change. About more clear release next time. I'm not sure why this release is so crazy. Is it our lag, lag of coordination or so.. [1] http://projects.blender.org/scm/viewvc.php?view=revroot=bf-blenderrevision=39313 P.S. linux 32/64 bit would be available soon. Campbell Barton wrote: Hi, woke up to find a re-release from a revision that contains changes I made that were *not* intended to be in a stable release - switching operators and menus to hash lookups. We should have branched at r39259 stable and applied patches there before re-releasing. There is also the issue with grease pencil session - where the operator points to data that can be freed on 'Global Undo' (as opposed to the crasher with the modal operators own *fake* undo, fixed 39237 and double undos fixed 39235). Sergey's fix means you can't move the viewport while grease pencil session is enable so the option is now not at all working as it was meant. *Sigh* Since there were 3 fairly bad bugs in this tool (2 crashers), my impression is that option isn't used all that much. A correct fix isn't some small edit, the operator must store data differently, this should have been picked up during normal development, IMHO we should not attempt to sort this out as a last-minute, show-stopper fix. There is the remaining issue: Do we use current bsd/linux/mac builds from r39304 (and wait on win build before announcing), Or re-branch from 39259 and apply a few fixes there and rebuild on all platforms. By not re-branching we break our own guidelines - to unfreeze quick but use a branch for fixes and it feels very sloppy to me. On the other hand my change of moving operators/menu's into a hash isn't that big a deal and works with scripts reloading, freeing, re-registering operators etc - I would expect any bugs here would be obvious and break blender immediately, so I *think* they are safe. Suggest to go ahead with r39304, but next release be more clear with release tag/branch, and the following unfreeze. - Campbell On Fri, Aug 12, 2011 at 3:58 AM, Kent Meinm...@cs.umn.edu wrote: In reply to Sergey I. Sharybin (g.ula...@gmail.com): Didn't know OSX still have got issues with non-trunk verison. I've just commited patch from Jens to solve this problems. We prefer to keep revisions synced for all platforms, so please use Trunk: r39307 Extensions: r2241 Updated tarball of the source and md5sum are in incoming on ftp.blender.org Kent ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers -- - Campbell ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers -- No essence. No permanence. No perfection. Only action. ___ Bf-committers mailing list Bf-committers@blender.org
Re: [Bf-committers] Blender 2.59 release AHOY!
Yep 39307 I'd prefer if this thread keeps on topic for devs release maintainers and have discussion about general changes in policy, opinions on best practice etc in a different thread. Theres some issues I'd like to bring up too but best do this after siggraph when more of the devs are reading the mailing list. On Sat, Aug 13, 2011 at 12:28 AM, pete larabell xgl.asyl...@gmail.com wrote: Just so I'm not confused as a platform builder... are the 39307 builds ok, or are we building again? lol On Fri, Aug 12, 2011 at 8:59 AM, Jim Williams sphere1...@gmail.com wrote: As painful as this attitude seems, I'd have to agree with it. The idea here is to modify expectations -- mostly on the developers part. Umgiven that the next number is to be 6.0 I wouldn't mind seeing that 200 bugs turn into 0 bugs in the near future rather than have to learn new UI. It's really nice when round numbers mean pretty product. On Fri, Aug 12, 2011 at 6:45 AM, Campbell Barton ideasma...@gmail.com wrote: This issue (IMHO) is not worth holding back the release for, we can review Sergey's fix and have it ready for next release. We now have 200 bugs in the tracker, so unless new bugs are found that are regressions from previous releases we're better off sticking to a more strict release cycle, 2.59 release we have now fixes ~140 bugs since 2.58 so IMHO users are still better off with the update and not waiting longer. On Fri, Aug 12, 2011 at 8:22 PM, Jass gaia.cl...@machinimatrix.org wrote: Why don't you just shift the release date (by one week for example), fix the issues as needed and keep trunk frozen for that period ? Wouldn't that help to get out an excellent release and avoid to push out 2.59b one week after 2.59 was released ? Am 12.08.2011 07:52, schrieb Sergey I. Sharybin: Hi, I've got fix for grease pencil in mu branch [1], but it's really that kind of changes which shouldn't be applied in last minute (at least there are several possible issues i wanted to check), so let's limit GP a bit for 2.59. About reloading scripts and so. I've been working on UI in my branch after merging ghash changes there and haven't found any bad sides of this change. About more clear release next time. I'm not sure why this release is so crazy. Is it our lag, lag of coordination or so.. [1] http://projects.blender.org/scm/viewvc.php?view=revroot=bf-blenderrevision=39313 P.S. linux 32/64 bit would be available soon. Campbell Barton wrote: Hi, woke up to find a re-release from a revision that contains changes I made that were *not* intended to be in a stable release - switching operators and menus to hash lookups. We should have branched at r39259 stable and applied patches there before re-releasing. There is also the issue with grease pencil session - where the operator points to data that can be freed on 'Global Undo' (as opposed to the crasher with the modal operators own *fake* undo, fixed 39237 and double undos fixed 39235). Sergey's fix means you can't move the viewport while grease pencil session is enable so the option is now not at all working as it was meant. *Sigh* Since there were 3 fairly bad bugs in this tool (2 crashers), my impression is that option isn't used all that much. A correct fix isn't some small edit, the operator must store data differently, this should have been picked up during normal development, IMHO we should not attempt to sort this out as a last-minute, show-stopper fix. There is the remaining issue: Do we use current bsd/linux/mac builds from r39304 (and wait on win build before announcing), Or re-branch from 39259 and apply a few fixes there and rebuild on all platforms. By not re-branching we break our own guidelines - to unfreeze quick but use a branch for fixes and it feels very sloppy to me. On the other hand my change of moving operators/menu's into a hash isn't that big a deal and works with scripts reloading, freeing, re-registering operators etc - I would expect any bugs here would be obvious and break blender immediately, so I *think* they are safe. Suggest to go ahead with r39304, but next release be more clear with release tag/branch, and the following unfreeze. - Campbell On Fri, Aug 12, 2011 at 3:58 AM, Kent Meinm...@cs.umn.edu wrote: In reply to Sergey I. Sharybin (g.ula...@gmail.com): Didn't know OSX still have got issues with non-trunk verison. I've just commited patch from Jens to solve this problems. We prefer to keep revisions synced for all platforms, so please use Trunk: r39307 Extensions: r2241 Updated tarball of the source and md5sum are in incoming on ftp.blender.org Kent ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers ___ Bf-committers mailing list Bf-committers@blender.org
Re: [Bf-committers] Blender 2.59 release AHOY!
Enable Use Sketching session (Grease Pencil) in the Toolbar, and draw something into the viewport. Undo. Crash. Confirmed by Sergey and myself on Linux and Windows. Showstopper!? Am 10.08.2011 22:18, schrieb Campbell Barton: yikes! thats bad!, yes _please_ report bugs like this right away, especially near release and in the tracker. but good you found this too, fixed in svn. Platform maintainers, these rev's are now needed for building. Trunk: r39272 Extensions: r2241 -- Thomas Dinges Blender Developer, Artist and Musician www.dingto.org ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] Blender 2.59 release AHOY!
As a side note, please keep trunk frozen until release is out! No unnecessary commits! Am 11.08.2011 14:37, schrieb Thomas Dinges: Enable Use Sketching session (Grease Pencil) in the Toolbar, and draw something into the viewport. Undo. Crash. Confirmed by Sergey and myself on Linux and Windows. Showstopper!? Am 10.08.2011 22:18, schrieb Campbell Barton: yikes! thats bad!, yes _please_ report bugs like this right away, especially near release and in the tracker. but good you found this too, fixed in svn. Platform maintainers, these rev's are now needed for building. Trunk: r39272 Extensions: r2241 -- Thomas Dinges Blender Developer, Artist and Musician www.dingto.org ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] Blender 2.59 release AHOY!
I've made grease pencil block all other operations when using it in sketching mode. It's the only way for now because it's not only undo which can confuse grease pencil, also toggling edit mode, transformation and so confuses this operator. So we should update release builds to Trunk: r39304 Extensions: r2241 Thomas Dinges wrote: As a side note, please keep trunk frozen until release is out! No unnecessary commits! Am 11.08.2011 14:37, schrieb Thomas Dinges: Enable Use Sketching session (Grease Pencil) in the Toolbar, and draw something into the viewport. Undo. Crash. Confirmed by Sergey and myself on Linux and Windows. Showstopper!? Am 10.08.2011 22:18, schrieb Campbell Barton: yikes! thats bad!, yes _please_ report bugs like this right away, especially near release and in the tracker. but good you found this too, fixed in svn. Platform maintainers, these rev's are now needed for building. Trunk: r39272 Extensions: r2241 -- With best regards, Sergey I. Sharybin ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] Blender 2.59 release AHOY!
The very recent linux release archives are there: http://download.blender.org/ftp/incoming/linux-release-39304/ Sergey I. Sharybin wrote: I've made grease pencil block all other operations when using it in sketching mode. It's the only way for now because it's not only undo which can confuse grease pencil, also toggling edit mode, transformation and so confuses this operator. So we should update release builds to Trunk: r39304 Extensions: r2241 Thomas Dinges wrote: As a side note, please keep trunk frozen until release is out! No unnecessary commits! Am 11.08.2011 14:37, schrieb Thomas Dinges: Enable Use Sketching session (Grease Pencil) in the Toolbar, and draw something into the viewport. Undo. Crash. Confirmed by Sergey and myself on Linux and Windows. Showstopper!? Am 10.08.2011 22:18, schrieb Campbell Barton: yikes! thats bad!, yes _please_ report bugs like this right away, especially near release and in the tracker. but good you found this too, fixed in svn. Platform maintainers, these rev's are now needed for building. Trunk: r39272 Extensions: r2241 -- With best regards, Sergey I. Sharybin -- With best regards, Sergey I. Sharybin ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] Blender 2.59 release AHOY!
Pardon, guys, Didn't know OSX still have got issues with non-trunk verison. I've just commited patch from Jens to solve this problems. We prefer to keep revisions synced for all platforms, so please use Trunk: r39307 Extensions: r2241 as reference for new release archives. I hope it's last update before real release! Anyway, thanks all! -- With best regards, Sergey I. Sharybin ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] Blender 2.59 release AHOY!
FreeBSD builds are up... again again :) On Thu, Aug 11, 2011 at 11:01 AM, Sergey I. Sharybin g.ula...@gmail.com wrote: Pardon, guys, Didn't know OSX still have got issues with non-trunk verison. I've just commited patch from Jens to solve this problems. We prefer to keep revisions synced for all platforms, so please use Trunk: r39307 Extensions: r2241 as reference for new release archives. I hope it's last update before real release! Anyway, thanks all! -- With best regards, Sergey I. Sharybin ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] Blender 2.59 release AHOY!
In reply to Sergey I. Sharybin (g.ula...@gmail.com): Didn't know OSX still have got issues with non-trunk verison. I've just commited patch from Jens to solve this problems. We prefer to keep revisions synced for all platforms, so please use Trunk: r39307 Extensions: r2241 Updated tarball of the source and md5sum are in incoming on ftp.blender.org Kent ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] Blender 2.59 release AHOY!
Hi, woke up to find a re-release from a revision that contains changes I made that were *not* intended to be in a stable release - switching operators and menus to hash lookups. We should have branched at r39259 stable and applied patches there before re-releasing. There is also the issue with grease pencil session - where the operator points to data that can be freed on 'Global Undo' (as opposed to the crasher with the modal operators own *fake* undo, fixed 39237 and double undos fixed 39235). Sergey's fix means you can't move the viewport while grease pencil session is enable so the option is now not at all working as it was meant. *Sigh* Since there were 3 fairly bad bugs in this tool (2 crashers), my impression is that option isn't used all that much. A correct fix isn't some small edit, the operator must store data differently, this should have been picked up during normal development, IMHO we should not attempt to sort this out as a last-minute, show-stopper fix. There is the remaining issue: Do we use current bsd/linux/mac builds from r39304 (and wait on win build before announcing), Or re-branch from 39259 and apply a few fixes there and rebuild on all platforms. By not re-branching we break our own guidelines - to unfreeze quick but use a branch for fixes and it feels very sloppy to me. On the other hand my change of moving operators/menu's into a hash isn't that big a deal and works with scripts reloading, freeing, re-registering operators etc - I would expect any bugs here would be obvious and break blender immediately, so I *think* they are safe. Suggest to go ahead with r39304, but next release be more clear with release tag/branch, and the following unfreeze. - Campbell On Fri, Aug 12, 2011 at 3:58 AM, Kent Mein m...@cs.umn.edu wrote: In reply to Sergey I. Sharybin (g.ula...@gmail.com): Didn't know OSX still have got issues with non-trunk verison. I've just commited patch from Jens to solve this problems. We prefer to keep revisions synced for all platforms, so please use Trunk: r39307 Extensions: r2241 Updated tarball of the source and md5sum are in incoming on ftp.blender.org Kent ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers -- - Campbell ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] Blender 2.59 release AHOY!
I only have a 39307 uploaded.. don't think I put 39304 up... is 39307 ok??? On Thu, Aug 11, 2011 at 7:10 PM, Campbell Barton ideasma...@gmail.com wrote: Hi, woke up to find a re-release from a revision that contains changes I made that were *not* intended to be in a stable release - switching operators and menus to hash lookups. We should have branched at r39259 stable and applied patches there before re-releasing. There is also the issue with grease pencil session - where the operator points to data that can be freed on 'Global Undo' (as opposed to the crasher with the modal operators own *fake* undo, fixed 39237 and double undos fixed 39235). Sergey's fix means you can't move the viewport while grease pencil session is enable so the option is now not at all working as it was meant. *Sigh* Since there were 3 fairly bad bugs in this tool (2 crashers), my impression is that option isn't used all that much. A correct fix isn't some small edit, the operator must store data differently, this should have been picked up during normal development, IMHO we should not attempt to sort this out as a last-minute, show-stopper fix. There is the remaining issue: Do we use current bsd/linux/mac builds from r39304 (and wait on win build before announcing), Or re-branch from 39259 and apply a few fixes there and rebuild on all platforms. By not re-branching we break our own guidelines - to unfreeze quick but use a branch for fixes and it feels very sloppy to me. On the other hand my change of moving operators/menu's into a hash isn't that big a deal and works with scripts reloading, freeing, re-registering operators etc - I would expect any bugs here would be obvious and break blender immediately, so I *think* they are safe. Suggest to go ahead with r39304, but next release be more clear with release tag/branch, and the following unfreeze. - Campbell On Fri, Aug 12, 2011 at 3:58 AM, Kent Mein m...@cs.umn.edu wrote: In reply to Sergey I. Sharybin (g.ula...@gmail.com): Didn't know OSX still have got issues with non-trunk verison. I've just commited patch from Jens to solve this problems. We prefer to keep revisions synced for all platforms, so please use Trunk: r39307 Extensions: r2241 Updated tarball of the source and md5sum are in incoming on ftp.blender.org Kent ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers -- - Campbell ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] Blender 2.59 release AHOY!
if you need 39304 for FreeBSD it'll have to wait till tomorrow... :( On Thu, Aug 11, 2011 at 7:29 PM, pete larabell xgl.asyl...@gmail.com wrote: I only have a 39307 uploaded.. don't think I put 39304 up... is 39307 ok??? On Thu, Aug 11, 2011 at 7:10 PM, Campbell Barton ideasma...@gmail.com wrote: Hi, woke up to find a re-release from a revision that contains changes I made that were *not* intended to be in a stable release - switching operators and menus to hash lookups. We should have branched at r39259 stable and applied patches there before re-releasing. There is also the issue with grease pencil session - where the operator points to data that can be freed on 'Global Undo' (as opposed to the crasher with the modal operators own *fake* undo, fixed 39237 and double undos fixed 39235). Sergey's fix means you can't move the viewport while grease pencil session is enable so the option is now not at all working as it was meant. *Sigh* Since there were 3 fairly bad bugs in this tool (2 crashers), my impression is that option isn't used all that much. A correct fix isn't some small edit, the operator must store data differently, this should have been picked up during normal development, IMHO we should not attempt to sort this out as a last-minute, show-stopper fix. There is the remaining issue: Do we use current bsd/linux/mac builds from r39304 (and wait on win build before announcing), Or re-branch from 39259 and apply a few fixes there and rebuild on all platforms. By not re-branching we break our own guidelines - to unfreeze quick but use a branch for fixes and it feels very sloppy to me. On the other hand my change of moving operators/menu's into a hash isn't that big a deal and works with scripts reloading, freeing, re-registering operators etc - I would expect any bugs here would be obvious and break blender immediately, so I *think* they are safe. Suggest to go ahead with r39304, but next release be more clear with release tag/branch, and the following unfreeze. - Campbell On Fri, Aug 12, 2011 at 3:58 AM, Kent Mein m...@cs.umn.edu wrote: In reply to Sergey I. Sharybin (g.ula...@gmail.com): Didn't know OSX still have got issues with non-trunk verison. I've just commited patch from Jens to solve this problems. We prefer to keep revisions synced for all platforms, so please use Trunk: r39307 Extensions: r2241 Updated tarball of the source and md5sum are in incoming on ftp.blender.org Kent ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers -- - Campbell ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] Blender 2.59 release AHOY!
well, 12.5 hrs from now... is tomorrow for me. i can have it uploaded in 13hrs from now. On Thu, Aug 11, 2011 at 7:29 PM, pete larabell xgl.asyl...@gmail.com wrote: if you need 39304 for FreeBSD it'll have to wait till tomorrow... :( On Thu, Aug 11, 2011 at 7:29 PM, pete larabell xgl.asyl...@gmail.com wrote: I only have a 39307 uploaded.. don't think I put 39304 up... is 39307 ok??? On Thu, Aug 11, 2011 at 7:10 PM, Campbell Barton ideasma...@gmail.com wrote: Hi, woke up to find a re-release from a revision that contains changes I made that were *not* intended to be in a stable release - switching operators and menus to hash lookups. We should have branched at r39259 stable and applied patches there before re-releasing. There is also the issue with grease pencil session - where the operator points to data that can be freed on 'Global Undo' (as opposed to the crasher with the modal operators own *fake* undo, fixed 39237 and double undos fixed 39235). Sergey's fix means you can't move the viewport while grease pencil session is enable so the option is now not at all working as it was meant. *Sigh* Since there were 3 fairly bad bugs in this tool (2 crashers), my impression is that option isn't used all that much. A correct fix isn't some small edit, the operator must store data differently, this should have been picked up during normal development, IMHO we should not attempt to sort this out as a last-minute, show-stopper fix. There is the remaining issue: Do we use current bsd/linux/mac builds from r39304 (and wait on win build before announcing), Or re-branch from 39259 and apply a few fixes there and rebuild on all platforms. By not re-branching we break our own guidelines - to unfreeze quick but use a branch for fixes and it feels very sloppy to me. On the other hand my change of moving operators/menu's into a hash isn't that big a deal and works with scripts reloading, freeing, re-registering operators etc - I would expect any bugs here would be obvious and break blender immediately, so I *think* they are safe. Suggest to go ahead with r39304, but next release be more clear with release tag/branch, and the following unfreeze. - Campbell On Fri, Aug 12, 2011 at 3:58 AM, Kent Mein m...@cs.umn.edu wrote: In reply to Sergey I. Sharybin (g.ula...@gmail.com): Didn't know OSX still have got issues with non-trunk verison. I've just commited patch from Jens to solve this problems. We prefer to keep revisions synced for all platforms, so please use Trunk: r39307 Extensions: r2241 Updated tarball of the source and md5sum are in incoming on ftp.blender.org Kent ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers -- - Campbell ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] Blender 2.59 release AHOY!
While writing my last reply I made an error checking on the re-release revision I saw Sergey's mail refer to 39304. In my last mail substitute 39304 with 39307. Lets use tag's next time! On Fri, Aug 12, 2011 at 10:30 AM, pete larabell xgl.asyl...@gmail.com wrote: well, 12.5 hrs from now... is tomorrow for me. i can have it uploaded in 13hrs from now. On Thu, Aug 11, 2011 at 7:29 PM, pete larabell xgl.asyl...@gmail.com wrote: if you need 39304 for FreeBSD it'll have to wait till tomorrow... :( On Thu, Aug 11, 2011 at 7:29 PM, pete larabell xgl.asyl...@gmail.com wrote: I only have a 39307 uploaded.. don't think I put 39304 up... is 39307 ok??? On Thu, Aug 11, 2011 at 7:10 PM, Campbell Barton ideasma...@gmail.com wrote: Hi, woke up to find a re-release from a revision that contains changes I made that were *not* intended to be in a stable release - switching operators and menus to hash lookups. We should have branched at r39259 stable and applied patches there before re-releasing. There is also the issue with grease pencil session - where the operator points to data that can be freed on 'Global Undo' (as opposed to the crasher with the modal operators own *fake* undo, fixed 39237 and double undos fixed 39235). Sergey's fix means you can't move the viewport while grease pencil session is enable so the option is now not at all working as it was meant. *Sigh* Since there were 3 fairly bad bugs in this tool (2 crashers), my impression is that option isn't used all that much. A correct fix isn't some small edit, the operator must store data differently, this should have been picked up during normal development, IMHO we should not attempt to sort this out as a last-minute, show-stopper fix. There is the remaining issue: Do we use current bsd/linux/mac builds from r39304 (and wait on win build before announcing), Or re-branch from 39259 and apply a few fixes there and rebuild on all platforms. By not re-branching we break our own guidelines - to unfreeze quick but use a branch for fixes and it feels very sloppy to me. On the other hand my change of moving operators/menu's into a hash isn't that big a deal and works with scripts reloading, freeing, re-registering operators etc - I would expect any bugs here would be obvious and break blender immediately, so I *think* they are safe. Suggest to go ahead with r39304, but next release be more clear with release tag/branch, and the following unfreeze. - Campbell On Fri, Aug 12, 2011 at 3:58 AM, Kent Mein m...@cs.umn.edu wrote: In reply to Sergey I. Sharybin (g.ula...@gmail.com): Didn't know OSX still have got issues with non-trunk verison. I've just commited patch from Jens to solve this problems. We prefer to keep revisions synced for all platforms, so please use Trunk: r39307 Extensions: r2241 Updated tarball of the source and md5sum are in incoming on ftp.blender.org Kent ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers -- - Campbell ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers -- - Campbell ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] Blender 2.59 release AHOY!
Hi, I've got fix for grease pencil in mu branch [1], but it's really that kind of changes which shouldn't be applied in last minute (at least there are several possible issues i wanted to check), so let's limit GP a bit for 2.59. About reloading scripts and so. I've been working on UI in my branch after merging ghash changes there and haven't found any bad sides of this change. About more clear release next time. I'm not sure why this release is so crazy. Is it our lag, lag of coordination or so.. [1] http://projects.blender.org/scm/viewvc.php?view=revroot=bf-blenderrevision=39313 P.S. linux 32/64 bit would be available soon. Campbell Barton wrote: Hi, woke up to find a re-release from a revision that contains changes I made that were *not* intended to be in a stable release - switching operators and menus to hash lookups. We should have branched at r39259 stable and applied patches there before re-releasing. There is also the issue with grease pencil session - where the operator points to data that can be freed on 'Global Undo' (as opposed to the crasher with the modal operators own *fake* undo, fixed 39237 and double undos fixed 39235). Sergey's fix means you can't move the viewport while grease pencil session is enable so the option is now not at all working as it was meant. *Sigh* Since there were 3 fairly bad bugs in this tool (2 crashers), my impression is that option isn't used all that much. A correct fix isn't some small edit, the operator must store data differently, this should have been picked up during normal development, IMHO we should not attempt to sort this out as a last-minute, show-stopper fix. There is the remaining issue: Do we use current bsd/linux/mac builds from r39304 (and wait on win build before announcing), Or re-branch from 39259 and apply a few fixes there and rebuild on all platforms. By not re-branching we break our own guidelines - to unfreeze quick but use a branch for fixes and it feels very sloppy to me. On the other hand my change of moving operators/menu's into a hash isn't that big a deal and works with scripts reloading, freeing, re-registering operators etc - I would expect any bugs here would be obvious and break blender immediately, so I *think* they are safe. Suggest to go ahead with r39304, but next release be more clear with release tag/branch, and the following unfreeze. - Campbell On Fri, Aug 12, 2011 at 3:58 AM, Kent Meinm...@cs.umn.edu wrote: In reply to Sergey I. Sharybin (g.ula...@gmail.com): Didn't know OSX still have got issues with non-trunk verison. I've just commited patch from Jens to solve this problems. We prefer to keep revisions synced for all platforms, so please use Trunk: r39307 Extensions: r2241 Updated tarball of the source and md5sum are in incoming on ftp.blender.org Kent ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers -- With best regards, Sergey I. Sharybin ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] Blender 2.59 release AHOY!
Wait! Haven't noticed that regression. New builds are soon.. Sergey I. Sharybin wrote: Hi, Linux 32/64 builds are there http://download.blender.org/ftp/incoming/ Campbell Barton wrote: Hi devs, I've been keeping an eye on the tracker for new reports since our 2.59RC release and am happy we don't have any real show stoppers. Thomas committed the splash, we have version bumped so think its time to build! Since there is some secret to tagging trunk, lib extensions that Nathan isn't around to impart, for now just build from revisions. Trunk: r39263 Extensions: r2241 I'll be available tomorrow to help with getting the uploads copied to the download dir and update changelog typo3 pages. Really happy with this release :), thanks to everyone for you're contributions! - Campbell ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers -- With best regards, Sergey I. Sharybin -- With best regards, Sergey I. Sharybin ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] Blender 2.59 release AHOY!
FreeBSD builds are up, again :) On Wed, Aug 10, 2011 at 3:26 PM, Sergey I. Sharybin g.ula...@gmail.com wrote: Wait! Haven't noticed that regression. New builds are soon.. Sergey I. Sharybin wrote: Hi, Linux 32/64 builds are there http://download.blender.org/ftp/incoming/ Campbell Barton wrote: Hi devs, I've been keeping an eye on the tracker for new reports since our 2.59RC release and am happy we don't have any real show stoppers. Thomas committed the splash, we have version bumped so think its time to build! Since there is some secret to tagging trunk, lib extensions that Nathan isn't around to impart, for now just build from revisions. Trunk: r39263 Extensions: r2241 I'll be available tomorrow to help with getting the uploads copied to the download dir and update changelog typo3 pages. Really happy with this release :), thanks to everyone for you're contributions! - Campbell ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers -- With best regards, Sergey I. Sharybin -- With best regards, Sergey I. Sharybin ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
Re: [Bf-committers] Blender 2.59 release AHOY!
Ok, new builds are there http://download.blender.org/ftp/incoming/linux-release-39272/ Please, delete http://download.blender.org/ftp/incoming/linux-new/ and 2.59 builds from root of incoming. Campbell Barton wrote: yikes! thats bad!, yes _please_ report bugs like this right away, especially near release and in the tracker. but good you found this too, fixed in svn. Platform maintainers, these rev's are now needed for building. Trunk: r39272 Extensions: r2241 removed freebsd build and source code for 2.59 from the download server. On Thu, Aug 11, 2011 at 4:39 AM, Alberto Torreskungfoo...@gmail.com wrote: In blender 2.59rc, shape keys don't have its value in the list anymore like previous versions (so you can't tweak them just by dragging them). Is it a bug? Is it fixed? Sorry for putting this here, I've just noticed today (I've written this in another thread and it was ignored, I guess I should have opened a bug report first). 2011/8/10 pete larabellxgl.asyl...@gmail.com: FreeBSD build are up. :) On Wed, Aug 10, 2011 at 11:22 AM, Campbell Bartonideasma...@gmail.com wrote: Hi devs, I've been keeping an eye on the tracker for new reports since our 2.59RC release and am happy we don't have any real show stoppers. Thomas committed the splash, we have version bumped so think its time to build! Since there is some secret to tagging trunk, lib extensions that Nathan isn't around to impart, for now just build from revisions. Trunk: r39263 Extensions: r2241 I'll be available tomorrow to help with getting the uploads copied to the download dir and update changelog typo3 pages. Really happy with this release :), thanks to everyone for you're contributions! - Campbell ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers -- With best regards, Sergey I. Sharybin ___ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
