JK
Jörg Knobloch
Sun, Apr 22, 2018 1:52 PM
Hi fine friends of Thunderbird and people with fast processors, SSDs and
at least 4 GB of RAM ;-)
If you want to continue compiling your favourite application locally,
please consider switching to "M-C as top source directory". People doing
so are no longer the avant-garde; things have changed and people
compiling with C-C as top source directory will no longer be supported
and things will stop working for them. On Windows, they already get a
build warnings and, unless I missed something, some Xpcshell tests don't
run locally any more.
So let's compare old and new.
Old:
You checked out C-C, in there, you created a directory "mozilla" and
checked out M-C.
Your .mozconfig had |ac_add_options --enable-application=mail|.
You could refresh your local repositories with |python client.py checkout|.
To build, you used |mozilla/mach build|.
To run Xpcshell tests |mozilla/mach xpcshell-test
mailnews/base/test/unit/test_autoconfigFetchDisk.js|.
To run Mozmill tests (from the obj dir) |mozmake
SOLO_TEST=newmailaccount/test-newmailaccount.js mozmill-one|.
New:
You check out M-C, in there, you create a directory "comm" and check out
C-C (see below).
Your .mozconfig needs |ac_add_options --enable-application=comm/mail|.
|python client.py checkout| does not work any more, you need to use |hg
pull -u| twice.
To build, use |mach build|.
To run Xpcshell tests |mach xpcshell-test
comm/mailnews/base/test/unit/test_autoconfigFetchDisk.js|.
Running Mozmill tests hasn't changed.
Of course, to switch from the old setup to the new, you don't need to
checkout fresh copies. You can just shuffle files around. The object
directory will now sit as a sibling next to "comm". So delete the
previous object directory before moving things.
I attach a picture of the new setup.
Jörg.
P.S.:
https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Build_Instructions/Simple_Thunderbird_build
is now sadly out of date :-(
Hi fine friends of Thunderbird and people with fast processors, SSDs and
at least 4 GB of RAM ;-)
If you want to continue compiling your favourite application locally,
please consider switching to "M-C as top source directory". People doing
so are no longer the avant-garde; things have changed and people
compiling with C-C as top source directory will no longer be supported
and things will stop working for them. On Windows, they already get a
build warnings and, unless I missed something, some Xpcshell tests don't
run locally any more.
So let's compare old and new.
Old:
You checked out C-C, in there, you created a directory "mozilla" and
checked out M-C.
Your .mozconfig had |ac_add_options --enable-application=mail|.
You could refresh your local repositories with |python client.py checkout|.
To build, you used |mozilla/mach build|.
To run Xpcshell tests |mozilla/mach xpcshell-test
mailnews/base/test/unit/test_autoconfigFetchDisk.js|.
To run Mozmill tests (from the obj dir) |mozmake
SOLO_TEST=newmailaccount/test-newmailaccount.js mozmill-one|.
New:
You check out M-C, in there, you create a directory "comm" and check out
C-C (see below).
Your .mozconfig needs |ac_add_options --enable-application=comm/mail|.
|python client.py checkout| does not work any more, you need to use |hg
pull -u| twice.
To build, use |mach build|.
To run Xpcshell tests |mach xpcshell-test
comm/mailnews/base/test/unit/test_autoconfigFetchDisk.js|.
Running Mozmill tests hasn't changed.
Of course, to switch from the old setup to the new, you don't need to
checkout fresh copies. You can just shuffle files around. The object
directory will now sit as a sibling next to "comm". So delete the
previous object directory before moving things.
I attach a picture of the new setup.
Jörg.
P.S.:
https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Build_Instructions/Simple_Thunderbird_build
is now sadly out of date :-(
JK
Jörg Knobloch
Sun, Apr 22, 2018 2:02 PM
On 22/04/2018 15:52, Jörg Knobloch wrote:
Of course, to switch from the old setup to the new, you don't need to
checkout fresh copies. You can just shuffle files around.
I forgot to say:
I ran into build problems after shuffling files around and typing |mach
build| for the first time. The culprit was an empty file called
"configure" which wasn't under version control. Removing the file got me
going.
Jörg.
On 22/04/2018 15:52, Jörg Knobloch wrote:
> Of course, to switch from the old setup to the new, you don't need to
> checkout fresh copies. You can just shuffle files around.
I forgot to say:
I ran into build problems after shuffling files around and typing |mach
build| for the first time. The culprit was an empty file called
"configure" which wasn't under version control. Removing the file got me
going.
Jörg.
JK
Jonathan Kamens
Mon, Apr 23, 2018 1:16 PM
Thanks for the excellent step-by-step, Jörg. Using your instructions, I
was able to switch over to the new setup painlessly.
jik
On 4/22/18 10:02 AM, Jörg Knobloch wrote:
On 22/04/2018 15:52, Jörg Knobloch wrote:
Of course, to switch from the old setup to the new, you don't need to
checkout fresh copies. You can just shuffle files around.
Thanks for the excellent step-by-step, Jörg. Using your instructions, I
was able to switch over to the new setup painlessly.
jik
On 4/22/18 10:02 AM, Jörg Knobloch wrote:
> On 22/04/2018 15:52, Jörg Knobloch wrote:
>> Of course, to switch from the old setup to the new, you don't need to
>> checkout fresh copies. You can just shuffle files around.
>
> I forgot to say:
>
> I ran into build problems after shuffling files around and typing
> |mach build| for the first time. The culprit was an empty file called
> "configure" which wasn't under version control. Removing the file got
> me going.
>
> Jörg.
>
>
> _______________________________________________
> Maildev mailing list
> Maildev@lists.thunderbird.net
> http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net
>
>
T
Tito
Tue, May 1, 2018 8:22 PM
Hallo Jörg,
Could you please also share the Mozilla central repository link that you
have used? I have tried this one
https://hg.mozilla.org/mozilla-central/
but i do not see the comm directory there? Or have i overlooked
something? I.e. from the png picture you have attached in your last mail.
many thanks
Tito
On 4/22/18 3:52 PM, Jörg Knobloch wrote:
Hi fine friends of Thunderbird and people with fast processors, SSDs and
at least 4 GB of RAM ;-)
If you want to continue compiling your favourite application locally,
please consider switching to "M-C as top source directory". People doing
so are no longer the avant-garde; things have changed and people
compiling with C-C as top source directory will no longer be supported
and things will stop working for them. On Windows, they already get a
build warnings and, unless I missed something, some Xpcshell tests don't
run locally any more.
So let's compare old and new.
Old:
You checked out C-C, in there, you created a directory "mozilla" and
checked out M-C.
Your .mozconfig had |ac_add_options --enable-application=mail|.
You could refresh your local repositories with |python client.py checkout|.
To build, you used |mozilla/mach build|.
To run Xpcshell tests |mozilla/mach xpcshell-test
mailnews/base/test/unit/test_autoconfigFetchDisk.js|.
To run Mozmill tests (from the obj dir) |mozmake
SOLO_TEST=newmailaccount/test-newmailaccount.js mozmill-one|.
New:
You check out M-C, in there, you create a directory "comm" and check out
C-C (see below).
Your .mozconfig needs |ac_add_options --enable-application=comm/mail|.
|python client.py checkout| does not work any more, you need to use |hg
pull -u| twice.
To build, use |mach build|.
To run Xpcshell tests |mach xpcshell-test
comm/mailnews/base/test/unit/test_autoconfigFetchDisk.js|.
Running Mozmill tests hasn't changed.
Of course, to switch from the old setup to the new, you don't need to
checkout fresh copies. You can just shuffle files around. The object
directory will now sit as a sibling next to "comm". So delete the
previous object directory before moving things.
I attach a picture of the new setup.
Jörg.
P.S.:
https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Build_Instructions/Simple_Thunderbird_build
is now sadly out of date :-(
Maildev mailing list
Maildev@lists.thunderbird.net
http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net
Hallo Jörg,
Could you please also share the Mozilla central repository link that you
have used? I have tried this one
https://hg.mozilla.org/mozilla-central/
but i do not see the comm directory there? Or have i overlooked
something? I.e. from the png picture you have attached in your last mail.
many thanks
Tito
On 4/22/18 3:52 PM, Jörg Knobloch wrote:
> Hi fine friends of Thunderbird and people with fast processors, SSDs and
> at least 4 GB of RAM ;-)
>
> If you want to continue compiling your favourite application locally,
> please consider switching to "M-C as top source directory". People doing
> so are no longer the avant-garde; things have changed and people
> compiling with C-C as top source directory will no longer be supported
> and things will stop working for them. On Windows, they already get a
> build warnings and, unless I missed something, some Xpcshell tests don't
> run locally any more.
>
> So let's compare old and new.
>
> Old:
> You checked out C-C, in there, you created a directory "mozilla" and
> checked out M-C.
> Your .mozconfig had |ac_add_options --enable-application=mail|.
> You could refresh your local repositories with |python client.py checkout|.
> To build, you used |mozilla/mach build|.
> To run Xpcshell tests |mozilla/mach xpcshell-test
> mailnews/base/test/unit/test_autoconfigFetchDisk.js|.
> To run Mozmill tests (from the obj dir) |mozmake
> SOLO_TEST=newmailaccount/test-newmailaccount.js mozmill-one|.
>
> New:
> You check out M-C, in there, you create a directory "comm" and check out
> C-C (see below).
> Your .mozconfig needs |ac_add_options --enable-application=comm/mail|.
> |python client.py checkout| does not work any more, you need to use |hg
> pull -u| twice.
> To build, use |mach build|.
> To run Xpcshell tests |mach xpcshell-test
> comm/mailnews/base/test/unit/test_autoconfigFetchDisk.js|.
> Running Mozmill tests hasn't changed.
>
> Of course, to switch from the old setup to the new, you don't need to
> checkout fresh copies. You can just shuffle files around. The object
> directory will now sit as a sibling next to "comm". So delete the
> previous object directory before moving things.
>
> I attach a picture of the new setup.
>
> Jörg.
>
> P.S.:
> https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Build_Instructions/Simple_Thunderbird_build
> is now sadly out of date :-(
>
>
> _______________________________________________
> Maildev mailing list
> Maildev@lists.thunderbird.net
> http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net
>
TP
Tom Prince
Tue, May 1, 2018 8:52 PM
You need to checkout https://hg.mozilla.org/comm-central into a directory
called comm inside the mozilla-central checkout. (This is flipped from the
old layout, which had mozilla-central checked out as a subdirectory of
comm-central).
On Tue, May 1, 2018 at 2:28 PM Tito f.disclosure@gmail.com wrote:
Hallo Jörg,
Could you please also share the Mozilla central repository link that you
have used? I have tried this one
https://hg.mozilla.org/mozilla-central/
but i do not see the comm directory there? Or have i overlooked
something? I.e. from the png picture you have attached in your last mail.
many thanks
Tito
On 4/22/18 3:52 PM, Jörg Knobloch wrote:
Hi fine friends of Thunderbird and people with fast processors, SSDs and
at least 4 GB of RAM ;-)
If you want to continue compiling your favourite application locally,
please consider switching to "M-C as top source directory". People doing
so are no longer the avant-garde; things have changed and people
compiling with C-C as top source directory will no longer be supported
and things will stop working for them. On Windows, they already get a
build warnings and, unless I missed something, some Xpcshell tests don't
run locally any more.
So let's compare old and new.
Old:
You checked out C-C, in there, you created a directory "mozilla" and
checked out M-C.
Your .mozconfig had |ac_add_options --enable-application=mail|.
You could refresh your local repositories with |python client.py
To build, you used |mozilla/mach build|.
To run Xpcshell tests |mozilla/mach xpcshell-test
mailnews/base/test/unit/test_autoconfigFetchDisk.js|.
To run Mozmill tests (from the obj dir) |mozmake
SOLO_TEST=newmailaccount/test-newmailaccount.js mozmill-one|.
New:
You check out M-C, in there, you create a directory "comm" and check out
C-C (see below).
Your .mozconfig needs |ac_add_options --enable-application=comm/mail|.
|python client.py checkout| does not work any more, you need to use |hg
pull -u| twice.
To build, use |mach build|.
To run Xpcshell tests |mach xpcshell-test
comm/mailnews/base/test/unit/test_autoconfigFetchDisk.js|.
Running Mozmill tests hasn't changed.
Of course, to switch from the old setup to the new, you don't need to
checkout fresh copies. You can just shuffle files around. The object
directory will now sit as a sibling next to "comm". So delete the
previous object directory before moving things.
I attach a picture of the new setup.
Jörg.
P.S.:
You need to checkout https://hg.mozilla.org/comm-central into a directory
called comm inside the mozilla-central checkout. (This is flipped from the
old layout, which had mozilla-central checked out as a subdirectory of
comm-central).
On Tue, May 1, 2018 at 2:28 PM Tito <f.disclosure@gmail.com> wrote:
>
> Hallo Jörg,
>
> Could you please also share the Mozilla central repository link that you
> have used? I have tried this one
>
> https://hg.mozilla.org/mozilla-central/
>
> but i do not see the comm directory there? Or have i overlooked
> something? I.e. from the png picture you have attached in your last mail.
>
> many thanks
>
> Tito
>
>
> On 4/22/18 3:52 PM, Jörg Knobloch wrote:
> > Hi fine friends of Thunderbird and people with fast processors, SSDs and
> > at least 4 GB of RAM ;-)
> >
> > If you want to continue compiling your favourite application locally,
> > please consider switching to "M-C as top source directory". People doing
> > so are no longer the avant-garde; things have changed and people
> > compiling with C-C as top source directory will no longer be supported
> > and things will stop working for them. On Windows, they already get a
> > build warnings and, unless I missed something, some Xpcshell tests don't
> > run locally any more.
> >
> > So let's compare old and new.
> >
> > Old:
> > You checked out C-C, in there, you created a directory "mozilla" and
> > checked out M-C.
> > Your .mozconfig had |ac_add_options --enable-application=mail|.
> > You could refresh your local repositories with |python client.py
> checkout|.
> > To build, you used |mozilla/mach build|.
> > To run Xpcshell tests |mozilla/mach xpcshell-test
> > mailnews/base/test/unit/test_autoconfigFetchDisk.js|.
> > To run Mozmill tests (from the obj dir) |mozmake
> > SOLO_TEST=newmailaccount/test-newmailaccount.js mozmill-one|.
> >
> > New:
> > You check out M-C, in there, you create a directory "comm" and check out
> > C-C (see below).
> > Your .mozconfig needs |ac_add_options --enable-application=comm/mail|.
> > |python client.py checkout| does not work any more, you need to use |hg
> > pull -u| twice.
> > To build, use |mach build|.
> > To run Xpcshell tests |mach xpcshell-test
> > comm/mailnews/base/test/unit/test_autoconfigFetchDisk.js|.
> > Running Mozmill tests hasn't changed.
> >
> > Of course, to switch from the old setup to the new, you don't need to
> > checkout fresh copies. You can just shuffle files around. The object
> > directory will now sit as a sibling next to "comm". So delete the
> > previous object directory before moving things.
> >
> > I attach a picture of the new setup.
> >
> > Jörg.
> >
> > P.S.:
> >
> https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Build_Instructions/Simple_Thunderbird_build
> > is now sadly out of date :-(
> >
> >
> > _______________________________________________
> > Maildev mailing list
> > Maildev@lists.thunderbird.net
> >
> http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net
> >
>
>
> _______________________________________________
> Maildev mailing list
> Maildev@lists.thunderbird.net
> http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net
>
T
Tito
Wed, May 2, 2018 4:57 PM
Hello Tom, Jörg
many thanks works like a charm, i was able to build 61.0a1 (2018-05-02)
(64-bit) today without any issues the only think i notices which was
different with the last builds is the rust dependencies, those were not
required before.
On 5/1/18 10:52 PM, Tom Prince wrote:
You need to checkout https://hg.mozilla.org/comm-central into a
directory called comminside the mozilla-central checkout. (This is
flipped from the old layout, which had mozilla-central checked out as a
subdirectory of comm-central).
Hello Tom, Jörg
many thanks works like a charm, i was able to build 61.0a1 (2018-05-02)
(64-bit) today without any issues the only think i notices which was
different with the last builds is the rust dependencies, those were not
required before.
On 5/1/18 10:52 PM, Tom Prince wrote:
> You need to checkout https://hg.mozilla.org/comm-central into a
> directory called comminside the mozilla-central checkout. (This is
> flipped from the old layout, which had mozilla-central checked out as a
> subdirectory of comm-central).
>
BB
Ben Bucksch
Mon, May 7, 2018 9:03 PM
Jörg Knobloch wrote on 22.04.18 15:52:
Could somebody adapt this, please?
And also the build scripts like client.py?
Whoever made the code change is also on the hook or adapting the
documentation :)
Ben
Jörg Knobloch wrote on 22.04.18 15:52:
> P.S.:
> https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Build_Instructions/Simple_Thunderbird_build
> is now sadly out of date :-(
Could somebody adapt this, please?
And also the build scripts like client.py?
Whoever made the code change is also on the hook or adapting the
documentation :)
Ben
BB
Ben Bucksch
Wed, May 9, 2018 8:22 PM
Ben Bucksch wrote on 07.05.18 23:03:
Jörg Knobloch wrote on 22.04.18 15:52:
Could somebody adapt this, please?
And also the build scripts like client.py?
Whoever made the code change is also on the hook or adapting the
documentation :)
I've adapted the build docs now. I'd appreciate, if somebody could
double-check them.
I really do think that such changes that affect so many people should a)
be discussed here first, and b) must come with documentation, that
should be a check-in requirement.
Ben
Ben Bucksch wrote on 07.05.18 23:03:
> Jörg Knobloch wrote on 22.04.18 15:52:
>> P.S.:
>> https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Build_Instructions/Simple_Thunderbird_build
>> is now sadly out of date :-(
>
>
> Could somebody adapt this, please?
>
> And also the build scripts like client.py?
>
> Whoever made the code change is also on the hook or adapting the
> documentation :)
I've adapted the build docs now. I'd appreciate, if somebody could
double-check them.
I really do think that such changes that affect so many people should a)
be discussed here first, and b) must come with documentation, that
should be a check-in requirement.
Ben
PC
Patrick Cloke
Thu, May 10, 2018 7:12 PM
If |python client.py checkout| does not work anymore, is there any
reason to keep it in the tree?
--Patrick
On 4/22/18 9:52 AM, Jörg Knobloch wrote:
Hi fine friends of Thunderbird and people with fast processors, SSDs
and at least 4 GB of RAM ;-)
If you want to continue compiling your favourite application locally,
please consider switching to "M-C as top source directory". People
doing so are no longer the avant-garde; things have changed and people
compiling with C-C as top source directory will no longer be supported
and things will stop working for them. On Windows, they already get a
build warnings and, unless I missed something, some Xpcshell tests
don't run locally any more.
So let's compare old and new.
Old:
You checked out C-C, in there, you created a directory "mozilla" and
checked out M-C.
Your .mozconfig had |ac_add_options --enable-application=mail|.
You could refresh your local repositories with |python client.py
checkout|.
To build, you used |mozilla/mach build|.
To run Xpcshell tests |mozilla/mach xpcshell-test
mailnews/base/test/unit/test_autoconfigFetchDisk.js|.
To run Mozmill tests (from the obj dir) |mozmake
SOLO_TEST=newmailaccount/test-newmailaccount.js mozmill-one|.
New:
You check out M-C, in there, you create a directory "comm" and check
out C-C (see below).
Your .mozconfig needs |ac_add_options --enable-application=comm/mail|.
|python client.py checkout| does not work any more, you need to use
|hg pull -u| twice.
To build, use |mach build|.
To run Xpcshell tests |mach xpcshell-test
comm/mailnews/base/test/unit/test_autoconfigFetchDisk.js|.
Running Mozmill tests hasn't changed.
Of course, to switch from the old setup to the new, you don't need to
checkout fresh copies. You can just shuffle files around. The object
directory will now sit as a sibling next to "comm". So delete the
previous object directory before moving things.
I attach a picture of the new setup.
Jörg.
P.S.:
https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Build_Instructions/Simple_Thunderbird_build
is now sadly out of date :-(
Maildev mailing list
Maildev@lists.thunderbird.net
http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net
If |python client.py checkout| does not work anymore, is there any
reason to keep it in the tree?
--Patrick
On 4/22/18 9:52 AM, Jörg Knobloch wrote:
> Hi fine friends of Thunderbird and people with fast processors, SSDs
> and at least 4 GB of RAM ;-)
>
> If you want to continue compiling your favourite application locally,
> please consider switching to "M-C as top source directory". People
> doing so are no longer the avant-garde; things have changed and people
> compiling with C-C as top source directory will no longer be supported
> and things will stop working for them. On Windows, they already get a
> build warnings and, unless I missed something, some Xpcshell tests
> don't run locally any more.
>
> So let's compare old and new.
>
> Old:
> You checked out C-C, in there, you created a directory "mozilla" and
> checked out M-C.
> Your .mozconfig had |ac_add_options --enable-application=mail|.
> You could refresh your local repositories with |python client.py
> checkout|.
> To build, you used |mozilla/mach build|.
> To run Xpcshell tests |mozilla/mach xpcshell-test
> mailnews/base/test/unit/test_autoconfigFetchDisk.js|.
> To run Mozmill tests (from the obj dir) |mozmake
> SOLO_TEST=newmailaccount/test-newmailaccount.js mozmill-one|.
>
> New:
> You check out M-C, in there, you create a directory "comm" and check
> out C-C (see below).
> Your .mozconfig needs |ac_add_options --enable-application=comm/mail|.
> |python client.py checkout| does not work any more, you need to use
> |hg pull -u| twice.
> To build, use |mach build|.
> To run Xpcshell tests |mach xpcshell-test
> comm/mailnews/base/test/unit/test_autoconfigFetchDisk.js|.
> Running Mozmill tests hasn't changed.
>
> Of course, to switch from the old setup to the new, you don't need to
> checkout fresh copies. You can just shuffle files around. The object
> directory will now sit as a sibling next to "comm". So delete the
> previous object directory before moving things.
>
> I attach a picture of the new setup.
>
> Jörg.
>
> P.S.:
> https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Build_Instructions/Simple_Thunderbird_build
> is now sadly out of date :-(
>
>
> _______________________________________________
> Maildev mailing list
> Maildev@lists.thunderbird.net
> http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net
MH
Matt Harris
Thu, May 10, 2018 10:20 PM
On 10-May-18 5:52 AM, Ben Bucksch wrote:
I really do think that such changes that affect so many people should
a) be discussed here first, and b) must come with documentation, that
should be a check-in requirement.
Ben
While not requiring discussion the same as a build change, I am looking
for some way to improve user facing documentation. Currently the release
notes appear to be about the only way to back track what changes.
Sadly even using release notes, the release release notes do not
contain a bug reference and the relevant tracking bug often mentions a
lot of bugs that did not make it into the release notes. Once located
the entire relevant bug must often be read to determine exactly what
changed and were. For a mature project with such involved build, as a
group we do not do very well in the non technical side of development.
Documenting change as it appears to the user. Surely we can automate
some form of notification of bugs with user facing change.
What is the answer? I have spent days trying to write a what is new for
Thunderbird 60. Each item on the list takes half an hour or more
depending on just how hard the bug is to locate and decipher.
Matt
On 10-May-18 5:52 AM, Ben Bucksch wrote:
>
> I really do think that such changes that affect so many people should
> a) be discussed here first, and b) must come with documentation, that
> should be a check-in requirement.
>
> Ben
While not requiring discussion the same as a build change, I am looking
for some way to improve user facing documentation. Currently the release
notes appear to be about the only way to back track what changes.
Sadly even using release notes, the release release notes do not
contain a bug reference and the relevant tracking bug often mentions a
lot of bugs that did not make it into the release notes. Once located
the entire relevant bug must often be read to determine exactly what
changed and were. For a mature project with such involved build, as a
group we do not do very well in the non technical side of development.
Documenting change as it appears to the user. Surely we can automate
some form of notification of bugs with user facing change.
What is the answer? I have spent days trying to write a what is new for
Thunderbird 60. Each item on the list takes half an hour or more
depending on just how hard the bug is to locate and decipher.
Matt
