Changes between Version 23 and Version 24 of TracTicketsCustomTimeFields

Timestamp:

Apr 21, 2010, 2:06:32 AM (14 years ago)

Author:

hoff.st@…

Comment:

marked fixed bugs, changed bug description according to current behavior

TracTicketsCustomTimeFields

@@ -40 +40 @@
 
 ''base'': patches apply cleanly to Trac trunk r9443, cloned from rblank's Mercurial repository at bitbucket.org.[[BR]]
-''quality'': alpha - major design flaws and backward-incompatible changes possible until stable release[[BR]]
-''focus'': completion of basic functionality, bug-fixes
+''quality'': beta - code flaws should no longer affect db, only minor changes expected until stable release[[BR]]
+''focus'': completion of basic functionality, bug-fixes[[BR]]
 ''reviews'': so far just me
 
-If you pull that early, test tickets may pollute your db with nasty values that need to be discharged for the final implementation to work flawlessly. You've been warned. See [#KnownBugs Known Bugs] for more details. As soon as I see sort of a release candidate, I'll let you know.
+You may pull right now, or wait for an official call for beta-test, that will be announced after code works more flawlessly. There might still lure some serious bug I'm currently not aware of. You've been warned. See [#KnownBugs Known Bugs] for more details. A release candidate is not far away now.
 
 No longer bug-fixing on my initial approach, but doing a fresh and hopefully clean new implementation as detailed above. Assume to come out with some patches soon. I've setup [http://bitbucket.org/hasienda/shelf/ my place at bitbucket.org] recently, that'll make collaboration via a Mercurial repository easier than via Sourceforge.net.
@@ -61 +61 @@
 ==== Known Bugs ====
 Problems (with priority) occurring arround ticket changes
- * (C) preview time stamp format is not pretty, like '2010-04-19 20:03:00+00:00' instead of '19.04.2010 22:03:00'
- * (A) bad conversion of date/time value {{{None}}} to db string value {{{'None'}}} instead of {{{''}}}, gets overwritten with current date on next change, no date/time value deletion possible so far
- * (B) ticket diff view for change history exposes raw values from db, should convert microseconds POSIX to pretty time stamp string
+ * (A) preview time stamp format is throwing an exception
  * (B) [TracNotification Trac Notification] system unpatched, need to test and investigate, if necessary at all 
 fixed:
+ * ticket diff view for change history exposes raw values from db, should convert microseconds POSIX to pretty time stamp string
+ * bad conversion of date/time value {{{None}}} to db string value {{{'None'}}} instead of {{{''}}}, gets overwritten with current date on next change, no date/time value deletion possible so far
  * notification throwing an error note related to unexpected datetime.datetime input to [TracNotification Trac Notification] system: gone while correcting functions preceding in ticket change process, not even sure it was Trac Notification, since this was not active at time of test
  * current date is injected whenever time field is left/made empty: after extending all other functions the parser logic was the one place, where 'default_now' logic still happened overwriting undefined date/time