beta 29 has expired and it's the 23rd.
what's going on?

not really happy.

Post a reply to this message

"mulciber" <nomail@nomail> wrote in message 
news:web.4928e62c28608148efb2f8d40@news.povray.org...
> beta 29 has expired and it's the 23rd.
> what's going on?

I imagine it's life .... most folks working on this project have day jobs, 
maybe even families, and of course the holidays are almost upon us .... etc 
..... etc

Jim

Post a reply to this message

"Jim Holsenback" <jho### [at] hotmailcom> wrote:
> "mulciber" <nomail@nomail> wrote in message
> news:web.4928e62c28608148efb2f8d40@news.povray.org...
> > beta 29 has expired and it's the 23rd.
> > what's going on?
>
> I imagine it's life .... most folks working on this project have day jobs,
> maybe even families, and of course the holidays are almost upon us .... etc
> ..... etc
>
> Jim

Alternatively, look here:

http://news.povray.org/476af506$1@news.povray.org

for what to do about this.  (In other words, keep using it, just suppress the
expiration stuff.)

Post a reply to this message

"Jim Holsenback" <jho### [at] hotmailcom> wrote:
> "mulciber" <nomail@nomail> wrote in message
> news:web.4928e62c28608148efb2f8d40@news.povray.org...
> > beta 29 has expired and it's the 23rd.
> > what's going on?
>
> I imagine it's life .... most folks working on this project have day jobs,
> maybe even families, and of course the holidays are almost upon us .... etc
> ..... etc

Are there any folks besides Chris?

Post a reply to this message

"nemesis" <nam### [at] gmailcom> wrote in message 
news:web.49297b934d710484548cb3a50@news.povray.org...
> "Jim Holsenback" <jho### [at] hotmailcom> wrote:
>> "mulciber" <nomail@nomail> wrote in message
>> news:web.4928e62c28608148efb2f8d40@news.povray.org...
>> > beta 29 has expired and it's the 23rd.
>> > what's going on?
>>
>> I imagine it's life .... most folks working on this project have day 
>> jobs,
>> maybe even families, and of course the holidays are almost upon us .... 
>> etc
>> ..... etc
>
> Are there any folks besides Chris?

check the messages pane each time you start the application ;-)

Post a reply to this message

On Sun, 23 Nov 2008 00:12:12 -0500, mulciber wrote:

> beta 29 has expired and it's the 23rd. what's going on?

POVray is a project developed by people in their spare time, by and 
large.  Life happens.

> not really happy.

Use the released version, then.  It's not like it's a secret that the 
betas are timebombed (and just a hint, if you read the forums a bit more, 
you can find out how to extend the beta without messing with your clock).

Jim

Post a reply to this message

mulciber nous illumina en ce 2008-11-23 00:12 -->
> beta 29 has expired and it's the 23rd.
> what's going on?
> 
> not really happy.
> 
> 
When you start the beta after the expiration date, you'll get an alert box 
telling you so. That same box also let you extend the beta, after a count down.

And, as others have said, the developpers don't only work on POV-Ray. They have 
a normal JOB, family, friends, and other real life occupations.

-- 
Alain
-------------------------------------------------
Experience hath shewn, that even under the best forms of government those
entrusted with power have, in time, and by slow operations, perverted it
into tyranny.
Thomas Jefferson

Post a reply to this message

Jim Henderson wrote:
> POVray is a project developed by people in their spare time, by and 
> large.  Life happens.
> 
>> not really happy.
> 
> Use the released version, then.  It's not like it's a secret that the 
> betas are timebombed (and just a hint, if you read the forums a bit more, 
> you can find out how to extend the beta without messing with your clock).
> 

My interpretation isn't that the original poster is complaining about how the
developers aren't working hard enough.  I think he's complaining that the beta expires
before another is available.  Sure, there's an esoteric way to get around the
expiration.  But it all seems a bit silly for the deadline to be so much shorter than
the beta release cycle.

Personally, I think the expiration time should just be boosted up.

Easy enough:
source/backend/povray.h:#define EXPIRE_AT       (1225490400)

Dan

Post a reply to this message

On Tue, 25 Nov 2008 17:49:10 -0800, Dan Connelly wrote:

> Jim Henderson wrote:
>> POVray is a project developed by people in their spare time, by and
>> large.  Life happens.
>> 
>>> not really happy.
>> 
>> Use the released version, then.  It's not like it's a secret that the
>> betas are timebombed (and just a hint, if you read the forums a bit
>> more, you can find out how to extend the beta without messing with your
>> clock).
>> 
>> 
> My interpretation isn't that the original poster is complaining about
> how the developers aren't working hard enough.  I think he's complaining
> that the beta expires before another is available.  Sure, there's an
> esoteric way to get around the expiration.  But it all seems a bit silly
> for the deadline to be so much shorter than the beta release cycle.

I think both of those ideas are opposite sides of the same coin.  The 
release cycle isn't fast enough = the developers aren't meeting 
milestones for beta releases fast enough = the developers aren't working 
hard enough.

Especially with developers who volunteer their time (or work unpaid for 
their work), it's easy to make that connection.

The standard answer has always been "if the betas aren't updated fast 
enough for you, then don't use the beta".  Have a look back over the 
forum at earlier complaints about betas not being released as the earlier 
one expires and you'll see what I mean.  My answer is nothing new.  I 
imagine that none of the official team has replied simply *because* 
anyone who can read the group can find their answer already.

> Personally, I think the expiration time should just be boosted up.

Well, that's the developers' call for the official beta builds.

> Easy enough:
> source/backend/povray.h:#define EXPIRE_AT       (1225490400)

Yes, or if you want to compile your own with the code that's available, 
you could just remove that check if it really bothers you that much.  But 
don't be surprised if you (not "you", Dan, but "you" generically) don't 
get much help if you report a problem with a custom-compiled build or are 
told to update to the latest official beta when the time comes.

That's *why* the expiration is in there.  Again, that's all been 
explained many, many, many times before by the POV Team.

Jim

Post a reply to this message

Dan Connelly nous illumina en ce 2008-11-25 20:49 -->
> Jim Henderson wrote:
>> POVray is a project developed by people in their spare time, by and 
>> large.  Life happens.
>>
>>> not really happy.
>>
>> Use the released version, then.  It's not like it's a secret that the 
>> betas are timebombed (and just a hint, if you read the forums a bit 
>> more, you can find out how to extend the beta without messing with 
>> your clock).
>>
> 
> My interpretation isn't that the original poster is complaining about 
> how the developers aren't working hard enough.  I think he's complaining 
> that the beta expires before another is available.  Sure, there's an 
> esoteric way to get around the expiration.  But it all seems a bit silly 
> for the deadline to be so much shorter than the beta release cycle.
> 
> Personally, I think the expiration time should just be boosted up.
> 
> Easy enough:
> source/backend/povray.h:#define EXPIRE_AT       (1225490400)
> 
> Dan

In what way does waiting a few second and clicking a "Prolong" button is 
"esotheric"?
No need to fiddle with your system clock.
NO need to recompile.

Yes! The current betas do have an inbuilt extention option. The only thing, is 
that you agree to NOT file a bug report after you have used that option.

-- 
Alain
-------------------------------------------------
  Maybe God wants us to meet a few wrong people before meeting the right one, so 
that when we finally meet the person, we will know how to be grateful.

Post a reply to this message