You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-dev@xmlgraphics.apache.org by Bertrand Delacretaz <bd...@codeconsult.ch> on 2002/08/28 09:38:29 UTC
Re: Project Management (why not bugzilla?)
On Wednesday 28 August 2002 06:33, Arved Sandstrom wrote:
>. . .
> Bugzilla doesn't cut it for patches. I want a simple list.
>. . .
I don't see the problem with bugzilla, but maybe you have some specific
issues in mind?
The Cocoon project, for example uses bugzilla entries with summaries starting
with [PATCH] for this, and it seems to work pretty well (details under
http://xml.apache.org/cocoon/howto/howto-bugzilla.html).
Note also the "patch queue" link on http://xml.apache.org/cocoon/index.html,
which dynamically queries bugzilla for an up-to-date list of patches
(assuming the above convention is used).
IMHO a similar convention would prevent patches from falling through the
cracks, without needing a separate mailing list.
-Bertrand
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: Project Management (why not bugzilla?)
Posted by Christian Geisert <ch...@isu-gmbh.de>.
Bertrand Delacretaz schrieb:
[..]
> The Cocoon project, for example uses bugzilla entries with summaries starting
> with [PATCH] for this, and it seems to work pretty well (details under
> http://xml.apache.org/cocoon/howto/howto-bugzilla.html).
+1 for trying this
Christian
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: Project Management (why not bugzilla?)
Posted by "J.Pietschmann" <j3...@yahoo.de>.
Bertrand Delacretaz wrote:
> The Cocoon project, for example uses bugzilla entries with summaries starting
> with [PATCH] for this, and it seems to work pretty well (details under
> http://xml.apache.org/cocoon/howto/howto-bugzilla.html).
+1
J.Pietschmann
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: Project Management (why not bugzilla?)
Posted by Jeremias Maerki <de...@greenmail.ch>.
+1 from me, too. We already talked about this in June:
http://marc.theaimsgroup.com/?t=102462495900003&r=1&w=2
On 28.08.2002 09:38:29 Bertrand Delacretaz wrote:
> The Cocoon project, for example uses bugzilla entries with summaries starting
> with [PATCH] for this, and it seems to work pretty well (details under
> http://xml.apache.org/cocoon/howto/howto-bugzilla.html).
Jeremias Maerki
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: Project Management (why not bugzilla?)
Posted by Michael Gratton <mj...@recalldesign.com>.
[just diving in late here]
FWIW, I'm all for using Bugzilla for managing patches and the like.
Bertrand Delacretaz wrote:
>
> I think with Bugzilla and the [PATCH] convention for summary lines, patches
> that are entered correctly will not get lost. Just include a "patch queue"
> link on the FOP homepage and everybody can get the up-to-date list.
One small nit, wouldn't it be far, far better to use a keyword? You can
search for it, and you don't get any confusion over the actual spelling
(is it "[PATCH]" "[Patch]" "[patch]" or "*PATCH*"?).
Mike.
--
Michael Gratton <mj...@recalldesign.com>
Recall Design <http://www.recalldesign.com/>
s: 53 Gilbert Street Adelaide SA 5000 Australia
t: +61 8 8217 0500 f: +61 8 8217 0555
Re: Project Management (why not bugzilla?)
Posted by "Peter B. West" <pb...@powerup.com.au>.
Karen Lease wrote:
> Bertrand Delacretaz wrote:
>> I think with Bugzilla and the [PATCH] convention for summary lines,
>> patches that are entered correctly will not get lost. Just include a
>> "patch queue" link on the FOP homepage and everybody can get the
>> up-to-date list.
>>
>>> . . .
>>> I took a look at the Cocoon stuff, and it looks reasonable to me. I
>>> think
>>> we should give it a shot and see how it works. Any comments?
>>
>> +1 of course ;-)
>>
>> -Bertrand
>
> +1 for me too.
>
> -Karen
+1
--
Peter B. West pbwest@powerup.com.au http://www.powerup.com.au/~pbwest/
"Lord, to whom shall we go?"
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: Project Management (why not bugzilla?)
Posted by Karen Lease <kl...@club-internet.fr>.
Bertrand Delacretaz wrote:
> I think with Bugzilla and the [PATCH] convention for summary lines, patches
> that are entered correctly will not get lost. Just include a "patch queue"
> link on the FOP homepage and everybody can get the up-to-date list.
>
>
>>. . .
>>I took a look at the Cocoon stuff, and it looks reasonable to me. I think
>>we should give it a shot and see how it works. Any comments?
>>
>
> +1 of course ;-)
>
> -Bertrand
>
+1 for me too.
I'm having a hard time finding quality time as well. Maybe I'll follow
Arved and do some patching for a while too.
-Karen
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: Project Management (why not bugzilla?)
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Bertrand Delacretaz wrote:
> On Wednesday 28 August 2002 14:14, Arved Sandstrom wrote:
>
>>. . .My main objection to using Bugzilla is the same as
>>for the mailing list - when patches show up as emails on fop-dev, they are
>>lost in the noise.
>>. . .
>
>
> I think with Bugzilla and the [PATCH] convention for summary lines, patches
> that are entered correctly will not get lost. Just include a "patch queue"
> link on the FOP homepage and everybody can get the up-to-date list.
>
>
>>. . .
>>I took a look at the Cocoon stuff, and it looks reasonable to me. I think
>>we should give it a shot and see how it works. Any comments?
>
>
> +1 of course ;-)
BTW, after I set up the query link, I also had set up a cron job that
weekly got the patch queue and mailed a nag to the list ala Gump..
Currently it's down (I was using my company server), but it's planned
for Forrest, so if you start using bugzilla prepending [PATCH] to
subject line, you will be ready :-)
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: Project Management (why not bugzilla?)
Posted by Bertrand Delacretaz <bd...@codeconsult.ch>.
On Wednesday 28 August 2002 14:14, Arved Sandstrom wrote:
>. . .My main objection to using Bugzilla is the same as
> for the mailing list - when patches show up as emails on fop-dev, they are
> lost in the noise.
>. . .
I think with Bugzilla and the [PATCH] convention for summary lines, patches
that are entered correctly will not get lost. Just include a "patch queue"
link on the FOP homepage and everybody can get the up-to-date list.
>. . .
> I took a look at the Cocoon stuff, and it looks reasonable to me. I think
> we should give it a shot and see how it works. Any comments?
+1 of course ;-)
-Bertrand
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: Project Management (why not bugzilla?)
Posted by Bertrand Delacretaz <bd...@codeconsult.ch>.
On Wednesday 28 August 2002 16:55, Victor Mote wrote:
>. . .
> Also, looking at the URL on the Cocoon
> site, it looks like a persistent reusable query could be built within
> Bugzilla that one could simply build a link to (like they did from their
> web site).
>. . .
Yes, that's exactly how it's done in Cocoon, there is a bugzilla query named
"cocoon patch queue" that builds the list of patches.
-Bertrand
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
RE: Project Management (why not bugzilla?)
Posted by Victor Mote <vi...@outfitr.com>.
Arved Sandstrom wrote:
> > > Bugzilla doesn't cut it for patches. I want a simple list.
> > >. . .
> >
> > I don't see the problem with bugzilla, but maybe you have some specific
> > issues in mind?
> >
> > The Cocoon project, for example uses bugzilla entries with
> > summaries starting
> > with [PATCH] for this, and it seems to work pretty well (details under
> > http://xml.apache.org/cocoon/howto/howto-bugzilla.html).
> >
> > Note also the "patch queue" link on
> > http://xml.apache.org/cocoon/index.html,
> > which dynamically queries bugzilla for an up-to-date list of patches
> > (assuming the above convention is used).
> >
> > IMHO a similar convention would prevent patches from falling through the
> > cracks, without needing a separate mailing list.
>
> We can give it a try. My main objection to using Bugzilla is the
> same as for
> the mailing list - when patches show up as emails on fop-dev,
> they are lost
> in the noise. I am not convinced that, as a rule, they would do
> much better
> competing with bug reports in a defect tracking system. But maybe it'll do
> _enough_ better that a couple of dedicated patch people will have
> an easier
> time of it.
>
> I wasn't really criticizing Bugzilla itself. :-) Although I have seen
> all-purpose issue-tracking systems fail before, not only for patches, and
> not because the system itself was all that bad. So I am a bit skeptical at
> the moment, but I can be persuaded.
>
> I took a look at the Cocoon stuff, and it looks reasonable to me.
> I think we
> should give it a shot and see how it works. Any comments?
The thing I like about the Bugzilla approach is that a submitted item
appears on a permanent list until someone proactively removes it. Also, it
has a mechanism for negotiating. The release manager has a central place to
look for uncommitted changes before creating a release candidate. I like the
Cocoon example listed above. Also, looking at the URL on the Cocoon site, it
looks like a persistent reusable query could be built within Bugzilla that
one could simply build a link to (like they did from their web site). The
mechanism is less important than the principle, so I am not attached to any
particular solution, but it seems like Bugzilla would be a good approach. If
it doesn't work as well as hoped, we can change to something better. I am
pretty sure that it will be better than the current system.
Vic
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
RE: Project Management (why not bugzilla?)
Posted by Arved Sandstrom <Ar...@chebucto.ns.ca>.
> -----Original Message-----
> From: Bertrand Delacretaz [mailto:bdelacretaz@codeconsult.ch]
> Sent: August 28, 2002 4:38 AM
> To: fop-dev@xml.apache.org
> Cc: Arved Sandstrom
> Subject: Re: Project Management (why not bugzilla?)
>
>
> On Wednesday 28 August 2002 06:33, Arved Sandstrom wrote:
> >. . .
> > Bugzilla doesn't cut it for patches. I want a simple list.
> >. . .
>
> I don't see the problem with bugzilla, but maybe you have some specific
> issues in mind?
>
> The Cocoon project, for example uses bugzilla entries with
> summaries starting
> with [PATCH] for this, and it seems to work pretty well (details under
> http://xml.apache.org/cocoon/howto/howto-bugzilla.html).
>
> Note also the "patch queue" link on
> http://xml.apache.org/cocoon/index.html,
> which dynamically queries bugzilla for an up-to-date list of patches
> (assuming the above convention is used).
>
> IMHO a similar convention would prevent patches from falling through the
> cracks, without needing a separate mailing list.
We can give it a try. My main objection to using Bugzilla is the same as for
the mailing list - when patches show up as emails on fop-dev, they are lost
in the noise. I am not convinced that, as a rule, they would do much better
competing with bug reports in a defect tracking system. But maybe it'll do
_enough_ better that a couple of dedicated patch people will have an easier
time of it.
I wasn't really criticizing Bugzilla itself. :-) Although I have seen
all-purpose issue-tracking systems fail before, not only for patches, and
not because the system itself was all that bad. So I am a bit skeptical at
the moment, but I can be persuaded.
I took a look at the Cocoon stuff, and it looks reasonable to me. I think we
should give it a shot and see how it works. Any comments?
All I know is that the mailing list isn't working all that well.
Regards,
Arved
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org