From rijulsahu at gmail.com  Wed Apr  8 13:14:28 2015
From: rijulsahu at gmail.com (rijulsahu at gmail.com)
Date: Wed, 8 Apr 2015 06:14:28 -0700 (PDT)
Subject: How to file bug from email in bugzilla to generate automatic issue
Message-ID: <dcfc104f-5bd7-4531-822b-64b7dc61d4a5@googlegroups.com>



I have installed bugzilla 4.4.8 in my local ubuntu 14.04 LTS

also installed iRedAdmin v0.4.1 (MySQL) in my local ( with Round cube for email client)

now how to configure the system, so that i can file a bug from email (mymail at local.org) and bug is automatically generated in bugzilla.

i have referred email_in.pl script documentation but couldn't understand it

please help


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


From aliustek at gmail.com  Wed Apr  8 14:16:29 2015
From: aliustek at gmail.com (Ali Ustek)
Date: Wed, 8 Apr 2015 15:16:29 +0100
Subject: How to file bug from email in bugzilla to generate automatic issue
In-Reply-To: <dcfc104f-5bd7-4531-822b-64b7dc61d4a5@googlegroups.com>
References: <dcfc104f-5bd7-4531-822b-64b7dc61d4a5@googlegroups.com>
Message-ID: <CAGmUV-vbUZtAjfq2RChP0_fh=zk5obsbXBrrZwPVJycicC3E4w@mail.gmail.com>

https://rojanu.wordpress.com/2012/11/13/bugzilla-recieve-bugs-via-email/

On Wed, Apr 8, 2015 at 2:14 PM, <rijulsahu at gmail.com> wrote:

>
>
> I have installed bugzilla 4.4.8 in my local ubuntu 14.04 LTS
>
> also installed iRedAdmin v0.4.1 (MySQL) in my local ( with Round cube for
> email client)
>
> now how to configure the system, so that i can file a bug from email (
> mymail at local.org) and bug is automatically generated in bugzilla.
>
> i have referred email_in.pl script documentation but couldn't understand
> it
>
> please help
>
>
> Rijul Sahu
> _______________________________________________
> 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=aliustek at gmail.com>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bugzilla.org/pipermail/developers/attachments/20150408/b914414d/attachment.html>

From cedric.corazza at gmail.com  Sun Apr 12 15:40:23 2015
From: cedric.corazza at gmail.com (cedric.corazza at gmail.com)
Date: Sun, 12 Apr 2015 08:40:23 -0700 (PDT)
Subject: Bugzilla localization guide
In-Reply-To: <5510680A.8030706@gmail.com>
References: <_qWdnZEtH7eZ_pHInZ2dnUU7-S2dnZ2d@mozilla.org>
	<mailman.1135.1427125187.30386.dev-apps-bugzilla@lists.mozilla.org>
	<5510680A.8030706@gmail.com>
Message-ID: <487fd6af-21c3-4676-b645-19c44904a663@googlegroups.com>

Le lundi 23 mars 2015 20:22:50 UTC+1, C?dric Corazza a ?crit?:
> Le 23/03/2015 16:38, Gervase Markham a ?crit :
[...]
> >
> > Are you interested, and are the Bugzilla team interested, in making this
> > part of a more official Developer's Guide?
> Hi Gerv,
> 
> I can work on it if this is wanted, but I would need a review from an 
> English native speaker to correct my English and from some developer to 
> be sure I did not write incorrect things or if there is an easier/more 
> correct way to perform some of the instructions.
> 
> C?dric

Hi,

Here is how would look like the localization guide on RTD.org:

http://www.bugzilla.fr/docs/l10n/html/index.html

Note: I had to modify bugzilla.css file to get highlighting in the code blocks.

C?dric
_______________________________________________
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 Apr 15 09:27:56 2015
From: gerv at mozilla.org (Gervase Markham)
Date: Wed, 15 Apr 2015 10:27:56 +0100
Subject: Bugzilla localization guide
In-Reply-To: <487fd6af-21c3-4676-b645-19c44904a663@googlegroups.com>
References: <_qWdnZEtH7eZ_pHInZ2dnUU7-S2dnZ2d@mozilla.org>
	<mailman.1135.1427125187.30386.dev-apps-bugzilla@lists.mozilla.org>
	<5510680A.8030706@gmail.com>
	<487fd6af-21c3-4676-b645-19c44904a663@googlegroups.com>
Message-ID: <SoidnZeSu_qAsrPInZ2dnUU7-TmdnZ2d@mozilla.org>

On 12/04/15 16:40, cedric.corazza at gmail.com wrote:
> Here is how would look like the localization guide on RTD.org:
> 
> http://www.bugzilla.fr/docs/l10n/html/index.html
> 
> Note: I had to modify bugzilla.css file to get highlighting in the code blocks.

Given that the way l10n is done may change from release to release, it
seems to me that it makes sense to version a localizer's guide along
with the rest of the documentation.

What do people think? Should we check it in so it appears just as Cedric
has done it?

http://www.bugzilla.fr/docs/l10n/html/index.html

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  Tue Apr 21 14:19:18 2015
From: gerv at mozilla.org (Gervase Markham)
Date: Tue, 21 Apr 2015 16:19:18 +0200
Subject: Bugzilla localization guide
In-Reply-To: <SoidnZeSu_qAsrPInZ2dnUU7-TmdnZ2d@mozilla.org>
References: <_qWdnZEtH7eZ_pHInZ2dnUU7-S2dnZ2d@mozilla.org>
	<mailman.1135.1427125187.30386.dev-apps-bugzilla@lists.mozilla.org>
	<5510680A.8030706@gmail.com>
	<487fd6af-21c3-4676-b645-19c44904a663@googlegroups.com>
	<SoidnZeSu_qAsrPInZ2dnUU7-TmdnZ2d@mozilla.org>
Message-ID: <LbadnRafRqH6wavInZ2dnUU7-R-dnZ2d@mozilla.org>

On 15/04/15 11:27, Gervase Markham wrote:
> What do people think? Should we check it in so it appears just as Cedric
> has done it?
> 
> http://www.bugzilla.fr/docs/l10n/html/index.html

Silence is consent :-)

https://bugzilla.mozilla.org/show_bug.cgi?id=1156785

Gerv


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


From mcote at bugzilla.org  Tue Apr 21 20:59:03 2015
From: mcote at bugzilla.org (=?UTF-8?B?TWFyayBDw7R0w6k=?=)
Date: Tue, 21 Apr 2015 13:59:03 -0700
Subject: VCS updates: bzr moving, cvs ending
Message-ID: <9PednSEIUISFJ6vInZ2dnUU7-KednZ2d@mozilla.org>

At the Bugzilla project meeting on 2015-03-25[1] the project lead and
assistant leads agreed on two major changes to Bugzilla's source-code
hosting:

1. CVS support is officially dropped as of now. 4.0 is the last version
that was released on CVS, and it will be EOLed when 5.0 comes out (very
soon; rc3 was just released). In the event of a release on the 4.0
branch before it is EOLed, any Bugzilla installations that have not
migrated to bzr or git will have to apply patches[3] to upgrade, which
will continue to be distributed as usual. Bugzilla site admins are
strongly encouraged to migrate to pulling from git.mozilla.org[4] as
soon as possible.

2. Bazaar hosting has been officially switched from bzr.mozilla.org to
bzr.bugzilla.org. bzr.bugzilla.org is already active and syncing changes
from git.mozilla.org. bzr.mozilla.org is no longer syncing changes and
will soon be shut down. Any sites upgrading from bzr.mozilla.org *must*
do one of the following to apply any future upgrades, in order of
preference:

* Switch to upgrading from git.mozilla.org.[5]
* Switch to pulling from bzr.bugzilla.org. See instructions at 
http://bzr.bugzilla.org/.
* Apply the released patch.

bzr.bugzilla.org will continue to mirror changes from git.mozilla.org
for the 4.0, 4.2, and 4.4 branches as long as they are supported. Note
that, at the moment, master/trunk is being mirrored as well, but no
other branches, including and subsequent to 5.0, will be mirrored to
bzr.bugzilla.org, and trunk mirroring may cease at any time.

Note that bzr.bugzilla.org is waiting on a proper certificate[6]; please
use plain http until this is resolved.

The Bugzilla team apologizes for any inconvenience. Please see our
support options[7] if you have trouble migrating.

Mark C?t?
Assistant Project Lead, Bugzilla

[1] https://wiki.mozilla.org/Bugzilla:Meetings:2015-03-25
[2]
https://bugzilla.mozilla.org/buglist.cgi?f1=flagtypes.name&o1=substring&resolution=---&query_format=advanced&v1=blocking5.0%2B&product=Bugzilla
[3] https://www.bugzilla.org/download/#v40
[4]
http://bugzilla.readthedocs.org/en/latest/installing/migrating-from-cvs.html
[5]
http://bugzilla.readthedocs.org/en/latest/installing/migrating-from-bzr.html
[6] https://bugzilla.mozilla.org/show_bug.cgi?id=1155525
[7] https://www.bugzilla.org/support/

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

From justdave at bugzilla.org  Thu Apr 23 05:20:43 2015
From: justdave at bugzilla.org (Dave Miller)
Date: Thu, 23 Apr 2015 01:20:43 -0400
Subject: Bugzilla branch lifecycle proposal
Message-ID: <5538812B.2060003@bugzilla.org>

The following proposal was on the agenda for our Project meeting
yesterday, but because it was the only thing on the agenda, and we felt
it warranted a larger audience than those in attendance at the meeting,
we opted to call off the meeting and post it here.

----------------
Proposal (from LpSolit) : Reduce the number of supported branches.
Instead of waiting for {N+3}.0 to be released before N.x reaches EOL, I
propose N.x reaches EOL 4 months after the release of {N+2}.0. Concrete
example: instead of waiting for 6.0 to be released before 4.2 reaches
EOL, I propose 4.2 reaches EOL 4 months after the release of 5.0
(probably means around 5.0.2). Two major reasons for that: 1) when we
are closer from the next major release, having to think about very old
branches is a pain (think about security backports, QA, maintain old
repo alive, release stuff), and 2) data shows that installations still
running old versions of Bugzilla generally do not care about upgrading
(e.g. install 4.0.1 and that's it; never upgrade to 4.0.17, so why
should we bother that long?).
----------------

Since LpSolit hasn't posted it here himself yet I figured I'd get it out
there.  Discuss.

-- 
Dave Miller http://www.justdave.net/
IT Infrastructure Engineer, Mozilla http://www.mozilla.org/
Project Leader, Bugzilla Bug Tracking System http://www.bugzilla.org/



From justdave at bugzilla.org  Thu Apr 23 05:59:21 2015
From: justdave at bugzilla.org (Dave Miller)
Date: Thu, 23 Apr 2015 01:59:21 -0400
Subject: Bugzilla branch lifecycle proposal
In-Reply-To: <5538812B.2060003@bugzilla.org>
References: <5538812B.2060003@bugzilla.org>
Message-ID: <55388A39.5040900@bugzilla.org>

For the record, I like this plan.  Our release cycles tend to take long
enough these days that it's a Really Long Time? before a release gets EOLed.

Dave Miller wrote:
> The following proposal was on the agenda for our Project meeting
> yesterday, but because it was the only thing on the agenda, and we felt
> it warranted a larger audience than those in attendance at the meeting,
> we opted to call off the meeting and post it here.
> 
> ----------------
> Proposal (from LpSolit) : Reduce the number of supported branches.
> Instead of waiting for {N+3}.0 to be released before N.x reaches EOL, I
> propose N.x reaches EOL 4 months after the release of {N+2}.0. Concrete
> example: instead of waiting for 6.0 to be released before 4.2 reaches
> EOL, I propose 4.2 reaches EOL 4 months after the release of 5.0
> (probably means around 5.0.2). Two major reasons for that: 1) when we
> are closer from the next major release, having to think about very old
> branches is a pain (think about security backports, QA, maintain old
> repo alive, release stuff), and 2) data shows that installations still
> running old versions of Bugzilla generally do not care about upgrading
> (e.g. install 4.0.1 and that's it; never upgrade to 4.0.17, so why
> should we bother that long?).
> ----------------
> 
> Since LpSolit hasn't posted it here himself yet I figured I'd get it out
> there.  Discuss.
> 

-- 
Dave Miller http://www.justdave.net/
IT Infrastructure Engineer, Mozilla http://www.mozilla.org/
Project Leader, Bugzilla Bug Tracking System http://www.bugzilla.org/



From vladd at bugzilla.org  Thu Apr 23 07:26:37 2015
From: vladd at bugzilla.org (Vlad Dascalu)
Date: Thu, 23 Apr 2015 10:26:37 +0300
Subject: Bugzilla branch lifecycle proposal
In-Reply-To: <55388A39.5040900@bugzilla.org>
References: <5538812B.2060003@bugzilla.org>
	<55388A39.5040900@bugzilla.org>
Message-ID: <CAHzU5kcERwGXPQEPV2tvvpFQ61QLkUmgYFS9CkNo-P29J2q+ag@mail.gmail.com>

Looks good to me.

I'd encourage thoughts on how to be on par with Firefox, Chrome and
Cpanel-like products in terms of self-updates. To get there longterm we
need to discuss the strategy now.

On Thursday, April 23, 2015, Dave Miller <justdave at bugzilla.org> wrote:

> For the record, I like this plan.  Our release cycles tend to take long
> enough these days that it's a Really Long Time? before a release gets
> EOLed.
>
> Dave Miller wrote:
> > The following proposal was on the agenda for our Project meeting
> > yesterday, but because it was the only thing on the agenda, and we felt
> > it warranted a larger audience than those in attendance at the meeting,
> > we opted to call off the meeting and post it here.
> >
> > ----------------
> > Proposal (from LpSolit) : Reduce the number of supported branches.
> > Instead of waiting for {N+3}.0 to be released before N.x reaches EOL, I
> > propose N.x reaches EOL 4 months after the release of {N+2}.0. Concrete
> > example: instead of waiting for 6.0 to be released before 4.2 reaches
> > EOL, I propose 4.2 reaches EOL 4 months after the release of 5.0
> > (probably means around 5.0.2). Two major reasons for that: 1) when we
> > are closer from the next major release, having to think about very old
> > branches is a pain (think about security backports, QA, maintain old
> > repo alive, release stuff), and 2) data shows that installations still
> > running old versions of Bugzilla generally do not care about upgrading
> > (e.g. install 4.0.1 and that's it; never upgrade to 4.0.17, so why
> > should we bother that long?).
> > ----------------
> >
> > Since LpSolit hasn't posted it here himself yet I figured I'd get it out
> > there.  Discuss.
> >
>
> --
> Dave Miller http://www.justdave.net/
> IT Infrastructure Engineer, Mozilla http://www.mozilla.org/
> Project Leader, Bugzilla Bug Tracking System http://www.bugzilla.org/
>
> -
> To view or change your list settings, click here:
> <http://bugzilla.org/cgi-bin/mj_wwwusr?user=vladd at bugzilla.org>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bugzilla.org/pipermail/developers/attachments/20150423/8fe29262/attachment.html>

From gerv at mozilla.org  Thu Apr 23 15:56:54 2015
From: gerv at mozilla.org (Gervase Markham)
Date: Thu, 23 Apr 2015 16:56:54 +0100
Subject: Bugzilla branch lifecycle proposal
In-Reply-To: <5538812B.2060003@bugzilla.org>
References: <5538812B.2060003@bugzilla.org>
Message-ID: <55391646.5000403@mozilla.org>

On 23/04/15 06:20, Dave Miller wrote:
> Since LpSolit hasn't posted it here himself yet I figured I'd get it out
> there.  Discuss.

I'm in support of this.

Gerv



From cedric.corazza at gmail.com  Thu Apr 23 22:51:40 2015
From: cedric.corazza at gmail.com (cedric.corazza at gmail.com)
Date: Thu, 23 Apr 2015 15:51:40 -0700 (PDT)
Subject: Bugzilla branch lifecycle proposal
In-Reply-To: <mailman.2069.1429766450.29280.dev-apps-bugzilla@lists.mozilla.org>
References: <mailman.2069.1429766450.29280.dev-apps-bugzilla@lists.mozilla.org>
Message-ID: <d846d97d-6d26-4b1c-b220-fecf61d710f2@googlegroups.com>

> Since LpSolit hasn't posted it here himself yet I figured I'd get it out
> there.  Discuss.

As a localizer, I do agree too: from 4 to 5 branches to maintain (with trunk) is really painful.

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


From dkl at mozilla.com  Thu Apr 23 16:25:49 2015
From: dkl at mozilla.com (Dave Lawrence)
Date: Thu, 23 Apr 2015 12:25:49 -0400
Subject: Bugzilla branch lifecycle proposal
In-Reply-To: <5538812B.2060003@bugzilla.org>
References: <5538812B.2060003@bugzilla.org>
Message-ID: <CAO_8sEySYwx0WJGd6aYvJbZg12FxNz8Wbb7OfvZzae+kaj06jw@mail.gmail.com>

I also support this. Although I think it might be better to extend to 4
months instead of 6 given how long our release cycles have been
historically.

dkl

On Thu, Apr 23, 2015 at 1:20 AM, Dave Miller <justdave at bugzilla.org> wrote:

> The following proposal was on the agenda for our Project meeting
> yesterday, but because it was the only thing on the agenda, and we felt
> it warranted a larger audience than those in attendance at the meeting,
> we opted to call off the meeting and post it here.
>
> ----------------
> Proposal (from LpSolit) : Reduce the number of supported branches.
> Instead of waiting for {N+3}.0 to be released before N.x reaches EOL, I
> propose N.x reaches EOL 4 months after the release of {N+2}.0. Concrete
> example: instead of waiting for 6.0 to be released before 4.2 reaches
> EOL, I propose 4.2 reaches EOL 4 months after the release of 5.0
> (probably means around 5.0.2). Two major reasons for that: 1) when we
> are closer from the next major release, having to think about very old
> branches is a pain (think about security backports, QA, maintain old
> repo alive, release stuff), and 2) data shows that installations still
> running old versions of Bugzilla generally do not care about upgrading
> (e.g. install 4.0.1 and that's it; never upgrade to 4.0.17, so why
> should we bother that long?).
> ----------------
>
> Since LpSolit hasn't posted it here himself yet I figured I'd get it out
> there.  Discuss.
>
> --
> Dave Miller http://www.justdave.net/
> IT Infrastructure Engineer, Mozilla http://www.mozilla.org/
> Project Leader, Bugzilla Bug Tracking System http://www.bugzilla.org/
>
> -
> 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bugzilla.org/pipermail/developers/attachments/20150423/9b88a329/attachment.html>