Changes between Version 43 and Version 44 of TracTicketsCustomTimeFields

Timestamp:

Sep 16, 2012, 12:52:55 AM (12 years ago)

Author:

Steffen Hoffmann

Comment:

quick restructuring of page content to clearify recommendation for testing

TracTicketsCustomTimeFields

@@ -5 +5 @@
 This page presents information on adding a new type 'time' to the list of all currently available [wiki:TracTicketsCustomFields custom ticket fields].[[BR]]
 You may want to start by reading the [wiki:TracDev/Proposals/TracTicketsCustomTimeFields proposal page], that has more general information on this project.
+
+== !HowTo testing ==
+As stated above, the code has finally been pushed to Trac development branch and is `trunk` r11333, accompanied by a fresh jQuery date-picker implementation.
+
+''Note: Information below is outdated now. Please checkout current `trunk` and report your findings.''
 
 == Code review ==
@@ -30 +35 @@
 1. The common setup for Mercurial Queue puts the patches aside the main repository - into a Mercurial repo on it's own. So looking at [https://bitbucket.org/hasienda/trac-1942/changesets the changes] during development is as easy as looking at development in any repository.
 2. Since there is no other sane way to push changes to a public repository without making them irreversible, this look like the ideal compromise until substantial clearing with core Trac developers has been reached. However, some code already got forwarded for adoption into Trac `trunk`, like the one published in #9209).
-
-== !HowTo testing ==
-''Note: This is very outdated now. Until I step-up with a full revision you can still try and checkout the patch files and apply them on-top of trac `trunk` r10883.''
 
 For help on applying the patches to Trac trunk source the traditional way, i.e. with {{{patch}}}, look at the patch documentation in the [https://bitbucket.org/hasienda/trac-1942/src/tip/series series] file.