 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Fri, 08 Nov 2013 20:43:08 +1100, Chris Cason wrote:
> Folks,
>
> After many years of beta-testing, POV-Ray 3.7 has been officially
> released. Please see http://www.povray.org/download/ for the final
> downloads (which currently are only for Windows).
>
> Source code is released under the AGPL3 and is available via our github
> repository: https://github.com/POV-Ray/povray/tree/3.7-stable
>
> Thanks to all the developers, documentation wranglers, beta-testers,
> bug reporters, scene authors, contributors and supporters who made this
> possible.
>
> regards,
>
> -- Chris Cason
> POV-Ray Team Co-ordinator
Congrats on the release, Chris & Team!
Jim
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Chris Cason <del### [at] deletethistoo povrayorg> wrote:
> Folks,
>
> After many years of beta-testing, POV-Ray 3.7 has been officially
> released. Please see http://www.povray.org/download/ for the final
> downloads (which currently are only for Windows).
>
> Source code is released under the AGPL3 and is available via our
> github repository: https://github.com/POV-Ray/povray/tree/3.7-stable
>
> Thanks to all the developers, documentation wranglers, beta-testers,
> bug reporters, scene authors, contributors and supporters who made
> this possible.
>
> regards,
>
> -- Chris Cason
> POV-Ray Team Co-ordinator
woohooo!
ready the bottles of champagne, gentleman!
thumbs up
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 08/11/13 09:43, Chris Cason wrote:
> Folks,
>
> After many years of beta-testing, POV-Ray 3.7 has been officially
> released. Please see http://www.povray.org/download/ for the final
> downloads (which currently are only for Windows).
>
> Source code is released under the AGPL3 and is available via our
> github repository: https://github.com/POV-Ray/povray/tree/3.7-stable
>
> Thanks to all the developers, documentation wranglers, beta-testers,
> bug reporters, scene authors, contributors and supporters who made
> this possible.
>
> regards,
>
> -- Chris Cason
> POV-Ray Team Co-ordinator
>
Yeehah!! have just downloaded and compiled it on a vanilla Suse 12.3.
Excellent work, gentlemen
John
--
Protect the Earth
It was not given to you by your parents
You hold it in trust for your children
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
in news:527cb3bf@news.povray.org Chris Cason wrote:
Chris, Team,
Thank you!
Due to circumstances I havn't been able to contribute or even follow
development, I envy your stamina in getting it done. Nice to see it on
github.
Ingo
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Congrats, and many thanks, guys... your toughness is awesome (special
thanks to Chris for his almost "lifelong" devotion to POV-Ray).
Well, I think this is worth a comeback from semi-retirement... and a
bunch of celebration renders!
--
Jaime
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Fri, 08 Nov 2013 20:19:31 +0200, nemesis <nam### [at] gmailcom> wrote:
> woohooo!
>
You took the words right out of my mouth!
--
-Nekar Xenos-
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Sorry, I think that I have to play a little bit the devils advocat here. Yes, we
number now. For example the +c issue is not solved as stated. Thomas and I has
found problemns with it
(http://news.povray.org/povray.binaries.images/thread/%3C5239bc36%40news.povray.org%3E/)
never addressed by the three Christophs developing POV, but only ignored. For me
this is only RC 8, but not an final solution,
Best regards,
Michael
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 08/11/2013 10:09 AM, Stephen wrote:
>
> Thank you and everyone concerned with this. :-D
Oops! I got an exception and a crash when running Tim Nikias'a LSSM file
lssm_wlk.pov, from http://www.nolights.de/downloads.html#lssm
If you did not get the dump, I still have the files.
Sorry. :-(
BTW I changed nothing in the file, not even using a #version statement.
And I did run flow.pov okay.
--
Regards
Stephen
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 09.11.2013 19:29, schrieb MichaelJF:
> Sorry, I think that I have to play a little bit the devils advocat here. Yes, we
> number now. For example the +c issue is not solved as stated. Thomas and I has
> found problemns with it
>
(http://news.povray.org/povray.binaries.images/thread/%3C5239bc36%40news.povray.org%3E/)
> never addressed by the three Christophs developing POV, but only ignored. For me
> this is only RC 8, but not an final solution,
Reports of the +C bug appeared only a short time ago, while we had
already begun the last preparations for the actual release (which had
virtually nothing to do with changes to the code; stuff like making the
switch to the new license, setting up the Git repository, and other such
stuff).
It seems that in this last phase, povray.beta-test hasn't been read by
any of the developers on a regular basis, so we weren't even aware of
these +C artifacts and their severity; from what I see now they would
indeed have warranted halting the release process.
It should be mentioned that while povray.beta-test is a good place to
discuss /suspected/ issues, the most reliable way of communicating
/identified/ issues is via http://bugs.povray.org. New entries there
trigger an email to the members of the dev team.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 10-11-2013 14:31, clipka wrote:
> Reports of the +C bug appeared only a short time ago, while we had
> already begun the last preparations for the actual release (which had
> virtually nothing to do with changes to the code; stuff like making the
> switch to the new license, setting up the Git repository, and other such
> stuff).
>
> It seems that in this last phase, povray.beta-test hasn't been read by
> any of the developers on a regular basis, so we weren't even aware of
> these +C artifacts and their severity; from what I see now they would
> indeed have warranted halting the release process.
>
> It should be mentioned that while povray.beta-test is a good place to
> discuss /suspected/ issues, the most reliable way of communicating
> /identified/ issues is via http://bugs.povray.org. New entries there
> trigger an email to the members of the dev team.
>
Yes, I forgot to file a bug report indeed, so I take the blunt impact of
the responsibility :-)
I shall try to reproduce the problem. However, I have not noticed it in
any of my later renders, since my mention of it. So, it may be fairly
difficult to do, especially to make it reproducible. :-(
Thomas
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
