On Tue, Apr 07, 2009 at 08:04:56PM -0700, Marek Szuba wrote: -> On a related note, Chris has pointer out an important issue pertaining -> to fix submission: with Pygr code changing quite rapidly it is very -> easy on one hand for a patch to stop applying cleanly, on the other for -> the devs to forget whether a patch has actually been committed :-) In -> order to address this before it becomes a problem we would like to -> introduce the following policy: each patch which has made it to the -> fixed-needs-review stage is to be committed into a dedicated branch -> (named, unimaginatively, "issueXXX" or something like this) of the -> GitHub Pygr repository; these branches would then be deleted as the -> code is merged into the main repository. Given that most (if not all) -> Pygr developers have already got write access to that repository, the -> overhead of this approach would be minimal while greatly facilitating -> keeping patches under control. -> -> What do you think?
Sounds good. Just remember to delete the branches on that repo after merge... --titus -- C. Titus Brown, c...@msu.edu --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pygr-dev" group. To post to this group, send email to pygr-dev@googlegroups.com To unsubscribe from this group, send email to pygr-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/pygr-dev?hl=en -~----------~----~----~----~------~----~------~--~---
