Can you PLEASE post a list of features to be implemented on the 'ol website? A ToDo feature list? :-) ********************************* Jake Covert Infrastructure Analyst Electronic Data Systems PSIC Support Group (586) 986-9698 Work (586) 518-3859 Pager http://www.eds.com ********************************* -----Original Message----- From: dev-bounces@otrs.org [mailto:dev-bounces@otrs.org] On Behalf Of Martin Edenhofer Sent: Monday, February 23, 2004 2:57 PM To: dev@otrs.org Subject: [dev] CVS: 1.2 branch! Hi, today we created a cvs branch for OTRS 1.2. That means this branch will have all future bug fixes for OTRS 1.2.x (just bug fixes no new features). So the cvs (HEAD) is ready for new features (planned features see TODO file). To checkout the 1.2 branch use: =============================== "cvs -z3 -d :pserver:<user>@cvs.otrs.org:/home/cvs co -r rel-1_2 otrs" To checkout the cvs HEAD use: ============================= "cvs -z3 -d :pserver:<user>@cvs.otrs.org:/home/cvs co otrs" Thanks, happy coding! .-) Martin -- ((otrs.de)) :: OTRS GmbH :: Norsk-Data-Str. 1 :: 61352 Bad Homburg http://www.otrs.de/ :: Manage your communication! _______________________________________________ OTRS mailing list: dev - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/dev To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev
On Mon, Feb 23, 2004 at 02:59:10PM -0500, Covert, Jake wrote:
Can you PLEASE post a list of features to be implemented on the 'ol website? A ToDo feature list?
:-)
Take "http://cvs.otrs.org/viewcvs.cgi/otrs/TODO" because it's not a static list. Or we move the TODO-list it to the documentation. Any comments?
********************************* Jake Covert Infrastructure Analyst Electronic Data Systems PSIC Support Group (586) 986-9698 Work (586) 518-3859 Pager http://www.eds.com *********************************
Martin Edenhofer -- ((otrs.de)) :: OTRS GmbH :: Norsk-Data-Str. 1 :: 61352 Bad Homburg http://www.otrs.de/ :: Manage your communication!
Hi Martin, I added complete TicketHookSpace support to 1.1.3 (on the TODO list previously for 1.2 and now for 1.3) and plan on adding that functionality to 1.2 once we get a chance to install the latest version. I had tried to submit diff files to the dev list with the necessary changes, but if I recall correctly, the messages were always rejected due to the size of the attachment. Is this something that is of interest to the developers? The changes were fairly minor, the largest being a modification to the regexes that check for the presence of the tickethook to ensure backwards compatibility with tickets already in the system and active. Is this something I should try to pass on again? What would be the best method to pass it along to the developers? Many thanks, Paul
-----Original Message----- From: dev-bounces@otrs.org [mailto:dev-bounces@otrs.org] On Behalf Of Martin Edenhofer Sent: Monday, February 23, 2004 2:57 PM To: dev@otrs.org Subject: [dev] CVS: 1.2 branch!
Hi,
today we created a cvs branch for OTRS 1.2. That means this branch will have all future bug fixes for OTRS 1.2.x (just bug fixes no new features).
So the cvs (HEAD) is ready for new features (planned features see TODO file).
To checkout the 1.2 branch use: =============================== "cvs -z3 -d :pserver:<user>@cvs.otrs.org:/home/cvs co -r rel-1_2 otrs"
To checkout the cvs HEAD use: ============================= "cvs -z3 -d :pserver:<user>@cvs.otrs.org:/home/cvs co otrs"
Thanks, happy coding! .-)
Martin
-- ((otrs.de)) :: OTRS GmbH :: Norsk-Data-Str. 1 :: 61352 Bad Homburg http://www.otrs.de/ :: Manage your communication!
Hi Paul, On Wed, Feb 25, 2004 at 08:42:22AM -0500, Paul wrote:
I added complete TicketHookSpace support to 1.1.3 (on the TODO list previously for 1.2 and now for 1.3) and plan on adding that functionality to 1.2 once we get a chance to install the latest version. I had tried to submit diff files to the dev list with the necessary changes, but if I recall correctly, the messages were always rejected due to the size of the attachment.
Is this something that is of interest to the developers? The changes were fairly minor, the largest being a modification to the regexes that check for the presence of the tickethook to ensure backwards compatibility with tickets already in the system and active.
Is this something I should try to pass on again? What would be the best method to pass it along to the developers?
Sorry about the missing TicketHookSpace-patch in 1.2 (I forgot :-/). If you have an download link for the cvs head, then post it an I will add the patch to the current cvs head. Thanks!
Paul
Martin -- ((otrs.de)) :: OTRS GmbH :: Norsk-Data-Str. 1 :: 61352 Bad Homburg http://www.otrs.de/ :: Manage your communication!
participants (3)
-
Covert, Jake -
Martin Edenhofer -
Paul