20 Mar
2015
20 Mar
'15
2:41 p.m.
On 17 March 2015 at 17:48, Smita <kumarismita62(a)gmail.com> wrote:
On Fri, Mar 13, 2015 at 12:07 AM, Atul Pratap Singh
<
atulpratapsingh05(a)gmail.com> wrote:
older by a certain number of releases. But, if we remove them completely, I
think we won't be able to find them at all, so unless it is making the
server slow? I think we can keep them.
Also after this year's gsoc project I hope it will become faster and with
some state maintenance and persistent settings, the sheer number of reports
won't come in our way when using it.
--
Atul Pratap Singh
http://blog.atulsisodia.in/
On 12 March 2015 at 23:47, Smita
<kumarismita62(a)gmail.com> wrote:
It seems, I misunderstood the question. Thanks Atul for clarifying.
I think, It would be better if it is marked outdated automatically by
reporting server.
BTW do we need to keep the older reports (outdated marked ones) on our
server? May be, we can remove the ones which are older by 5-6 versions?
I agree about automatically marking reports as "outdated" for versions
On Thu, Mar 12, 2015 at 6:22 PM, Marc Delisle
<marc(a)infomarc.info>
wrote:
more about
whether we should do it automatically as well for the newly
coming reports which belong for older versions?
Hi devs,
As a follow-up to [0], should we manually mark old tickets (older than
the current version) as being "out of date", or should it be done
automatically by the reporting server, or none of these?
Hi
I think doing it manually will be very tedious. It would be better if
its done from the server itself, may be a mysql query can be written to
mark old tickets "out of date".
Indeed, a query will be needed to do it manually, maybe the issue is