 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
http://bugs.povray.org/
The above link leads to a blank "Not Found" page. Is there a new system
in place?
Mike
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 9/14/2016 2:57 AM, Mike Horvath wrote:
> http://bugs.povray.org/
>
> The above link leads to a blank "Not Found" page. Is there a new system
> in place?
>
>
> Mike
I found it on github.
Mike
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 9/14/2016 3:07 AM, Mike Horvath wrote:
> On 9/14/2016 2:57 AM, Mike Horvath wrote:
>> http://bugs.povray.org/
>>
>> The above link leads to a blank "Not Found" page. Is there a new system
>> in place?
>>
>>
>> Mike
>
> I found it on github.
is the official enough for me to change in the docs and mention github
instead?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 09/21/2016 05:08 PM, Jim Holsenback wrote:
> On 9/14/2016 3:07 AM, Mike Horvath wrote:
>> On 9/14/2016 2:57 AM, Mike Horvath wrote:
>>> http://bugs.povray.org/
>>>
>>> The above link leads to a blank "Not Found" page. Is there a new system
>>> in place?
>>>
>>>
>>> Mike
>>
>> I found it on github.
>
> is the official enough for me to change in the docs and mention github
> instead?
I found the FlySpray bug site up a few minutes ago. Thank you to
whomever brought the site back up again!
Given our code base is on github, new issues and requests should
certainly be created on github and so I believe our recent documentation
updates to point new issues to github are OK.
The question I have is whether bugs.povray.org will now be available
indefinitely and something we can continue to refer to on github or
should we work to port the FlySpray issues over to github issues where
the FS issues are still meaningful with the idea the FlySpray site will
be going away?
Maybe some partial movement of only 3.7+ issues to github given the
FlySpray site is valid for reporting 3.6 issues, where github is only
valid for 3.7 onward?
Bill P.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 03.10.2016 um 17:26 schrieb William F Pokorny:
> The question I have is whether bugs.povray.org will now be available
> indefinitely and something we can continue to refer to on github or
> should we work to port the FlySpray issues over to github issues where
> the FS issues are still meaningful with the idea the FlySpray site will
> be going away?
So far there is no intention to shut down the FlySpray tracker, but the
incident shows that nobody is breaking a leg to keep it well-maintained
either; so I think we better prepare for it to disappear sooner or later
(probably with a whimper rather than a bang). There is no real point in
maintaining two issue trackers in parallel, and although the FlySpray
tracker is much more powerful, the GitHub issue tracker has already won
the race merely by sitting right there alongside the repo where
development happens anyway.
> Maybe some partial movement of only 3.7+ issues to github given the
> FlySpray site is valid for reporting 3.6 issues, where github is only
> valid for 3.7 onward?
When it comes to bugs that are truly 3.6-only, I guess we won't find any
volunteers to do any more maintenance on 3.6 anyway, so why even bother.
Bugs reported for 3.6 but still valid for 3.7, now that's an entirely
different matter.
If you'd be willing to port the open FlySpray issues in a useful manner,
maybe even going the extra mile (as you tend to do) and giving them a
thorough review for relevancy, at least I for one would appreciate that.
BTW, is there an e-mail address by which you can be reached? In case
you're reluctant to disclose it publicly, please drop an e-mail to
Christoph at Lipka-Koeln, dot DE.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
