From mhoye at mozilla.com  Mon Jan  5 15:54:28 2015
From: mhoye at mozilla.com (Mike Hoye)
Date: Mon, 05 Jan 2015 10:54:28 -0500
Subject: Documentation help wanted for specific topics
In-Reply-To: <67qdnY6iKdJDygXJnZ2dnUU7-TmdnZ2d@mozilla.org>
References: <67qdnY6iKdJDygXJnZ2dnUU7-TmdnZ2d@mozilla.org>
Message-ID: <54AAB3B4.2020009@mozilla.com>

On 2014-12-22 12:41 PM, Gervase Markham wrote:
> There are some bits of Bugzilla which are not well documented at the
> moment, because I (and often other Bugzilla devs) do not have much
> experience with them. In particular, this includes:
>
> * Installing on Windows
> * Installing on Mac OS
> * Oracle
> * email_in.pl (incoming email gateway)
> * LDAP authentication
> * RADIUS authentication
> * Groups
>
> If you know something, anything at all, about those bits of Bugzilla,
> please drop me an email.

Do we have a page enumerating these shortcomings - a bug or not, could 
be anything - that I can point potential contributors at?


- mhoye
_______________________________________________
dev-apps-bugzilla mailing list
dev-apps-bugzilla at lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-apps-bugzilla


From marshall.sweng at gmail.com  Mon Jan  5 17:35:45 2015
From: marshall.sweng at gmail.com (Marshall SwEng)
Date: Mon, 5 Jan 2015 12:35:45 -0500
Subject: Documentation help wanted for specific topics
In-Reply-To: <54AAB3B4.2020009@mozilla.com>
References: <67qdnY6iKdJDygXJnZ2dnUU7-TmdnZ2d@mozilla.org> <54AAB3B4.2020009@mozilla.com>
Message-ID: <CAAKcVq1yk4fuJb+bropdcz401PdYRQDHuMfcfXijLAVqBrjAqQ@mail.gmail.com>

Hey Mike,

The "page enumerating these shortcomings" IMHO, would be found at:
https://bugzilla.mozilla.org/buglist.cgi?product=Bugzilla&component=Documentation&resolution=---
I say this by following this trail starting at http://www.bugzilla.org/docs/
1.  "Interested in helping to improve Bugzilla's documentation? See
our Bugzilla
Documentor's Guide <http://www.bugzilla.org/docs/documentor.html>."
2.  "Finding where we need help
<http://www.bugzilla.org/docs/documentor.html#finding-where>"
3.  "Lists of documentation bugs:

   - Open bugs in the Documentation Component
   <https://bugzilla.mozilla.org/buglist.cgi?product=Bugzilla&component=Documentation&resolution=--->
   "

Gervase,
I have experience installing and configuring Bugzilla 4.4 on Windows 2008
R2 SP1 using IIS 7.5.7600.  We use LDAP, so I _may_ be able to provide some
feedback there as well.  E.g. bug 922845.

I usually keep very good notes during _all_ installations.  But, it's been
a while.  So our current settings have probably drifted from my initial
notes.

That being said, my manager recently gave me permission to contribute to
open source projects.  Time permitting of course.  I'm new to this list,
but I feel I can add some documentation.  At the very least I can give
feedback on my personal experiences.

--
Marshall

On Mon, Jan 5, 2015 at 10:54 AM, Mike Hoye <mhoye at mozilla.com> wrote:

> On 2014-12-22 12:41 PM, Gervase Markham wrote:
>
>> There are some bits of Bugzilla which are not well documented at the
>> moment, because I (and often other Bugzilla devs) do not have much
>> experience with them. In particular, this includes:
>>
>> * Installing on Windows
>> * Installing on Mac OS
>> * Oracle
>> * email_in.pl (incoming email gateway)
>> * LDAP authentication
>> * RADIUS authentication
>> * Groups
>>
>> If you know something, anything at all, about those bits of Bugzilla,
>> please drop me an email.
>>
>
> Do we have a page enumerating these shortcomings - a bug or not, could be
> anything - that I can point potential contributors at?
>
>
> - mhoye
> _______________________________________________
> dev-apps-bugzilla mailing list
> dev-apps-bugzilla at lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-apps-bugzilla
> -
> To view or change your list settings, click here:
> <http://bugzilla.org/cgi-bin/mj_wwwusr?user=Marshall.SwEng+
> Mozilla at gmail.com>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bugzilla.org/pipermail/developers/attachments/20150105/a333e683/attachment.html>

From jochen.wiedmann at gmail.com  Wed Jan 14 09:23:39 2015
From: jochen.wiedmann at gmail.com (Jochen Wiedmann)
Date: Wed, 14 Jan 2015 10:23:39 +0100
Subject: Documentation help wanted for specific topics
In-Reply-To: <5499727B.4000904@mozilla.org>
References: <67qdnY6iKdJDygXJnZ2dnUU7-TmdnZ2d@mozilla.org> <CAF8HOZLd=LAY4u=SMcT88VctU1mq0noOGTUc1iw_ejjQWEKSgg@mail.gmail.com>
 <5499727B.4000904@mozilla.org>
Message-ID: <CAF8HOZJt_iwefJSKo5f5bnL_uGuMJ8tD_hg39f_OZW8nQbyhTA@mail.gmail.com>

Hi,

for your info: I had to install Bugzilla on Windows these days and am
running into problems as soon as testing the installed Bugzilla. (More
precisely, I get an HTTP error code 403.)

Some digging in the web suggests that my fault could be to use Apache
2.4, rather than 2.2 (the authorization stuff has changed quite a bit,
although I have mod_access_compat loaded).

Is anyone out there who might be able to help with that?

Thanks,

Jochen


On Tue, Dec 23, 2014 at 2:47 PM, Gervase Markham <gerv at mozilla.org> wrote:
> On 22/12/14 18:53, Jochen Wiedmann wrote:
>> I pride myself to have some experience with installation on Windows.
>
> Wonderful :-) Might you be able to check over our Windows installation
> documentation here:
> http://bugzilla.readthedocs.org/en/latest/installing/windows.html
> and give us your feedback? (Also the sub-pages about IIS and about
> Apache on Windows.) You are welcome to submit patches, or file bugs, or
> email me with suggestions, whatever's easiest for you.
>
> I would like to have enough confidence in these Windows docs to take the
> disclaimer off the top.
>
> Gerv
> -
> To view or change your list settings, click here:
> <http://bugzilla.org/cgi-bin/mj_wwwusr?user=jochen.wiedmann at gmail.com>



-- 
Our time is just a point along a line that runs forever with no end.
(Al Stewart, Lord Grenville)


From jochen.wiedmann at gmail.com  Wed Jan 14 12:31:01 2015
From: jochen.wiedmann at gmail.com (Jochen Wiedmann)
Date: Wed, 14 Jan 2015 13:31:01 +0100
Subject: Documentation help wanted for specific topics
In-Reply-To: <CAF8HOZJt_iwefJSKo5f5bnL_uGuMJ8tD_hg39f_OZW8nQbyhTA@mail.gmail.com>
References: <67qdnY6iKdJDygXJnZ2dnUU7-TmdnZ2d@mozilla.org> <CAF8HOZLd=LAY4u=SMcT88VctU1mq0noOGTUc1iw_ejjQWEKSgg@mail.gmail.com>
 <5499727B.4000904@mozilla.org> <CAF8HOZJt_iwefJSKo5f5bnL_uGuMJ8tD_hg39f_OZW8nQbyhTA@mail.gmail.com>
Message-ID: <CAF8HOZJVu=1BWYjUo+1tHC-vavZdtXor7jDRvWm3Hu5jr+H+QA@mail.gmail.com>

Okay, succeeded by using Apache 2.2.

I suggest to add the following to the Windows installation docs.

1.) Do *not* use Apache HTTPD 2.4. Use 2.2 instead. (This might apply
to all platforms, btw.)
2.) Do *not* use Strawberry Perl, unless you really know what you are doing.
     Despite a lot of efforts by the Strawberry Maintainers, there are still
     glitches when installing modules, in particular for DBD::mysql. (For
     example, mysqladmin.exe *must* be in the path.
3.) The updated list of modules to install via PPM:

  ppm install AppConfig TimeDate DateTime DateTime-TimeZone DBI
DBD-mysql Template-Toolkit
  ppm install MailTools GD Chart GDGraph Net-LDAP-Express Email-Reply
Email-Send Math-Random-ISAAC
  ppm install Template-GD MIME-tools XML-Twig PatchReader
  ppm install Authen-SASL Net-SMTP-SSL Authen-Radius JSON-RPC JSON-XS Test-Taint
  ppm install HTML-Scrubber Encode-Detect HTML-FormatText-WithLinks
  ppm install File-Slurp IO-stringy

    Note, that ppm is happily installing multiple modules in one execution.


Jochen


On Wed, Jan 14, 2015 at 10:23 AM, Jochen Wiedmann
<jochen.wiedmann at gmail.com> wrote:
> Hi,
>
> for your info: I had to install Bugzilla on Windows these days and am
> running into problems as soon as testing the installed Bugzilla. (More
> precisely, I get an HTTP error code 403.)
>
> Some digging in the web suggests that my fault could be to use Apache
> 2.4, rather than 2.2 (the authorization stuff has changed quite a bit,
> although I have mod_access_compat loaded).
>
> Is anyone out there who might be able to help with that?
>
> Thanks,
>
> Jochen
>
>
> On Tue, Dec 23, 2014 at 2:47 PM, Gervase Markham <gerv at mozilla.org> wrote:
>> On 22/12/14 18:53, Jochen Wiedmann wrote:
>>> I pride myself to have some experience with installation on Windows.
>>
>> Wonderful :-) Might you be able to check over our Windows installation
>> documentation here:
>> http://bugzilla.readthedocs.org/en/latest/installing/windows.html
>> and give us your feedback? (Also the sub-pages about IIS and about
>> Apache on Windows.) You are welcome to submit patches, or file bugs, or
>> email me with suggestions, whatever's easiest for you.
>>
>> I would like to have enough confidence in these Windows docs to take the
>> disclaimer off the top.
>>
>> Gerv
>> -
>> To view or change your list settings, click here:
>> <http://bugzilla.org/cgi-bin/mj_wwwusr?user=jochen.wiedmann at gmail.com>
>
>
>
> --
> Our time is just a point along a line that runs forever with no end.
> (Al Stewart, Lord Grenville)



-- 
Our time is just a point along a line that runs forever with no end.
(Al Stewart, Lord Grenville)


From michiel.beijen at gmail.com  Wed Jan 14 12:55:54 2015
From: michiel.beijen at gmail.com (Michiel Beijen)
Date: Wed, 14 Jan 2015 13:55:54 +0100
Subject: Documentation help wanted for specific topics
In-Reply-To: <CAF8HOZJVu=1BWYjUo+1tHC-vavZdtXor7jDRvWm3Hu5jr+H+QA@mail.gmail.com>
References: <67qdnY6iKdJDygXJnZ2dnUU7-TmdnZ2d@mozilla.org> <CAF8HOZLd=LAY4u=SMcT88VctU1mq0noOGTUc1iw_ejjQWEKSgg@mail.gmail.com>
 <5499727B.4000904@mozilla.org> <CAF8HOZJt_iwefJSKo5f5bnL_uGuMJ8tD_hg39f_OZW8nQbyhTA@mail.gmail.com>
 <CAF8HOZJVu=1BWYjUo+1tHC-vavZdtXor7jDRvWm3Hu5jr+H+QA@mail.gmail.com>
Message-ID: <CABD0r11WGUQnEWJ0T7uf5ARdiHuVo0_1PbvQYrKTRS4LrdngTw@mail.gmail.com>

Hi Jochen,

On Wed, Jan 14, 2015 at 1:31 PM, Jochen Wiedmann
<jochen.wiedmann at gmail.com> wrote:
> Okay, succeeded by using Apache 2.2.
>
> I suggest to add the following to the Windows installation docs.
>
> 1.) Do *not* use Apache HTTPD 2.4. Use 2.2 instead. (This might apply
> to all platforms, btw.)

It might be a good idea if Bugzilla would provide one configuration
file that would be applicable for both 2.2 and 2.4 versions of the
product. OTRS also has this and it works quite nicely:
https://github.com/OTRS/otrs/blob/rel-4_0/scripts/apache2-httpd.include.conf

Of course for now probably using 2.2 would just be simpler. But Linux
distributions like CentOS 7 also have Apache 2.4 so it would be great
if the configuration would support it.

> 2.) Do *not* use Strawberry Perl, unless you really know what you are doing.
>      Despite a lot of efforts by the Strawberry Maintainers, there are still
>      glitches when installing modules, in particular for DBD::mysql. (For
>      example, mysqladmin.exe *must* be in the path.

Why do you install DBD::mysql on Strawberry? Since I guess Strawberry
Perl 5.10 years ago, it's been bundled by default. Strawberry Perl
does not support the binary packages (ppm) that ActiveState perl does.
But apart from that its build environment works well and is similar to
ActiveState. ActiveStates PPM repos are shut down after a while, for
instance if you'd have an ActiveState perl 5.14 installation a while
ago, right now you can not use PPM anymore unless you get a support
contract; or if you uninstall perl and install 5.20 or so.


Apart from that you can simply install stuff by typing 'cpan DateTime
File::Slurp' et cetera, or use cpanm if you want.
--
Mike


From jochen.wiedmann at gmail.com  Wed Jan 14 13:07:28 2015
From: jochen.wiedmann at gmail.com (Jochen Wiedmann)
Date: Wed, 14 Jan 2015 14:07:28 +0100
Subject: Documentation help wanted for specific topics
In-Reply-To: <CABD0r11WGUQnEWJ0T7uf5ARdiHuVo0_1PbvQYrKTRS4LrdngTw@mail.gmail.com>
References: <67qdnY6iKdJDygXJnZ2dnUU7-TmdnZ2d@mozilla.org> <CAF8HOZLd=LAY4u=SMcT88VctU1mq0noOGTUc1iw_ejjQWEKSgg@mail.gmail.com>
 <5499727B.4000904@mozilla.org> <CAF8HOZJt_iwefJSKo5f5bnL_uGuMJ8tD_hg39f_OZW8nQbyhTA@mail.gmail.com>
 <CAF8HOZJVu=1BWYjUo+1tHC-vavZdtXor7jDRvWm3Hu5jr+H+QA@mail.gmail.com> <CABD0r11WGUQnEWJ0T7uf5ARdiHuVo0_1PbvQYrKTRS4LrdngTw@mail.gmail.com>
Message-ID: <CAF8HOZLamyATwjzZLcbbkZnb5Jau+tpzRvcqeiphCnMCi8fxqQ@mail.gmail.com>

On Wed, Jan 14, 2015 at 1:55 PM, Michiel Beijen
<michiel.beijen at gmail.com> wrote:

> It might be a good idea if Bugzilla would provide one configuration
> file that would be applicable for both 2.2 and 2.4 versions of the
> product. OTRS also has this and it works quite nicely:
> https://github.com/OTRS/otrs/blob/rel-4_0/scripts/apache2-httpd.include.conf

It is not as simple as that. For example, there are also the .htaccess
files, as generated by checksetup.pl.

> Why do you install DBD::mysql on Strawberry? Since I guess Strawberry
> Perl 5.10 years ago, it's been bundled by default.

Have to admit, I missed that. Probably worth another try.


Jochen


From lpsolit at gmail.com  Wed Jan 14 16:40:23 2015
From: lpsolit at gmail.com (=?UTF-8?B?RnLDqWTDqXJpYyBCdWNsaW4=?=)
Date: Wed, 14 Jan 2015 17:40:23 +0100
Subject: Documentation help wanted for specific topics
In-Reply-To: <CAF8HOZJVu=1BWYjUo+1tHC-vavZdtXor7jDRvWm3Hu5jr+H+QA@mail.gmail.com>
References: <67qdnY6iKdJDygXJnZ2dnUU7-TmdnZ2d@mozilla.org> <CAF8HOZLd=LAY4u=SMcT88VctU1mq0noOGTUc1iw_ejjQWEKSgg@mail.gmail.com> <5499727B.4000904@mozilla.org> <CAF8HOZJt_iwefJSKo5f5bnL_uGuMJ8tD_hg39f_OZW8nQbyhTA@mail.gmail.com> <CAF8HOZJVu=1BWYjUo+1tHC-vavZdtXor7jDRvWm3Hu5jr+H+QA@mail.gmail.com>
Message-ID: <54B69BF7.708@gmail.com>

Le 14. 01. 15 13:31, Jochen Wiedmann a ?crit :
> 1.) Do *not* use Apache HTTPD 2.4. Use 2.2 instead. (This might apply
> to all platforms, btw.)

I use Apache HTTPD 2.4 with Bugzilla for a very long time without any
problem.

LpSolit



From theycallmefish at gmail.com  Wed Jan 14 18:17:47 2015
From: theycallmefish at gmail.com (Ryan Wilson)
Date: Wed, 14 Jan 2015 18:17:47 +0000
Subject: Documentation help wanted for specific topics
References: <67qdnY6iKdJDygXJnZ2dnUU7-TmdnZ2d@mozilla.org> <CAF8HOZLd=LAY4u=SMcT88VctU1mq0noOGTUc1iw_ejjQWEKSgg@mail.gmail.com>
 <5499727B.4000904@mozilla.org> <CAF8HOZJt_iwefJSKo5f5bnL_uGuMJ8tD_hg39f_OZW8nQbyhTA@mail.gmail.com>
 <CAF8HOZJVu=1BWYjUo+1tHC-vavZdtXor7jDRvWm3Hu5jr+H+QA@mail.gmail.com> <54B69BF7.708@gmail.com>
Message-ID: <CACS7coKU1ZnQyj6xSQPpH6j=OUis8TbH7XJi3nfYeZiHuZZJHg@mail.gmail.com>

I have as well. I've had some additional customizations to my installation,
but nothing this document couldn't fix.

http://httpd.apache.org/docs/2.4/upgrading.html

On Wed Jan 14 2015 at 9:41:30 AM Fr?d?ric Buclin <lpsolit at gmail.com> wrote:

> Le 14. 01. 15 13:31, Jochen Wiedmann a ?crit :
> > 1.) Do *not* use Apache HTTPD 2.4. Use 2.2 instead. (This might apply
> > to all platforms, btw.)
>
> I use Apache HTTPD 2.4 with Bugzilla for a very long time without any
> problem.
>
> LpSolit
>
> -
> To view or change your list settings, click here:
> <http://bugzilla.org/cgi-bin/mj_wwwusr?user=theycallmefish at gmail.com>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bugzilla.org/pipermail/developers/attachments/20150114/d8ebe38c/attachment.html>

From mcote at bugzilla.org  Thu Jan 15 18:26:04 2015
From: mcote at bugzilla.org (=?UTF-8?B?TWFyayBDw7R0w6k=?=)
Date: Thu, 15 Jan 2015 13:26:04 -0500
Subject: Release notes for future versions
Message-ID: <T6mdnYer_5mhmyXJnZ2dnUU7-VednZ2d@mozilla.org>

dkl has been chugging away at the release notes for 5.0rc1.  I would
like to remind all developers, reviewers, and approvers that any
significant change should be tagged with the "relnote" keyword.  Trying
to figure out what should go into the release notes is very tedious when
the keyword is regularly neglected.

Second, I'd like to propose an amendment to this process: rather than
waiting until the first release candidate, any change that requires a
relnote should have the relnote added before the bug is resolved.  This
will vastly speed up the release process, since the release manager
won't have to read through bug comments to get the gist of changes.  dkl
suggests using the User Story field, which makes sense to me, since the
release note is essentially a very brief summary of the change.

Finally, if someone is looking for a way to contribute to Bugzilla, I'm
sure dkl would appreciate help with future releases!  It's a perfect
opportunity to help out if you don't feel comfortable coding on Bugzilla.

Mark

-- 
Mark C?t?
Assistant Project Lead, Bugzilla
_______________________________________________
dev-apps-bugzilla mailing list
dev-apps-bugzilla at lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-apps-bugzilla

From lance.zimmerman at ubnt.com  Thu Jan 15 18:37:39 2015
From: lance.zimmerman at ubnt.com (Lance Zimmerman)
Date: Thu, 15 Jan 2015 10:37:39 -0800
Subject: Self-Introduction: Lance Zimmerman
Message-ID: <CAPaf3Ma2PdE+4sU88KMdZxSz7byAOWimUfetRMHECp6TBp6B7A@mail.gmail.com>

Hi,
My name is Lance Zimmerman. I live and work in San Jose, CA. I would like
to help out with contributing to Bugzilla. I have been working in software
build and test for the last 10 years, mostly with wireless network drivers.
Perl has been the primary test and script language used. I would rate my
current Perl skill level as medium or upper medium. I have experience with
various bug tracking and workflow systems on the user level. These include
Bugzilla, Extra View, Trac, Confluence, Jenkins, and JIRA.

Looking at the bugs marked good for newcomers, I thought *Bug 577958*
<https://bugzilla.mozilla.org/show_bug.cgi?id=577958> might be a good one
for me to start with.

Thanks,
Lance
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bugzilla.org/pipermail/developers/attachments/20150115/04a31329/attachment.html>

From mcote at bugzilla.org  Thu Jan 15 20:36:07 2015
From: mcote at bugzilla.org (=?UTF-8?B?TWFyayBDw7R0w6k=?=)
Date: Thu, 15 Jan 2015 15:36:07 -0500
Subject: Self-Introduction: Lance Zimmerman
In-Reply-To: <mailman.8339.1421347197.26608.dev-apps-bugzilla@lists.mozilla.org>
References: <mailman.8339.1421347197.26608.dev-apps-bugzilla@lists.mozilla.org>
Message-ID: <GaadnT58rL0quSXJnZ2dnUU7-budnZ2d@mozilla.org>

Hi Lance, welcome!  Always great to find more Perl hackers!

Yes, that bug is probably pretty simple.  Good luck!  And feel free to
drop into #bugzilla on irc.mozilla.org if you have questions.

Mark


On 2015-01-15 1:37 PM, Lance Zimmerman wrote:
> Hi,
> My name is Lance Zimmerman. I live and work in San Jose, CA. I would like
> to help out with contributing to Bugzilla. I have been working in software
> build and test for the last 10 years, mostly with wireless network drivers.
> Perl has been the primary test and script language used. I would rate my
> current Perl skill level as medium or upper medium. I have experience with
> various bug tracking and workflow systems on the user level. These include
> Bugzilla, Extra View, Trac, Confluence, Jenkins, and JIRA.
> 
> Looking at the bugs marked good for newcomers, I thought *Bug 577958*
> <https://bugzilla.mozilla.org/show_bug.cgi?id=577958> might be a good one
> for me to start with.
> 
> Thanks,
> Lance
> 


-- 
Mark C?t?
Assistant Project Lead, Bugzilla
_______________________________________________
dev-apps-bugzilla mailing list
dev-apps-bugzilla at lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-apps-bugzilla

From gerv at mozilla.org  Fri Jan 16 10:49:36 2015
From: gerv at mozilla.org (Gervase Markham)
Date: Fri, 16 Jan 2015 10:49:36 +0000
Subject: Release notes for future versions
In-Reply-To: <T6mdnYer_5mhmyXJnZ2dnUU7-VednZ2d@mozilla.org>
References: <T6mdnYer_5mhmyXJnZ2dnUU7-VednZ2d@mozilla.org>
Message-ID: <54B8ECC0.8030306@mozilla.org>

Hi,

On 15/01/15 18:26, Mark C?t? wrote:
> dkl has been chugging away at the release notes for 5.0rc1.  I would
> like to remind all developers, reviewers, and approvers that any
> significant change should be tagged with the "relnote" keyword.  Trying
> to figure out what should go into the release notes is very tedious when
> the keyword is regularly neglected.
> 
> Second, I'd like to propose an amendment to this process: rather than

Can I counter-propose a different amendment?

We should keep the release notes in the docs/ folder as reST, and
require the patch to contain a patch to the release notes if it's
release-noteworthy. This means all the work is done at the time of patch
submission. The release manager has the option of trimming down the list
(and so we can err on the side of inclusion when considering whether
bugs are note-worthy), but won't need to go and seek information to add
it. So it would make their job easier.

Gerv


From lpsolit at gmail.com  Fri Jan 16 18:10:01 2015
From: lpsolit at gmail.com (=?UTF-8?B?RnLDqWTDqXJpYyBCdWNsaW4=?=)
Date: Fri, 16 Jan 2015 19:10:01 +0100
Subject: Release notes for future versions
In-Reply-To: <54B8ECC0.8030306@mozilla.org>
References: <T6mdnYer_5mhmyXJnZ2dnUU7-VednZ2d@mozilla.org> <54B8ECC0.8030306@mozilla.org>
Message-ID: <54B953F9.9000105@gmail.com>

Le 16. 01. 15 11:49, Gervase Markham a ?crit :
> We should keep the release notes in the docs/ folder as reST, and

I disagree. This requires to compile the docs to read them. I think it's
much easier to simply have an HTML page as we do currently.


> require the patch to contain a patch to the release notes if it's
> release-noteworthy. This means all the work is done at the time of patch
> submission.

I disagree here too. It's not the job of the contributor to decide what
should be relnoted and what shouldn't. And even if we say this should be
relnoted, it's not his job to follow our guidelines to document new
features. Also, some features require several bugs to be fully
implemented. It's much easier to relnote relevant information once the
whole feature is implemented. And so it's easier to do this after all
the related bugs have been fixed. And it's already hard enough to find
contributors, so please don't ask them to do more.

I made another proposal on IRC yesterday. The idea is to still add the
'relnote' keyword as we always did, but we update release notes for each
development release instead of waiting for rc1. The bug list between two
consecutive dev releases is not that big. And we have a better idea of
what is important and what is pretty minor.


LpSolit



From gerv at mozilla.org  Wed Jan 21 14:35:20 2015
From: gerv at mozilla.org (Gervase Markham)
Date: Wed, 21 Jan 2015 14:35:20 +0000
Subject: Release notes for future versions
In-Reply-To: <mailman.8616.1421431951.26609.dev-apps-bugzilla@lists.mozilla.org>
References: <T6mdnYer_5mhmyXJnZ2dnUU7-VednZ2d@mozilla.org>	<54B8ECC0.8030306@mozilla.org> <mailman.8616.1421431951.26609.dev-apps-bugzilla@lists.mozilla.org>
Message-ID: <54BFB928.1080006@mozilla.org>

On 16/01/15 18:10, Fr?d?ric Buclin wrote:
> I disagree. This requires to compile the docs to read them.

No, because there will be a copy on bugzilla.readthedocs.org.

>> require the patch to contain a patch to the release notes if it's
>> release-noteworthy. This means all the work is done at the time of patch
>> submission.
> 
> I disagree here too. It's not the job of the contributor to decide what
> should be relnoted and what shouldn't. 

Well, the contributor in collaboration with their reviewer.

Who adds the relnote keyword at the moment?

> I made another proposal on IRC yesterday. The idea is to still add the
> 'relnote' keyword as we always did, but we update release notes for each
> development release instead of waiting for rc1. The bug list between two
> consecutive dev releases is not that big. And we have a better idea of
> what is important and what is pretty minor.

I like that idea. :-) That may well help.

Gerv




From gerv at mozilla.org  Wed Jan 21 14:58:10 2015
From: gerv at mozilla.org (Gervase Markham)
Date: Wed, 21 Jan 2015 14:58:10 +0000
Subject: Documentation help wanted for specific topics
In-Reply-To: <mailman.7337.1420479534.26608.dev-apps-bugzilla@lists.mozilla.org>
References: <67qdnY6iKdJDygXJnZ2dnUU7-TmdnZ2d@mozilla.org>	<54AAB3B4.2020009@mozilla.com>
	<mailman.7337.1420479534.26608.dev-apps-bugzilla@lists.mozilla.org>
Message-ID: <DY-dnejOLsEeIyLJnZ2dnUU7-TOdnZ2d@mozilla.org>

On 05/01/15 17:35, Marshall SwEng wrote:
> 1.  "Interested in helping to improve Bugzilla's documentation? See
> our Bugzilla
> Documentor's Guide <http://www.bugzilla.org/docs/documentor.html>."

Wow, that file is really wrong :-(

Do we need a specific Documenter's Guide? If not, we should remove it.
Note that the new reST docs do have a "style.rst":
http://bugzilla.readthedocs.org/en/latest/style.html

> I have experience installing and configuring Bugzilla 4.4 on Windows 2008
> R2 SP1 using IIS 7.5.7600.  We use LDAP, so I _may_ be able to provide some
> feedback there as well.  E.g. bug 922845.

Input on that bug would be great.

I guess what would be most awesome would be for someone to read e.g. the
Windows install docs or the LDAP docs and either say "those are complete
and accurate to the best of my knowledge" or "here is a patch to make
them complete and accurate to the best of my knowledge".

Things short of that, such as specific patches, are good too, but that's
the optimum.

> I usually keep very good notes during _all_ installations.  But, it's been
> a while.  So our current settings have probably drifted from my initial
> notes.

Still, I'm sure this data would be very useful.

> That being said, my manager recently gave me permission to contribute to
> open source projects.  Time permitting of course.  I'm new to this list,
> but I feel I can add some documentation.  At the very least I can give
> feedback on my personal experiences.

Welcome on board! :-)

Gerv

_______________________________________________
dev-apps-bugzilla mailing list
dev-apps-bugzilla at lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-apps-bugzilla


From gerv at mozilla.org  Wed Jan 21 14:59:16 2015
From: gerv at mozilla.org (Gervase Markham)
Date: Wed, 21 Jan 2015 14:59:16 +0000
Subject: Documentation help wanted for specific topics
In-Reply-To: <mailman.8182.1421253748.26608.dev-apps-bugzilla@lists.mozilla.org>
References: <67qdnY6iKdJDygXJnZ2dnUU7-TmdnZ2d@mozilla.org>	<CAF8HOZLd=LAY4u=SMcT88VctU1mq0noOGTUc1iw_ejjQWEKSgg@mail.gmail.com>	<5499727B.4000904@mozilla.org>	<CAF8HOZJt_iwefJSKo5f5bnL_uGuMJ8tD_hg39f_OZW8nQbyhTA@mail.gmail.com>	<CAF8HOZJVu=1BWYjUo+1tHC-vavZdtXor7jDRvWm3Hu5jr+H+QA@mail.gmail.com>
	<mailman.8182.1421253748.26608.dev-apps-bugzilla@lists.mozilla.org>
Message-ID: <DY-dnevOLsFZIyLJnZ2dnUU7-TOdnZ2d@mozilla.org>

On 14/01/15 16:40, Fr?d?ric Buclin wrote:
> I use Apache HTTPD 2.4 with Bugzilla for a very long time without any
> problem.

It may well be that the Linux description of the config works with 2.4,
but the Windows one has not been updated.

Gerv

_______________________________________________
dev-apps-bugzilla mailing list
dev-apps-bugzilla at lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-apps-bugzilla

From gerv at mozilla.org  Wed Jan 21 14:59:49 2015
From: gerv at mozilla.org (Gervase Markham)
Date: Wed, 21 Jan 2015 14:59:49 +0000
Subject: Documentation help wanted for specific topics
In-Reply-To: <mailman.8200.1421259616.26608.dev-apps-bugzilla@lists.mozilla.org>
References: <67qdnY6iKdJDygXJnZ2dnUU7-TmdnZ2d@mozilla.org>	<CAF8HOZLd=LAY4u=SMcT88VctU1mq0noOGTUc1iw_ejjQWEKSgg@mail.gmail.com>	<5499727B.4000904@mozilla.org>	<CAF8HOZJt_iwefJSKo5f5bnL_uGuMJ8tD_hg39f_OZW8nQbyhTA@mail.gmail.com>	<CAF8HOZJVu=1BWYjUo+1tHC-vavZdtXor7jDRvWm3Hu5jr+H+QA@mail.gmail.com>	<54B69BF7.708@gmail.com>
	<mailman.8200.1421259616.26608.dev-apps-bugzilla@lists.mozilla.org>
Message-ID: <DY-dnerOLsF4IyLJnZ2dnUU7-TOdnZ2d@mozilla.org>

On 14/01/15 18:17, Ryan Wilson wrote:
> I have as well. I've had some additional customizations to my installation,
> but nothing this document couldn't fix.
> 
> http://httpd.apache.org/docs/2.4/upgrading.html

If the config in the Bugzilla docs doesn't work out of the box, we
should fix the docs. Does it?

Gerv

_______________________________________________
dev-apps-bugzilla mailing list
dev-apps-bugzilla at lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-apps-bugzilla


From gerv at mozilla.org  Wed Jan 21 15:01:42 2015
From: gerv at mozilla.org (Gervase Markham)
Date: Wed, 21 Jan 2015 15:01:42 +0000
Subject: Documentation help wanted for specific topics
In-Reply-To: <mailman.8147.1421238801.26608.dev-apps-bugzilla@lists.mozilla.org>
References: <67qdnY6iKdJDygXJnZ2dnUU7-TmdnZ2d@mozilla.org>	<CAF8HOZLd=LAY4u=SMcT88VctU1mq0noOGTUc1iw_ejjQWEKSgg@mail.gmail.com>	<5499727B.4000904@mozilla.org>	<CAF8HOZJt_iwefJSKo5f5bnL_uGuMJ8tD_hg39f_OZW8nQbyhTA@mail.gmail.com>
	<mailman.8147.1421238801.26608.dev-apps-bugzilla@lists.mozilla.org>
Message-ID: <DY-dneXOLsHKIiLJnZ2dnUU7-TMAAAAA@mozilla.org>

On 14/01/15 12:31, Jochen Wiedmann wrote:
> 1.) Do *not* use Apache HTTPD 2.4. Use 2.2 instead. (This might apply
> to all platforms, btw.)

I don't think we can recommend that, unless we have very good reasons. I
think the right fix here is to update our Windows docs to include a 2.4
config (or one which works everywhere).

> 3.) The updated list of modules to install via PPM:
> 
>   ppm install AppConfig TimeDate DateTime DateTime-TimeZone DBI
> DBD-mysql Template-Toolkit
>   ppm install MailTools GD Chart GDGraph Net-LDAP-Express Email-Reply
> Email-Send Math-Random-ISAAC
>   ppm install Template-GD MIME-tools XML-Twig PatchReader
>   ppm install Authen-SASL Net-SMTP-SSL Authen-Radius JSON-RPC JSON-XS Test-Taint
>   ppm install HTML-Scrubber Encode-Detect HTML-FormatText-WithLinks
>   ppm install File-Slurp IO-stringy

Can you turn this into a bug with a diff? :-)

Gerv

_______________________________________________
dev-apps-bugzilla mailing list
dev-apps-bugzilla at lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-apps-bugzilla


From gerv at mozilla.org  Wed Jan 21 15:03:47 2015
From: gerv at mozilla.org (Gervase Markham)
Date: Wed, 21 Jan 2015 15:03:47 +0000
Subject: bugzilla changelog pointing to BZR instead of GIT?
In-Reply-To: <mailman.7009.1419888009.26608.dev-apps-bugzilla@lists.mozilla.org>
References: <mailman.7009.1419888009.26608.dev-apps-bugzilla@lists.mozilla.org>
Message-ID: <DY-dneTOLsFOIiLJnZ2dnUU7-TOdnZ2d@mozilla.org>

On 29/12/14 21:17, Damien wrote:
> Half the links go to bonsai.mozilla.org while the other half goes to
> bzr.mozilla.org.
> If the CVS / BZR imports were all successful, and GIT is the source of
> truth, maybe
> someone can spend some cycles on fixing the changelog page.

Filed as https://bugzilla.mozilla.org/show_bug.cgi?id=1124194 .

Gerv

_______________________________________________
dev-apps-bugzilla mailing list
dev-apps-bugzilla at lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-apps-bugzilla


From lpsolit at gmail.com  Wed Jan 21 15:06:28 2015
From: lpsolit at gmail.com (=?windows-1252?Q?Fr=E9d=E9ric_Buclin?=)
Date: Wed, 21 Jan 2015 16:06:28 +0100
Subject: Documentation help wanted for specific topics
In-Reply-To: <DY-dnejOLsEeIyLJnZ2dnUU7-TOdnZ2d@mozilla.org>
References: <67qdnY6iKdJDygXJnZ2dnUU7-TmdnZ2d@mozilla.org>	<54AAB3B4.2020009@mozilla.com>	<mailman.7337.1420479534.26608.dev-apps-bugzilla@lists.mozilla.org> <DY-dnejOLsEeIyLJnZ2dnUU7-TOdnZ2d@mozilla.org>
Message-ID: <54BFC074.9040001@gmail.com>

Le 21. 01. 15 15:58, Gervase Markham a ?crit :
> Wow, that file is really wrong :-(
> 
> Do we need a specific Documenter's Guide? If not, we should remove it.


Kill it! If someone was still reading this page, he would have reported
that 2.20 is no longer supported. So just kill it!



From dkl at mozilla.com  Wed Jan 21 15:25:02 2015
From: dkl at mozilla.com (David Lawrence)
Date: Wed, 21 Jan 2015 10:25:02 -0500
Subject: Release notes for future versions
In-Reply-To: <54BFB928.1080006@mozilla.org>
References: <T6mdnYer_5mhmyXJnZ2dnUU7-VednZ2d@mozilla.org>	<54B8ECC0.8030306@mozilla.org> <mailman.8616.1421431951.26609.dev-apps-bugzilla@lists.mozilla.org> <54BFB928.1080006@mozilla.org>
Message-ID: <54BFC4CE.70204@mozilla.com>

My proposal for discussion for an updated release notes process

1) When a bug is approved for inclusion in a release, the approver decides if a release note
is warranted and adds the relnote keyword to the keywords field of the bug (happens more or less now).

2) The approver also sets the target milestone appropriately so the release manager will know which
release notes should contain the summary.

3) Once we are ready for a development snapshot to be made for the next release, the release
manager looks for all bugs targeted for that release and has the relnote keyword set. Also  a top level release
notes bug is created for tracking and to also contain the high level key points for the release which will be
reviewed separately.

4) The release manager goes through the bug list and adds a brief summary of the bug fix to the "User Story"
field for each bug.

5) The release manager sets the relnote? flag for each with the approver as the requestee. Would someone else
be better for the requestee?

6) The requestee reviews the release note summary and sets the relnote+ flag or relnote- if something needs to be changed.

7) Once all release notes are reviewed, the release manager will use a script to pull the high level summaries, each of the
individual summaries per bug and using a template, create a new release notes page to be shipped with the final release.
The individual summaries can be separated by topic or component.

The goal of all of this is to figure out how to:

1) start this whole process as early as possible so that it can be revised  over time and be ready when release time comes around.

2) And to be able to script this so that the release process can systematically pull everything using a bug query and construct
the release notes page easily.

Thoughts?
dkl

On 01/21/2015 09:35 AM, Gervase Markham wrote:
> On 16/01/15 18:10, Fr?d?ric Buclin wrote:
>> I disagree. This requires to compile the docs to read them.
> No, because there will be a copy on bugzilla.readthedocs.org.
>
>>> require the patch to contain a patch to the release notes if it's
>>> release-noteworthy. This means all the work is done at the time of patch
>>> submission.
>> I disagree here too. It's not the job of the contributor to decide what
>> should be relnoted and what shouldn't. 
> Well, the contributor in collaboration with their reviewer.
>
> Who adds the relnote keyword at the moment?
>
>> I made another proposal on IRC yesterday. The idea is to still add the
>> 'relnote' keyword as we always did, but we update release notes for each
>> development release instead of waiting for rc1. The bug list between two
>> consecutive dev releases is not that big. And we have a better idea of
>> what is important and what is pretty minor.
> I like that idea. :-) That may well help.
>
> Gerv
>
>
> -
> To view or change your list settings, click here:
> <http://bugzilla.org/cgi-bin/mj_wwwusr?user=dkl at mozilla.com>

-- 
David Lawrence
dkl at mozilla.com
bugzilla.mozilla.org



From lpsolit at gmail.com  Thu Jan 22 00:37:45 2015
From: lpsolit at gmail.com (=?UTF-8?B?RnLDqWTDqXJpYyBCdWNsaW4=?=)
Date: Thu, 22 Jan 2015 01:37:45 +0100
Subject: Release notes for future versions
In-Reply-To: <54BFC4CE.70204@mozilla.com>
References: <T6mdnYer_5mhmyXJnZ2dnUU7-VednZ2d@mozilla.org>	<54B8ECC0.8030306@mozilla.org> <mailman.8616.1421431951.26609.dev-apps-bugzilla@lists.mozilla.org> <54BFB928.1080006@mozilla.org> <54BFC4CE.70204@mozilla.com>
Message-ID: <54C04659.9090804@gmail.com>

Le 21. 01. 15 16:25, David Lawrence a ?crit :
> 4) The release manager goes through the bug list and adds a brief
> summary of the bug fix to the "User Story" field for each bug.

In that case, instead of doing this + setting the relnote flag +
writing/running a script, it would be much easier to update
page/release-notes.html.tmpl directly and attach a patch for review.


LpSolit


From dkl at mozilla.com  Thu Jan 22 16:26:07 2015
From: dkl at mozilla.com (David Lawrence)
Date: Thu, 22 Jan 2015 11:26:07 -0500
Subject: Release notes for future versions
In-Reply-To: <54C04659.9090804@gmail.com>
References: <T6mdnYer_5mhmyXJnZ2dnUU7-VednZ2d@mozilla.org>	<54B8ECC0.8030306@mozilla.org> <mailman.8616.1421431951.26609.dev-apps-bugzilla@lists.mozilla.org> <54BFB928.1080006@mozilla.org> <54BFC4CE.70204@mozilla.com> <54C04659.9090804@gmail.com>
Message-ID: <54C1249F.5060008@mozilla.com>

Well, my thinking was when we do a single patch with all relnotes combines in a
single file initially, it is up to the single reviewer to go back through all the bugs
and verify that the relnote is correct for each. By having each relnote attached
to the inidividul bugs and then asking for review, the approver would only need
to look at that specific relnote. The final reviewer for the top level release notes
bug would therefore only need to look at the high level key points. My proposal
spreads the work load and also the approvers normally have a good understanding
of what is being solved by each bug report.

dkl

On 01/21/2015 07:37 PM, Fr?d?ric Buclin wrote:
> Le 21. 01. 15 16:25, David Lawrence a ?crit :
>> 4) The release manager goes through the bug list and adds a brief
>> summary of the bug fix to the "User Story" field for each bug.
> In that case, instead of doing this + setting the relnote flag +
> writing/running a script, it would be much easier to update
> page/release-notes.html.tmpl directly and attach a patch for review.
>
>
> LpSolit
> -
> To view or change your list settings, click here:
> <http://bugzilla.org/cgi-bin/mj_wwwusr?user=dkl at mozilla.com>

-- 
David Lawrence
dkl at mozilla.com
bugzilla.mozilla.org