I have created the issue OPENMEETINGS-806<https://issues.apache.org/jira/browse/OPENMEETINGS-806>
I was able to reproduce and fix it and there were no reasons to wait if issue will be created or not :) Issues are necessary since: 1) all resolved issues are goes to release notes automatically 2) it is not lost in the mails On Mon, Sep 30, 2013 at 3:02 PM, Sam Hagen <hagen....@gmail.com> wrote: > Cool, thanks! Is it worth me documenting the issue if it's already been > resolved and committed? (Sorry if these questions are profoundly > elementary; I'm still getting the hang of the etiquette surrounding this > stuff) :-) > On Sep 30, 2013 3:47 AM, "Maxim Solodovnik" <solomax...@gmail.com> wrote: > >> sure :) >> >> go here: >> https://issues.apache.org/jira/browse/OPENMEETINGS<https://issues.apache.org/jira/browse/OPENMEETINGS-806> >> register >> create new issue >> >> the one reported by you >> https://issues.apache.org/jira/browse/OPENMEETINGS-806 is already fixed >> for upcoming 2.2 and 3.0 versions >> >> >> >> On Mon, Sep 30, 2013 at 2:42 PM, Sam Hagen <hagen....@gmail.com> wrote: >> >>> Hi there! >>> >>> Thanks for taking a look at this. I am, unfortunately a noob when it >>> comes to development and so I don't know what you mean by "filing jira >>> issue." Would you be so kind as to fill me in or direct me to a tutorial? >>> I'd appreciate it and would be happy to do so if it's still needed. >>> >>> Best >>> >>> Sam >> >> >> >> >> -- >> WBR >> Maxim aka solomax >> > -- WBR Maxim aka solomax
