|
»
»
»
»
»
Suggestion for improving the RFC process
|
View:
New views
5 Messages
—
Rating Filter:
Alert me
|
 |
Suggestion for improving the RFC process
by zspitzer
::
Rate this Message:
I would like to suggest adding a extra step for the RFC process that
involves adding any trac tickets relating to the the RFC to the RFC page z -- Zac Spitzer - http://zacster.blogspot.com (My Blog) +61 405 847 168 _______________________________________________ mapguide-internals mailing list mapguide-internals@... http://lists.osgeo.org/mailman/listinfo/mapguide-internals |
|
|
RE: Suggestion for improving the RFC process
by JasonBirch
::
Rate this Message:
I really like the current practice of referencing the ticket number in a
changeset, and backreferencing the changesets from the ticket. With this in place, linking to the tickets from the RFC would allow interested parties to see exactly what changes were made to the code as part of an RFC. It would also, in some cases, allow seeing the initial enhancement request that caused the RFC to be written. As part of this process, the enhancement request could be more easily closed when the ticket is marked as complete. I'd be in favour of adding this to the RFC documents in a "Related Tickets" section. Would this create too much overhead for the RFC implementers? Jason -----Original Message----- From: Zac Spitzer Subject: [mapguide-internals] Suggestion for improving the RFC process I would like to suggest adding a extra step for the RFC process that involves adding any trac tickets relating to the the RFC to the RFC page _______________________________________________ mapguide-internals mailing list mapguide-internals@... http://lists.osgeo.org/mailman/listinfo/mapguide-internals |
|
|
RE: Suggestion for improving the RFC process
by Tom Fukushima
::
Rate this Message:
+1 Tom. I'm in favor of this. Do we need to RFC this? I hope not; let's just update the RFC template.
And as far as I can see it barely adds any overhead, and may make it easier for even the developer to find the relevant ticket since they could go through the RFC instead of having to go through trac. -----Original Message----- From: mapguide-internals-bounces@... [mailto:mapguide-internals-bounces@...] On Behalf Of Jason Birch Sent: Monday, July 21, 2008 1:20 PM To: MapGuide Internals Mail List Subject: RE: [mapguide-internals] Suggestion for improving the RFC process I really like the current practice of referencing the ticket number in a changeset, and backreferencing the changesets from the ticket. With this in place, linking to the tickets from the RFC would allow interested parties to see exactly what changes were made to the code as part of an RFC. It would also, in some cases, allow seeing the initial enhancement request that caused the RFC to be written. As part of this process, the enhancement request could be more easily closed when the ticket is marked as complete. I'd be in favour of adding this to the RFC documents in a "Related Tickets" section. Would this create too much overhead for the RFC implementers? Jason -----Original Message----- From: Zac Spitzer Subject: [mapguide-internals] Suggestion for improving the RFC process I would like to suggest adding a extra step for the RFC process that involves adding any trac tickets relating to the the RFC to the RFC page _______________________________________________ mapguide-internals mailing list mapguide-internals@... http://lists.osgeo.org/mailman/listinfo/mapguide-internals _______________________________________________ mapguide-internals mailing list mapguide-internals@... http://lists.osgeo.org/mailman/listinfo/mapguide-internals |
|
|
RE: Suggestion for improving the RFC process
by Bruce Dechant
::
Rate this Message:
+1 Bruce
I think we just need to update the RFC template we use and start adding the info. Bruce -----Original Message----- From: mapguide-internals-bounces@... [mailto:mapguide-internals-bounces@...] On Behalf Of Tom Fukushima Sent: Monday, July 21, 2008 1:33 PM To: MapGuide Internals Mail List Subject: RE: [mapguide-internals] Suggestion for improving the RFC process +1 Tom. I'm in favor of this. Do we need to RFC this? I hope not; let's just update the RFC template. And as far as I can see it barely adds any overhead, and may make it easier for even the developer to find the relevant ticket since they could go through the RFC instead of having to go through trac. -----Original Message----- From: mapguide-internals-bounces@... [mailto:mapguide-internals-bounces@...] On Behalf Of Jason Birch Sent: Monday, July 21, 2008 1:20 PM To: MapGuide Internals Mail List Subject: RE: [mapguide-internals] Suggestion for improving the RFC process I really like the current practice of referencing the ticket number in a changeset, and backreferencing the changesets from the ticket. With this in place, linking to the tickets from the RFC would allow interested parties to see exactly what changes were made to the code as part of an RFC. It would also, in some cases, allow seeing the initial enhancement request that caused the RFC to be written. As part of this process, the enhancement request could be more easily closed when the ticket is marked as complete. I'd be in favour of adding this to the RFC documents in a "Related Tickets" section. Would this create too much overhead for the RFC implementers? Jason -----Original Message----- From: Zac Spitzer Subject: [mapguide-internals] Suggestion for improving the RFC process I would like to suggest adding a extra step for the RFC process that involves adding any trac tickets relating to the the RFC to the RFC page _______________________________________________ mapguide-internals mailing list mapguide-internals@... http://lists.osgeo.org/mailman/listinfo/mapguide-internals _______________________________________________ mapguide-internals mailing list mapguide-internals@... http://lists.osgeo.org/mailman/listinfo/mapguide-internals _______________________________________________ mapguide-internals mailing list mapguide-internals@... http://lists.osgeo.org/mailman/listinfo/mapguide-internals |
|
|
Re: Suggestion for improving the RFC process
by pagameba
::
Rate this Message:
+1 Paul
On 21-Jul-08, at 3:32 PM, Tom Fukushima wrote: > +1 Tom. I'm in favor of this. Do we need to RFC this? I hope not; > let's just update the RFC template. > > And as far as I can see it barely adds any overhead, and may make it > easier for even the developer to find the relevant ticket since they > could go through the RFC instead of having to go through trac. > > > -----Original Message----- > From: mapguide-internals-bounces@... [mailto:mapguide-internals-bounces@... > ] On Behalf Of Jason Birch > Sent: Monday, July 21, 2008 1:20 PM > To: MapGuide Internals Mail List > Subject: RE: [mapguide-internals] Suggestion for improving the RFC > process > > I really like the current practice of referencing the ticket number > in a > changeset, and backreferencing the changesets from the ticket. With > this in place, linking to the tickets from the RFC would allow > interested parties to see exactly what changes were made to the code > as > part of an RFC. It would also, in some cases, allow seeing the > initial > enhancement request that caused the RFC to be written. As part of > this > process, the enhancement request could be more easily closed when the > ticket is marked as complete. > > I'd be in favour of adding this to the RFC documents in a "Related > Tickets" section. Would this create too much overhead for the RFC > implementers? > > Jason > > -----Original Message----- > From: Zac Spitzer > Subject: [mapguide-internals] Suggestion for improving the RFC process > > I would like to suggest adding a extra step for the RFC process that > involves adding any trac tickets > relating to the the RFC to the RFC page > _______________________________________________ > mapguide-internals mailing list > mapguide-internals@... > http://lists.osgeo.org/mailman/listinfo/mapguide-internals > _______________________________________________ > mapguide-internals mailing list > mapguide-internals@... > http://lists.osgeo.org/mailman/listinfo/mapguide-internals __________________________________________ Paul Spencer Chief Technology Officer DM Solutions Group Inc http://www.dmsolutions.ca/ _______________________________________________ mapguide-internals mailing list mapguide-internals@... http://lists.osgeo.org/mailman/listinfo/mapguide-internals |
| Free Forum Powered by Nabble | Forum Help |