You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by Lucas Burson <lj...@gmail.com> on 2012/12/04 08:52:32 UTC
correct response to finding previous found bug?
Hi,
I was doing some regression testing on Ubuntu and discovered a bug
which was already reported [1]. It's about 3 months old.
That got me wondering, is there some "best practice" (or something) to
update a previously found bug? In bugzilla, should I add a comment and
update the 'last confirmation date' field?
Also any idea where in the source I would browse to investigate this
'Auto Text' paths?
Thanks,
Lucas
[1] https://issues.apache.org/ooo/show_bug.cgi?id=121028
Re: correct response to finding previous found bug?
Posted by Rob Weir <ro...@apache.org>.
On Tue, Dec 4, 2012 at 1:29 PM, Lucas Burson <lj...@gmail.com> wrote:
> Well, that got complicated. Thanks for finding that, Ariel. it'll help
> me find out how this stuff is put together.
>
> Can I ask here to get edit privs on AOO bugzilla?
>
I've added you to the qa-team role, so you now have additional edit
permissions in Bugzilla.
-Rob
>
> On Tue, Dec 4, 2012 at 11:19 AM, Ariel Constenla-Haile
> <ar...@apache.org> wrote:
>> Hi Lucas,
>>
>> On Tue, Dec 04, 2012 at 01:52:32AM -0600, Lucas Burson wrote:
>>> Hi,
>>>
>>> I was doing some regression testing on Ubuntu and discovered a bug
>>> which was already reported [1]. It's about 3 months old.
>>> That got me wondering, is there some "best practice" (or something) to
>>> update a previously found bug? In bugzilla, should I add a comment and
>>> update the 'last confirmation date' field?
>>>
>>> Also any idea where in the source I would browse to investigate this
>>> 'Auto Text' paths?
>>
>> See my comment in the bug:
>>
>>> [1] https://issues.apache.org/ooo/show_bug.cgi?id=121028
>>
>> The bug is in the framework module, not in that dialog, nor in Writer.
>>
>>
>> Regards
>> --
>> Ariel Constenla-Haile
>> La Plata, Argentina
Re: correct response to finding previous found bug?
Posted by Jürgen Schmidt <jo...@gmail.com>.
On 12/5/12 5:34 AM, Lucas Burson wrote:
>> Do you know C++? Are you willing to dive into the source? I/we can give
>> a hand and point you where to look.
>
> I do know C++ (and xslt, if it's anywhere) and I am willing to play
> with source. The downside is that I've never worked on a project of
> this size... so I started with picking up QA stuff. But I would
> definitely like to help.
it can be of course a challenge to work on a project of this size but I
can ensure that it is no magic ;-) You will notice that everybody is
cooking with water only.
The problem is that it is a lot of code, grown over years and that often
documentation is missing. It means also that the code and the style is
different, old code looks different than newer code etc.
But we have tools to search the code and when you have found specific
areas of your interest you can focus on this code. You don't need the
knowledge of everything. The work with the code will guide you
automatically in further code areas and you will learn more and more
over time.
Don't be shy and try it out and what's more important feel free to ask
questions here on the list. Taking the huge size of the code base into
account I would say that it gives not really stupid questions ;-),
please simply ask.
Welcome on board
Juergen
>
>
> Lucas
>
Re: correct response to finding previous found bug?
Posted by Ariel Constenla-Haile <ar...@apache.org>.
Hi Lucas,
On Thu, Dec 06, 2012 at 12:49:08PM -0600, Lucas Burson wrote:
> >
> > Yes, it is as a tag and there is a branch for 3.4*, but if you want to
> > start developing, the best it work directly with trunk (and use git-svn
> > instead of subversion, it is better for a project this size; I don't
> > recall if there is somewhere on the building guide a instruction to
> > check out the source with git-svn, but I can give the one I use in case
> > you choose git instead of subversion).
> >
>
> Thanks forthe info Ariel. Is [1] the right place for the AOO4 M1 code?
This is 3.4.1 tag:
http://svn.apache.org/viewvc/openoffice/tags/AOO341/
svn co https://svn.apache.org/repos/asf/openoffice/tags/AOO341
This is 3.4 branch:
http://svn.apache.org/viewvc/openoffice/branches/AOO34/
svn co https://svn.apache.org/repos/asf/openoffice/branches/AOO34
For development, you should checkout trunk, the 3.4 branch is only for
adding new translations.
> And I found [2] which has 'git svn clone ...', is that git-svn?
Yes, but you should use the master server URL (IIRC this was an advice
from Eike or Michael Stahl):
git svn clone https://svn-master.apache.org/repos/asf/openoffice/trunk
> I've used git for a couple of small github projects but never mixed
> svn and git.
There is a small tutorial
http://trac.parrot.org/parrot/wiki/git-svn-tutorial
If you search on the web, you'll find more. If you are familiar with
git, it is rather simple, you use the svn wrapper only for updating the
sources and committing changes (git svn rebase, git svn dcommit), for
all the rest it's just git :)
Regards
--
Ariel Constenla-Haile
La Plata, Argentina
Re: correct response to finding previous found bug?
Posted by Lucas Burson <lj...@gmail.com>.
>
> Yes, it is as a tag and there is a branch for 3.4*, but if you want to
> start developing, the best it work directly with trunk (and use git-svn
> instead of subversion, it is better for a project this size; I don't
> recall if there is somewhere on the building guide a instruction to
> check out the source with git-svn, but I can give the one I use in case
> you choose git instead of subversion).
>
Thanks forthe info Ariel. Is [1] the right place for the AOO4 M1 code?
And I found [2] which has 'git svn clone ...', is that git-svn? I've
used git for a couple of small github projects but never mixed svn and
git. I do want to help with development.
[1] https://svn.apache.org/repos/asf/openoffice/tags/SNAPSHOT/
[2] http://wiki.openoffice.org/wiki/Source_Code
Re: correct response to finding previous found bug?
Posted by Ariel Constenla-Haile <ar...@apache.org>.
Hi Lucas,
On Thu, Dec 06, 2012 at 10:41:58AM -0600, Lucas Burson wrote:
> > Good to know. Did you already build OpenOffice? In which platform are
> > you developing?
>
> Nope, I did not build it yet.
> I did get the AOO4.0 M1 binary release and I've done a few manual
> tests on TestLink; soon I'll checkout the svn automated tests to see
> what that's like (looked really easy, someone did a nice job). I use
> Ubuntu 64bit.
>
> Is the Milestone 1 release on SVN? I could try building that
Yes, it is as a tag and there is a branch for 3.4*, but if you want to
start developing, the best it work directly with trunk (and use git-svn
instead of subversion, it is better for a project this size; I don't
recall if there is somewhere on the building guide a instruction to
check out the source with git-svn, but I can give the one I use in case
you choose git instead of subversion).
Regards
--
Ariel Constenla-Haile
La Plata, Argentina
Re: correct response to finding previous found bug?
Posted by Lucas Burson <lj...@gmail.com>.
> Good to know. Did you already build OpenOffice? In which platform are
> you developing?
Nope, I did not build it yet.
I did get the AOO4.0 M1 binary release and I've done a few manual
tests on TestLink; soon I'll checkout the svn automated tests to see
what that's like (looked really easy, someone did a nice job). I use
Ubuntu 64bit.
Is the Milestone 1 release on SVN? I could try building that
Regards,
Lucas
Re: correct response to finding previous found bug?
Posted by Ariel Constenla-Haile <ar...@apache.org>.
Hi Lucas,
On Tue, Dec 04, 2012 at 10:34:24PM -0600, Lucas Burson wrote:
> > Do you know C++? Are you willing to dive into the source? I/we can give
> > a hand and point you where to look.
>
> I do know C++ (and xslt, if it's anywhere) and I am willing to play
> with source. The downside is that I've never worked on a project of
> this size... so I started with picking up QA stuff. But I would
> definitely like to help.
Good to know. Did you already build OpenOffice? In which platform are
you developing?
Regards
--
Ariel Constenla-Haile
La Plata, Argentina
Re: correct response to finding previous found bug?
Posted by Lucas Burson <lj...@gmail.com>.
> Do you know C++? Are you willing to dive into the source? I/we can give
> a hand and point you where to look.
I do know C++ (and xslt, if it's anywhere) and I am willing to play
with source. The downside is that I've never worked on a project of
this size... so I started with picking up QA stuff. But I would
definitely like to help.
Lucas
Re: correct response to finding previous found bug?
Posted by Ariel Constenla-Haile <ar...@apache.org>.
Hi Lucas,
On Tue, Dec 04, 2012 at 12:29:22PM -0600, Lucas Burson wrote:
> Well, that got complicated. Thanks for finding that, Ariel. it'll help
> me find out how this stuff is put together.
Do you know C++? Are you willing to dive into the source? I/we can give
a hand and point you where to look.
> Can I ask here to get edit privs on AOO bugzilla?
Yes, you can. Please post a new mail with the request on the subject, so
that bugzilla admins can detect the request easily.
Regards
--
Ariel Constenla-Haile
La Plata, Argentina
Re: correct response to finding previous found bug?
Posted by Lucas Burson <lj...@gmail.com>.
Well, that got complicated. Thanks for finding that, Ariel. it'll help
me find out how this stuff is put together.
Can I ask here to get edit privs on AOO bugzilla?
On Tue, Dec 4, 2012 at 11:19 AM, Ariel Constenla-Haile
<ar...@apache.org> wrote:
> Hi Lucas,
>
> On Tue, Dec 04, 2012 at 01:52:32AM -0600, Lucas Burson wrote:
>> Hi,
>>
>> I was doing some regression testing on Ubuntu and discovered a bug
>> which was already reported [1]. It's about 3 months old.
>> That got me wondering, is there some "best practice" (or something) to
>> update a previously found bug? In bugzilla, should I add a comment and
>> update the 'last confirmation date' field?
>>
>> Also any idea where in the source I would browse to investigate this
>> 'Auto Text' paths?
>
> See my comment in the bug:
>
>> [1] https://issues.apache.org/ooo/show_bug.cgi?id=121028
>
> The bug is in the framework module, not in that dialog, nor in Writer.
>
>
> Regards
> --
> Ariel Constenla-Haile
> La Plata, Argentina
Re: correct response to finding previous found bug?
Posted by Ariel Constenla-Haile <ar...@apache.org>.
Hi Lucas,
On Tue, Dec 04, 2012 at 01:52:32AM -0600, Lucas Burson wrote:
> Hi,
>
> I was doing some regression testing on Ubuntu and discovered a bug
> which was already reported [1]. It's about 3 months old.
> That got me wondering, is there some "best practice" (or something) to
> update a previously found bug? In bugzilla, should I add a comment and
> update the 'last confirmation date' field?
>
> Also any idea where in the source I would browse to investigate this
> 'Auto Text' paths?
See my comment in the bug:
> [1] https://issues.apache.org/ooo/show_bug.cgi?id=121028
The bug is in the framework module, not in that dialog, nor in Writer.
Regards
--
Ariel Constenla-Haile
La Plata, Argentina
Re: correct response to finding previous found bug?
Posted by Jürgen Schmidt <jo...@gmail.com>.
On 12/4/12 8:52 AM, Lucas Burson wrote:
> Hi,
>
> I was doing some regression testing on Ubuntu and discovered a bug
> which was already reported [1]. It's about 3 months old.
> That got me wondering, is there some "best practice" (or something) to
> update a previously found bug? In bugzilla, should I add a comment and
> update the 'last confirmation date' field?
yes, I think a new comment in the existing bug is a good approach. And
updating the 'last confirmation date' seems to be appropriate to me as
well.
>
> Also any idea where in the source I would browse to investigate this
> 'Auto Text' paths?
mmh, I don't know. I would assume in the writer somewhere but I have no
real idea.
OpenGrok is a nice tool to search the code base
http://opengrok.adfinis-sygroup.org/source/
Juergen
>
> Thanks,
> Lucas
>
> [1] https://issues.apache.org/ooo/show_bug.cgi?id=121028
>