Stefan Peter
unread,Apr 27, 2015, 2:43:32 PM4/27/15Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Sign in to report message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Bug 1448816, hugi...@googlegroups.com
On 27.04.2015 17:16, tmodes wrote:
>> The .py modules mentioned shold be changed to have
>> # @api-max 2015.0
>> instead of
>> # @api-max 2014.1
>
> I know. But it would be nice if someone could test the scripts and
> report back if there are still running. (I never used them so I can not
> judge if they are still okay.)
I can not judge, either. But api-max was set to 2014.1, so I assume that
these scripts were activated in the development version. I'd expect that
a breakage would have been noticed there.
>
> Currently it seems that woa is currently not running, so for woa we can
> not update the api-max. Only when the issue is fixed we need to update
> api-min *and* api-max for woa then.
>
If this is true, it seems that no one cared during the development cycle
then. Wouldn't it be more honest to axe woa if nobody gives a damn?
Regards
Stefan Peter
--
Any technology that does not appear magical is insufficiently advanced."
~ Gregory Benford