Changes between Version 13 and Version 14 of TracTicketsCustomTimeFields

Timestamp:

Apr 9, 2010, 12:42:28 AM (14 years ago)

Author:

hoff.st@…

Comment:

added link to other related ticket, more info about development

TracTicketsCustomTimeFields

@@ -23 +23 @@
 
 === Status of Development ===
-Code was published in a Mercurial repository (see ''custom-time'' branch) at
+Code was published but removed later from Mercurial repository (see ''custom-time'' branch) at
  http://traccustom-time.hg.sourceforge.net:8000/hgroot/traccustom-time/traccustom-time
-currently with SVN changes up to trac SVN changeset r9442.
+because I re-based on clone of rblank's Mercurial repository with SVN changes up to trac SVN changeset r9443 and moved changes to Mercurial patch queue, and there is no sane way to push to repository (just volatile changesets), will not dare to push again before substantial clearing with core developers is reached, however patch files will get published somehow (starting with #9209)
 
 Feedback could happen through
@@ -31 +31 @@
  * edits to (the discussion section of) this wiki page,
  * private e-mail, or
- * commits to VCS after initial per-developer arrangement inside the Sourceforge project.
+ * ~~commits to VCS after initial per-developer arrangement inside the Sourceforge project~~,
  * chat while I'm arround in IRC channel #trac at freenode.net
 
 ==== Known Bugs ====
-I recognized at least a glitch on creation of new tickets that needs to be fixed ASAP.
+I recognized at problems on creation of new tickets that needs to be fixed ASAP.
 
 ==== Making ''mxDateTime.Parser'' an option ====
@@ -59 +59 @@
 Happened to have access to !SourceForge, so I choose to go and push code into a Mercurial repository there to enable collaboration based on a distributed VCS as per suggestion from IRC channel #trac at freenode.net.
  rblank offered to rebase my code on top of code from his own repository, so a least he would be able to rewiev more easily. I'll try it and combine this move with a trial on Mercurial patch queue.
+  '''Done''', re-based on clone of rblank's Mercurial repository, all changes converted to patch series,[[BR]]cleared repository on Sourceforge, because previous work was to dirty and non-functional in early tests, I found that I forgot to ''--addremove'' after pull/merge and so missed new files as well as deletions
 
-Current development is based on Trac-0.12dev_~~r9115~~r9442 (see current state), testet with Python2.5 on ''Debian GNU/Linux'' stable. However it would be great to have it in trunk soon (trac-0.12.x?).
+Current development is based on Trac-0.12dev_~~r9115~~r9443 (see current state), testet with Python2.5 on ''Debian GNU/Linux'' stable. However it would be great to have it in trunk soon (trac-0.12.x?).
   (cboos): that's way too old to base new development upon, especially for timestamp related development, as r9210 introduced a big change here (time are now stored as microseconds elapsed since epoch, as bigints).
     Ah, well, thanks for the hint. We're at r9420 right now, any recommendation where to start from other than HEAD? 
@@ -77 +78 @@
  #2288 asked for date/time based ticket query functions, that exist by now[[BR]]
  #8354 seeking to get more date/time related information from queries, following #2288[[BR]]
- #6466 asked for higher time stamp precision introduced with microseconds for ''time'' and ''changetime'' in r9210
+ #6466 asked for higher time stamp precision introduced with microseconds for ''time'' and ''changetime'' in r9210[[BR]]
+ #9209 suggests code cleanup for trac/ticket/model.py, as side effect of my code review for this project
 
 == External related resources ==