Edgewall Software

Changes between Version 18 and Version 19 of TracTicketsCustomTimeFields


Ignore:
Timestamp:
Apr 17, 2010, 3:37:01 PM (14 years ago)
Author:
hoff.st@…
Comment:

added announcement of patch set in alpha status

Legend:

Unmodified
Added
Removed
Modified
  • TracTicketsCustomTimeFields

    v18 v19  
    3535
    3636=== Status of Development ===
    37 No longer bug-fixing here and there, 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.
     37I've decided on going public with my current Mercurial queue applicable for Trac trunk r9443 cloned from rblanks Mercurial repository at bitbucket.org. Here it is:
     38
     39 http://bitbucket.org/hasienda/custom-time/overview
     40
     41I consider the code in alpha stage right now. If you pull that early, test tickets may 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.
     42
     43No 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.
    3844
    3945Code of former implementation was published but removed later from Mercurial repository (see ''custom-time'' branch) at
    40  http://traccustom-time.hg.sourceforge.net:8000/hgroot/traccustom-time/traccustom-time
     46 !http://traccustom-time.hg.sourceforge.net:8000/hgroot/traccustom-time/traccustom-time
    4147because I re-based on a 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)
    4248