lyskomd-qa February 2006

lyskomd-qa@lists.lysator.liu.se

1 participants
7 discussions

[Bug 1601] Don't garb newly changed texts
by bugzilla-daemon＠lysator.liu.se 15 Feb '06

15 Feb '06

http://bugzilla.lysator.liu.se/show_bug.cgi?id=1601 ceder(a)lysator.liu.se changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Additional Comments From ceder(a)lysator.liu.se 2006-02-15 17:39 ------- The new field need not be changed to the database. Instead, we could postpone running the garb until the server has been up for at least 7 days, and have an in-core representation of the text numbers that we cannot touch for the next 7 days. Or, the set of untouchable text numbers could be saved in a separate file, so that we don't have to change the file format. Yet another alternative would be to add an automatic garb-prohibited-before aux item, with the cutoff date as the data. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 1601] New: Don't garb newly changed texts
by bugzilla-daemon＠lysator.liu.se 15 Feb '06

15 Feb '06

http://bugzilla.lysator.liu.se/show_bug.cgi?id=1601 Summary: Don't garb newly changed texts Product: lyskomd Version: 2.1.2 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: server AssignedTo: ceder(a)lysator.liu.se ReportedBy: ceder(a)lysator.liu.se QAContact: lyskomd-qa(a)lists.lysator.liu.se A text should be protected from garbing for a few days after anything has changed in it. If a conference is deleted, the texts can still be restored relatively easy (if you have access to the database files) as long as the texts are not garbed. Once the garb runs, however, things get a lot more complex. If each text-stat had a status-change-time field that was updated when the recipient list changes, the garb could check that the text is at least 7 days old before doing anything with it. (This should be a server-global configuration, set in the lyskomd.conf file.) ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 1600] Enable tagging of texts
by bugzilla-daemon＠lysator.liu.se 12 Feb '06

12 Feb '06

http://bugzilla.lysator.liu.se/show_bug.cgi?id=1600 ceder(a)lysator.liu.se changed: What |Removed |Added ---------------------------------------------------------------------------- OtherBugsDependingO| |1596 nThis| | Status|NEW |ASSIGNED ------- Additional Comments From ceder(a)lysator.liu.se 2006-02-12 08:12 ------- Bug 119 ("keyword support on conferences") is somewhat related to this bug, but it comes from an era when I believed in a centrally enforced order. It would probably make sense to be able to tag conferences as well, but tagging texts is more important, I believe. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 1600] New: Enable tagging of texts
by bugzilla-daemon＠lysator.liu.se 12 Feb '06

12 Feb '06

http://bugzilla.lysator.liu.se/show_bug.cgi?id=1600 Summary: Enable tagging of texts Product: lyskomd Version: 2.1.2 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: server AssignedTo: ceder(a)lysator.liu.se ReportedBy: ceder(a)lysator.liu.se QAContact: lyskomd-qa(a)lists.lysator.liu.se It would be useful to be able to tag texts. http://del.icio.us/help/tags explains "tags" like this: > What are tags? > > Tags are one-word descriptors that you can assign to any > bookmark. Tags can't contain quotation marks or whitespace, but are > otherwise unrestricted. You can assign as many tags to a bookmark as > you like, and rename, delete, add or merge tags together. > > What are tags good for? > > Tagging can be a whole lot easier and more flexible than fitting your > information into preconceived categories. If you want to post an > article about a little known Greek philosopher, just tag it with > "philosophy greece" or whatever other tags you'd want to use to find > it again. You don't have to rely on the designer of the system to > provide you with category for Greek philosophy. You just make up tags > as you need them. > > That's great for organizing personal data, but it goes even further > when someone else posts related content with the same tags. You begin > building a collaborative repository of related information, driven by > personal interests and creative organization. For instance, to view > everybody's bookmarks on design, visit del.icio.us/tag/design. > > Yeah but I still don't get it > > That's ok, you don't have to. It's pretty intuitive and takes a bit of > practice to fully understand. Just try it and experiment a bit! I'd like a similar feature to tag texts in the LysKOM system. Tags: - must be easy to create - must be indexed for easy retrieval - it must be possible to retrieve all texts relating to a certain tag, or to a number of tags ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 1599] Unclean shutdown if errors found during startup
by bugzilla-daemon＠lysator.liu.se 09 Feb '06

09 Feb '06

http://bugzilla.lysator.liu.se/show_bug.cgi?id=1599 ------- Additional Comments From ceder(a)lysator.liu.se 2006-02-09 09:02 ------- src/server/testsuite/lyskomd.0/53.exp highlights one instance of this problem. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 1599] Unclean shutdown if errors found during startup
by bugzilla-daemon＠lysator.liu.se 09 Feb '06

09 Feb '06

http://bugzilla.lysator.liu.se/show_bug.cgi?id=1599 ceder(a)lysator.liu.se changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Target Milestone|--- |Future ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 1599] New: Unclean shutdown if errors found during startup
by bugzilla-daemon＠lysator.liu.se 09 Feb '06

09 Feb '06

http://bugzilla.lysator.liu.se/show_bug.cgi?id=1599 Summary: Unclean shutdown if errors found during startup Product: lyskomd Version: 2.1.2 Platform: All OS/Version: All Status: NEW Severity: minor Priority: P2 Component: server AssignedTo: ceder(a)lysator.liu.se ReportedBy: ceder(a)lysator.liu.se QAContact: lyskomd-qa(a)lists.lysator.liu.se If an error is found during startup, the process will just call restart_kom. This makes it hard to find memory leaks that occur during problematic startups, since a lot of memory references will be held. It would be better to let each module have two functions: startup and cleanup. Build a framework that calls each startup in turn. If a startup function indicates that it failed, all the cleanup functions that correspond to successful startup functions would be called, in reverse order. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

lyskomd-qa February 2006