Re: [ jEdit-devel ] bug report directions

[Alan E. <ala...@gm...>]

I updated what is displayed in the jedit bugs tracker itself.
I was going to start editing the feedback page, but I was having trouble
with my shell connection to sf.net.

It's a PITA to edit those web files, and I think they should be under
revision control so we can commit to them via svn, and have them
automatically update the website daily or something.




On Sat, Jan 7, 2012 at 5:45 AM, Jarek Czekalski <jar...@po...>wrote:

> Recently a guy sent a complain to a bug tracker. It should be answered
> beginning with:
>
> This bug report does not fulfil our bug report directions (guidelines?).
> Please see ..... (link)
>
> But we don't have such directions. We have a bit here:
> http://www.jedit.org/index.php?page=feedback
> but this page must be changed to allow direct linking to the Reporting
> Bugs section.
>
> What needs to be added:
> - about steps to reproduce, a precise example could be good, or maybe a
> whole bug report example (a template?)
> - about desired behaviour
>
> Always feel free to correct my language errors or ambiguities. I passed
> only First Certificate and it was many years ago :)
>
> Jarek
>
>
> ------------------------------------------------------------------------------
> Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
> infrastructure or vast IT resources to deliver seamless, secure access to
> virtual desktops. With this all-in-one solution, easily deploy virtual
> desktops for less than the cost of PCs and save 60% on VDI infrastructure
> costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
> --
> -----------------------------------------------
> jEdit Developers' List
> jEd...@li...
> https://lists.sourceforge.net/lists/listinfo/jedit-devel
>