I tried to run it - seems to work fine, couldn't see any glaring mistakes.
The only small issue is with the owner emails, which are not displayed
completely but with dots (veg...@gmail.com instead of vega...@gmail.com).
Not sure if it is a big deal, might be worth to create a mapping from
When do we want to schedule the cut over? I can put the request in today...
~Michael
On Apr 23, 2011, at 2:44 PM, James Purser wrote:
+1 To the issue freeze and migrate option
On Sun, Apr 24, 2011 at 4:54 AM, Michael MacFadden
michael.macfad...@gmail.com wrote:
I think everything is
The sooner the better imho.
2011/4/24 Michael MacFadden michael.macfad...@gmail.com
When do we want to schedule the cut over? I can put the request in
today...
~Michael
On Apr 23, 2011, at 2:44 PM, James Purser wrote:
+1 To the issue freeze and migrate option
On Sun, Apr 24, 2011
All,
Unless I get any objection. Let's freeze the Google Code Issue repository.
To my knowledge there is no way to actually turn off the repository. The only
thing I think we can do is change the User Template for the bug to contain a
message saying this system is deprecated and offer a
+1
On Mon, Apr 25, 2011 at 1:13 PM, Michael MacFadden
michael.macfad...@gmail.com wrote:
All,
Unless I get any objection. Let's freeze the Google Code Issue
repository. To my knowledge there is no way to actually turn off the
repository. The only thing I think we can do is change the
+1
Sent from my iPhone
On 25 באפר 2011, at 06:18, James Purser jamesrpur...@gmail.com wrote:
+1
On Mon, Apr 25, 2011 at 1:13 PM, Michael MacFadden
michael.macfad...@gmail.com wrote:
All,
Unless I get any objection. Let's freeze the Google Code Issue
repository. To my knowledge
