Hello everyone, During today's meeting on EVO (which, by the way, seems to persistently suffer from sound problems - as a result of which we'll have the next meeting on Skype) we have decided to tag 0.8-alpha very soon - on either Sunday evening or Monday morning! The reason for waiting until the weekend is that there are still quite a few 0.8-related "fixed, needs review" issues in the tracker and at least some of them pertain to new features in this version; therefore, even though most of these issues are quite old and require merely pro-forma verification, it would be good to have them signed off before the tagging.
At present the list of such issues looks as follows: 34, 44, 57, 58, 70, 81 - to be reviewed by Titus; 54, 71 - to be reviewed by Jenny; 37 - to be reviewed by Namshin; 66, 80 - no reviewer! Fortunately these are not feature freeze-related. Good luck! * * * 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? -- MS --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
