[mapguide-internals] Trac Notifications

Robert Bray rbray at robertbray.net
Wed Mar 28 14:40:50 EDT 2007


So then to fix a bug, I need to write some code, create a patch, open a 
new "Patch" ticket, wait for feedback, respond to feedback, possibly 
attach an updated patch, wait for the developer to commit, close the 
patch ticket, and finally close the bug ticket.

Sound about right? The two ticket thing "bugs" me...


Jason Birch wrote:
> I wonder if we can set up a PatchSubmission artifact, and only make the
> list the default assignee for this artifact type?
> That would make it entirely about patch submissions and reviews :)
> I'm not subscribed to mapguide-trac; too much chatter, and I get the
> same from the changeset RSS feed.
> Jason
> -----Original Message-----
> From: Tom Fukushima
> Subject: RE: [mapguide-internals] Trac Notifications
> I originally liked this, but after thinking now I'm not sure I like
> this. I'm already subscribed to mapguide-trac and now my ticket emails
> are going to potentially double. If it's just me though who's subscribed
> to mapguide-trac, I can live with it.
> Also, I want to make it clear that I think that this is a different
> topic than the other thread on patch submissions and reviews.
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals

More information about the mapguide-internals mailing list