chgset numbers required in all Tickets

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

chgset numbers required in all Tickets

Jeff McKenna-2
As I'm hitting documentation tickets I see that most developers do not
mention what MapServer version the change applies to (causing me to
search HISTORY.txt)  Please can you either mention the MapServer version
and/or the SVN chgset/revision value for commits in all future tickets?
  thanks.

-jeff




_______________________________________________
mapserver-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapserver-dev
Reply | Threaded
Open this post in threaded view
|

Re: chgset numbers required in all Tickets

Daniel Morissette
Jeff McKenna wrote:
> As I'm hitting documentation tickets I see that most developers do not
> mention what MapServer version the change applies to (causing me to
> search HISTORY.txt)  Please can you either mention the MapServer version
> and/or the SVN chgset/revision value for commits in all future tickets?
>  thanks.
>

And talking of changeset refs in tickets, for those not much familiar
with Trac yet, the following conventions automatically create clickable
links in ticket output and are the preferred way to go in my opinion:

Use r1234 for a changeset.
e.g.
"... committed to SVN trunk in r1234, and backported to 5.0 branch in r1235"

Use #1234 for a ticket number
e.g.
"See also ticket #1234 for the documentation updates."


Daniel
--
Daniel Morissette
http://www.mapgears.com/
_______________________________________________
mapserver-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapserver-dev
Reply | Threaded
Open this post in threaded view
|

Re: chgset numbers required in all Tickets

Steve Lime
In reply to this post by Jeff McKenna-2
Should these requirements go into our committer guidelines?

Steve

>>> Daniel Morissette <[hidden email]> 03/20/08 2:40 PM >>>
Jeff McKenna wrote:
> As I'm hitting documentation tickets I see that most developers do not
> mention what MapServer version the change applies to (causing me to
> search HISTORY.txt)  Please can you either mention the MapServer version
> and/or the SVN chgset/revision value for commits in all future tickets?
>  thanks.
>

And talking of changeset refs in tickets, for those not much familiar
with Trac yet, the following conventions automatically create clickable
links in ticket output and are the preferred way to go in my opinion:

Use r1234 for a changeset.
e.g.
"... committed to SVN trunk in r1234, and backported to 5.0 branch in r1235"

Use #1234 for a ticket number
e.g.
"See also ticket #1234 for the documentation updates."


Daniel
--
Daniel Morissette
http://www.mapgears.com/
_______________________________________________
mapserver-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapserver-dev

_______________________________________________
mapserver-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapserver-dev
Reply | Threaded
Open this post in threaded view
|

Re: chgset numbers required in all Tickets

Daniel Morissette
Steve Lime wrote:
> Should these requirements go into our committer guidelines?
>

Probably a good idea, and while we're at it we should probably review
and update RFC-7 (as RFC-7-1 or RFC-7a?) to better reflect today's
project realities (use of SVN and Trac, etc.).

As part of incubation we may also need to add something where the
committers explicitly acknowledge that all their contributions are done
under the license of the project. I don't think the current RFC-7 covers
the license aspect. Some projects even go as far as requiring that the
committers sign a formal contributor agreement but that's not an
incubation requirement as long as there is a process to verify that "All
code contributors have agreed to abide by the project's license policy".
So far with other projects it seems that making that committment on the
dev mailing list by referring to e.g. RFC-7a would be sufficient.
(See http://wiki.osgeo.org/wiki/Project_Graduation_Checklist)

Unfortunately I don't have time to work on this update of RFC-7 now...
maybe in a few weeks.

Daniel
--
Daniel Morissette
http://www.mapgears.com/
_______________________________________________
mapserver-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapserver-dev