[hugin-ptx] Re: Hugin 2010.2.0 release process

2010-07-22 Thread Bob Campbell
Hey, just to throw a monkey-wrench into the works, I've just completed some (pretty minor, actually) updates to the libpano13-2.9.17 code (I got the svn trunk) so that it compiles* for Solaris on Sparc. It even passes the 'make check', so all the tools build, etc. Don't have an x86 Solaris box,

[hugin-ptx] Re: Hugin 2010.2.0 release process

2010-07-22 Thread Bob Campbell
Hey, just to throw a monkey-wrench into the works, I've just completed some (pretty minor, actually) updates to the libpano13-2.9.17 code (I got the svn trunk) so that it compiles* for Solaris on Sparc. It even passes the 'make check', so all the tools build, etc. Don't have an x86 Solaris box,

Re: [hugin-ptx] Re: Hugin 2010.2.0 release process

2010-07-22 Thread Bruno Postle
On Thu 22-Jul-2010 at 13:43 -0700, Bob Campbell wrote: Hey, just to throw a monkey-wrench into the works, I've just completed some (pretty minor, actually) updates to the libpano13-2.9.17 code (I got the svn trunk) so that it compiles* for Solaris on Sparc. It even passes the 'make check', so

Re: [hugin-ptx] Re: Hugin 2010.2.0 release process

2010-07-21 Thread Bruno Postle
Continuing my list of things to do for this release, we are now a bit further along: A libpano13-2.9.17 release Still needed. Thomas noted a bug calculating angle of view for panoramas with mosaics, I'm not sure if this is libpano13 or Hugin bug? Do something with translations, even if

Re: [hugin-ptx] Re: Hugin 2010.2.0 release process

2010-06-29 Thread Eric O'Brien
Gee, with Mercurial, this sort of stuff is supposed to... Just Work! :) Umm... did it? eo On Jun 28, 2010, at 2:07 PM, Bruno Postle wrote: On Sat 26-Jun-2010 at 17:15 +0100, Bruno Postle wrote: So we need to create a Hugin branch, then: Increment the version numbers in both the 'stable'

Re: [hugin-ptx] Re: Hugin 2010.2.0 release process

2010-06-29 Thread Kornel Benko
Am Dienstag, 29. Juni 2010 schrieb Tduell: Hullo Kornel, On Jun 28, 4:29 pm, Kornel Benko kornel.be...@berlin.de wrote: Am Montag, 28. Juni 2010 schrieb Tduell: abort: There is no Mercurial repository here (.hg not found)! -- New ChangeLog generated Maybe the solution is

Re: [hugin-ptx] Re: Hugin 2010.2.0 release process

2010-06-29 Thread Yuval Levy
On June 29, 2010 03:41:04 am Kornel Benko wrote: Am Dienstag, 29. Juni 2010 schrieb Tduell: I don't understand why the test for .hg didn't fail gracefully for Yuv. Because there _is_ a .hg in ${PROJECT_SOURCE_DIR}. But the execute_process() is called from the build-directory. Therefore

Re: [hugin-ptx] Re: Hugin 2010.2.0 release process

2010-06-29 Thread Yuval Levy
On June 29, 2010 02:14:46 am Eric O'Brien wrote: Gee, with Mercurial, this sort of stuff is supposed to... Just Work! :) it Just Works either way, so it does not really matter. Yuv -- You received this message because you are subscribed to the Google Groups hugin and other free panoramic

Re: [hugin-ptx] Re: Hugin 2010.2.0 release process

2010-06-29 Thread Bruno Postle
On Tue 29-Jun-2010 at 22:41 +0200, Kornel Benko wrote: did you commit the patch? if not, please do. I did not. If I understood correctly, Bruno was not satisfied with the outcome. But OK, with the patch it works at least. I didn't think I needed to comment, if you think something like

Re: [hugin-ptx] Re: Hugin 2010.2.0 release process

2010-06-29 Thread Yuval Levy
On June 29, 2010 04:59:48 pm Bruno Postle wrote: On Tue 29-Jun-2010 at 22:41 +0200, Kornel Benko wrote: did you commit the patch? if not, please do. I did not. If I understood correctly, Bruno was not satisfied with the outcome. But OK, with the patch it works at least. I didn't

Re: [hugin-ptx] Re: Hugin 2010.2.0 release process

2010-06-29 Thread Bruno Postle
On Tue 29-Jun-2010 at 17:44 -0400, Yuval Levy wrote: IMHO it is good to keep the ChangeLog generation manual. It makes the person who does the release stop and think, amongst others of updating authors.txt Yes the ChangeLog has only ever been generated if you build with cmake

Re: [hugin-ptx] Re: Hugin 2010.2.0 release process

2010-06-29 Thread Kornel Benko
Am Dienstag, 29. Juni 2010 schrieb Bruno Postle: On Tue 29-Jun-2010 at 22:41 +0200, Kornel Benko wrote: did you commit the patch? if not, please do. I did not. If I understood correctly, Bruno was not satisfied with the outcome. But OK, with the patch it works at least. I didn't

Re: [hugin-ptx] Re: Hugin 2010.2.0 release process

2010-06-28 Thread Kornel Benko
Am Montag, 28. Juni 2010 schrieb Tduell: abort: There is no Mercurial repository here (.hg not found)! -- New ChangeLog generated Maybe the solution is to just remove the test for .hg. Anyone see any problems with that? If you call hg to get some info, there has to be a directory

Re: [hugin-ptx] Re: Hugin 2010.2.0 release process

2010-06-28 Thread Oskar Sander
I took a stab at this one and just updated the wiki for *Layout tab* I just realized the *Move/drag* description on the same page does not mention what *normal/mosaic* mode means. So I also added something short here. Btw these are new undefined concepts that may require proper definitions...

Re: [hugin-ptx] Re: Hugin 2010.2.0 release process

2010-06-28 Thread Bruno Postle
On Sat 26-Jun-2010 at 17:15 +0100, Bruno Postle wrote: So we need to create a Hugin branch, then: Increment the version numbers in both the 'stable' branch and the 'trunk'. Ok, I *think* I've done this, there should now be a 2010.2 branch in addition to the default 'tip' which now builds

[hugin-ptx] Re: Hugin 2010.2.0 release process

2010-06-28 Thread Tduell
Hullo Kornel, On Jun 28, 4:29 pm, Kornel Benko kornel.be...@berlin.de wrote: Am Montag, 28. Juni 2010 schrieb Tduell: abort: There is no Mercurial repository here (.hg not found)! -- New ChangeLog generated Maybe the solution is to just remove the test for .hg. Anyone see any

[hugin-ptx] Re: Hugin 2010.2.0 release process

2010-06-28 Thread Tduell
Hullo Bruno, On Jun 29, 7:07 am, Bruno Postle br...@postle.net wrote: On Sat 26-Jun-2010 at 17:15 +0100, Bruno Postle wrote: Increment the version numbers in both the 'stable' branch and the 'trunk'. Ok, I *think* I've done this, there should now be a 2010.2 branch in addition to the

[hugin-ptx] Re: Hugin 2010.2.0 release process

2010-06-27 Thread Yuv
Hi Terry, On Jun 26, 8:14 pm, Tduell tdu...@iinet.net.au wrote: You still have to run `cmake -DUPDATE_CHANGELOG=1` to intentionally update the ChangeLog. I've tried it. because I build out of tree, it did not work properly. but it did turn the existing ChangeLog into an empty file: cd

Re: [hugin-ptx] Re: Hugin 2010.2.0 release process

2010-06-27 Thread Kornel Benko
Am Sonntag 27 Juni 2010 schrieb Yuv: Hi Terry, On Jun 26, 8:14 pm, Tduell tdu...@iinet.net.au wrote: You still have to run `cmake -DUPDATE_CHANGELOG=1` to intentionally update the ChangeLog. I've tried it. because I build out of tree, it did not work properly. but it did turn the

Re: [hugin-ptx] Re: Hugin 2010.2.0 release process

2010-06-27 Thread Kornel Benko
Am Sonntag 27 Juni 2010 schrieb Kornel Benko: Am Sonntag 27 Juni 2010 schrieb Yuv: Hi Terry, On Jun 26, 8:14 pm, Tduell tdu...@iinet.net.au wrote: You still have to run `cmake -DUPDATE_CHANGELOG=1` to intentionally update the ChangeLog. I've tried it. because I build out of

Re: [hugin-ptx] Re: Hugin 2010.2.0 release process

2010-06-27 Thread Bruno Postle
On Sat 26-Jun-2010 at 21:41 -0400, Robert Krawitz wrote: The exact way varies depending upon the exact log options, but it's easy to get a list of everyone with something like this: $ hg log |grep '^user:' | sed -e 's/^user:\s*//' -e 's/\s*.*$//' | sort | uniq This gives a list of everyone

[hugin-ptx] Re: Hugin 2010.2.0 release process

2010-06-27 Thread Tduell
Hullo Yuv, On Jun 27, 5:15 pm, Yuv goo...@levy.ch wrote: Hi Terry, On Jun 26, 8:14 pm, Tduell tdu...@iinet.net.au wrote: You still have to run `cmake -DUPDATE_CHANGELOG=1` to intentionally update the ChangeLog. I've tried it. because I build out of tree, it did not work properly. but

[hugin-ptx] Re: Hugin 2010.2.0 release process

2010-06-26 Thread Yuv
On Jun 24, 5:35 pm, Bruno Postle br...@postle.net wrote: Can we try and get an idea of tasks that need to be done? * The documentation [0] needs to be updated for Mercurial. I have updated the Ubuntu docs [1] four weeks ago to about 90%. I don't know about the docs for other O/S. * Wish: a

Re: [hugin-ptx] Re: Hugin 2010.2.0 release process

2010-06-26 Thread Kornel Benko
Am Samstag 26 Juni 2010 schrieb Yuv: [1] http://wiki.panotools.org/Hugin_Compiling_Ubuntu Hi Yuv, in Building Environment: missing cmake Apart from that, I could not find another mistake. Regards Kornel -- Kornel Benko kornel.be...@berlin.de signature.asc

Re: [hugin-ptx] Re: Hugin 2010.2.0 release process

2010-06-26 Thread Harry van der Wolf
2010/6/26 Yuv goo...@levy.ch On Jun 24, 5:35 pm, Bruno Postle br...@postle.net wrote: Can we try and get an idea of tasks that need to be done? * The documentation [0] needs to be updated for Mercurial. I have updated the Ubuntu docs [1] four weeks ago to about 90%. I don't know about

[hugin-ptx] Re: Hugin 2010.2.0 release process

2010-06-26 Thread Yuv
On Jun 26, 12:15 pm, Bruno Postle br...@postle.net wrote: * The documentation [0] needs to be updated for Mercurial.  I have updated the Ubuntu docs [1] four weeks ago to about 90%.  I don't know about the docs for other O/S. Actually this is not a blocker for a stable release since the end

[hugin-ptx] Re: Hugin 2010.2.0 release process

2010-06-26 Thread Tduell
Hullo Yuv, Hullo Yuv, On Jun 27, 4:49 am, Yuv goo...@levy.ch wrote: On Jun 26, 12:15 pm, Bruno Postle br...@postle.net wrote: Terry Duell has prompted this effort and has offered to do some of the legwork. Thank you, Terry! I'm not sure if I can do all that is needed, but I certainly

Re: [hugin-ptx] Re: Hugin 2010.2.0 release process

2010-06-26 Thread Robert Krawitz
Date: Sat, 26 Jun 2010 16:33:11 -0700 (PDT) From: Yuv goo...@levy.ch Hi Terry, On Jun 26, 7:13 pm, Tduell tdu...@iinet.net.au wrote: I have tested a change to the CMakeLists.txt which runs hg log -- follow --style=changelog and writes to the file ChangeLog, pretty much as

[hugin-ptx] Re: Hugin 2010.2.0 release process

2010-06-26 Thread Tduell
Hullo Yuv, On Jun 27, 9:33 am, Yuv goo...@levy.ch wrote: Yes, the hg log command is the right way to generate the ChangeLog.  I am not sure it is a good idea to automate / integrate it in the cmake build though.  One of the things that become apparent when looking at the ChangeLog between

[hugin-ptx] Re: Hugin 2010.2.0 release process

2010-06-26 Thread Tduell
Hullo Robert, On Jun 27, 9:53 am, Robert Krawitz r...@alum.mit.edu wrote:    Date: Sat, 26 Jun 2010 16:33:11 -0700 (PDT)    From: Yuv goo...@levy.ch    Yes, the hg log command is the right way to generate the ChangeLog.  I    am not sure it is a good idea to automate / integrate it in the

Re: [hugin-ptx] Re: Hugin 2010.2.0 release process

2010-06-26 Thread Robert Krawitz
Date: Sat, 26 Jun 2010 17:19:00 -0700 (PDT) From: Tduell tdu...@iinet.net.au Hullo Robert, On Jun 27, 9:53 am, Robert Krawitz r...@alum.mit.edu wrote:    Date: Sat, 26 Jun 2010 16:33:11 -0700 (PDT)    From: Yuv goo...@levy.ch    Yes, the hg log command is the right

[hugin-ptx] Re: Hugin 2010.2.0 release process

2010-06-26 Thread Tduell
Hullo Robert On Jun 27, 11:41 am, Robert Krawitz r...@alum.mit.edu wrote:    Date: Sat, 26 Jun 2010 17:19:00 -0700 (PDT)    From: Tduell tdu...@iinet.net.au     You could scan it for author names and compare them to the AUTHORS     file, and error out if there are any committers not listed

[hugin-ptx] Re: Hugin 2010.2.0 release process

2010-06-26 Thread Tduell
Hullo Robert, On Jun 27, 11:41 am, Robert Krawitz r...@alum.mit.edu wrote: [snip] So what we'll do is create a temporary file with a list of all authors, and use fgrep -v to see if there's anyone in the log list that isn't in the authors: [snip] I have tried your shell script but it seems

[hugin-ptx] Re: Hugin 2010.2.0 release process

2010-06-25 Thread T. Modes
Hi Bruno, On 24 Jun., 23:35, Bruno Postle br...@postle.net wrote: Hi all, the current HG 'trunk' is overdue for a release.  To do this we need to create a '2010.2.0' branch and work on clearing up the remaining bugs and various loose ends. Any objections?  Can we try and get an idea of tasks