Did you ever attempt an upgrade before and then downgrade?

I'm noticing two things in your dump:

1) Some of these things it's complaining about are already applied
evolutions, so you shouldn't see it again.
2) Some of them are things that existed in 1.6.13 (the repository fields in
particular were already there).

Christian

-- 
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com


On Thu, Dec 27, 2012 at 2:25 PM, jacob.j.rosales
<jacob.j.rosa...@gmail.com>wrote:

> Same issue when accessing <url>/admin/
>
> 2012-12-27 14:18:54,190 - ERROR - Internal Server Error: /admin/
>
> Traceback (most recent call last):
>   File
> "/usr/local/lib/python2.7/dist-packages/Django-1.4.3-py2.7.egg/django/core/handlers/base.py",
> line 89, in get_response
>     response = middleware_method(request)
>   File
> "/usr/local/lib/python2.7/dist-packages/ReviewBoard-1.7.1-py2.7.egg/reviewboard/accounts/middleware.py",
> line 12, in process_request
>     user = Profile.objects.get(user=request.user)
>   File
> "/usr/local/lib/python2.7/dist-packages/Django-1.4.3-py2.7.egg/django/db/models/manager.py",
> line 131, in get
>     return self.get_query_set().get(*args, **kwargs)
>   File
> "/usr/local/lib/python2.7/dist-packages/Django-1.4.3-py2.7.egg/django/db/models/query.py",
> line 361, in get
>     num = len(clone)
>   File
> "/usr/local/lib/python2.7/dist-packages/Django-1.4.3-py2.7.egg/django/db/models/query.py",
> line 85, in __len__
>     self._result_cache = list(self.iterator())
>   File
> "/usr/local/lib/python2.7/dist-packages/Django-1.4.3-py2.7.egg/django/db/models/query.py",
> line 291, in iterator
>     for row in compiler.results_iter():
>   File
> "/usr/local/lib/python2.7/dist-packages/Django-1.4.3-py2.7.egg/django/db/models/sql/compiler.py",
> line 763, in results_iter
>     for rows in self.execute_sql(MULTI):
>   File
> "/usr/local/lib/python2.7/dist-packages/Django-1.4.3-py2.7.egg/django/db/models/sql/compiler.py",
> line 818, in execute_sql
>     cursor.execute(sql, params)
>   File
> "/usr/local/lib/python2.7/dist-packages/Django-1.4.3-py2.7.egg/django/db/backends/mysql/base.py",
> line 114, in execute
>     return self.cursor.execute(query, args)
>   File "/usr/lib/pymodules/python2.7/MySQLdb/cursors.py", line 166, in
> execute
>     self.errorhandler(self, exc, value)
>   File "/usr/lib/pymodules/python2.7/MySQLdb/connections.py", line 35, in
> defaulterrorhandler
>     raise errorclass, errorvalue
> DatabaseError: (1054, "Unknown column 'accounts_profile.open_an_issue' in
> 'field list'")
>
>
> On Thursday, December 27, 2012 4:19:15 PM UTC-6, Christian Hammond wrote:
>
>> The dashboard is inaccessible, but I'd expect you could reach /admin/
>> directly.
>>
>> Christian
>>
>>
>> On Dec 27, 2012, at 13:59, "jacob.j.rosales" <jacob.j...@gmail.com>
>> wrote:
>>
>> It looks like due to the failed upgrade I am unable to access any pages
>> outside the login page
>>
>> 2012-12-27 13:48:48,658 - ERROR - Internal Server Error: /dashboard/
>> Traceback (most recent call last):
>>   File "/usr/local/lib/python2.7/**dist-packages/Django-1.4.3-**
>> py2.7.egg/django/core/**handlers/base.py", line 89, in get_response
>>     response = middleware_method(request)
>>   File "/usr/local/lib/python2.7/**dist-packages/ReviewBoard-1.7.**
>> 1-py2.7.egg/reviewboard/**accounts/middleware.py", line 12, in
>> process_request
>>     user = Profile.objects.get(user=**request.user)
>>   File "/usr/local/lib/python2.7/**dist-packages/Django-1.4.3-**
>> py2.7.egg/django/db/models/**manager.py", line 131, in get
>>     return self.get_query_set().get(***args, **kwargs)
>>   File "/usr/local/lib/python2.7/**dist-packages/Django-1.4.3-**
>> py2.7.egg/django/db/models/**query.py", line 361, in get
>>     num = len(clone)
>>   File "/usr/local/lib/python2.7/**dist-packages/Django-1.4.3-**
>> py2.7.egg/django/db/models/**query.py", line 85, in __len__
>>     self._result_cache = list(self.iterator())
>>   File "/usr/local/lib/python2.7/**dist-packages/Django-1.4.3-**
>> py2.7.egg/django/db/models/**query.py", line 291, in iterator
>>     for row in compiler.results_iter():
>>   File "/usr/local/lib/python2.7/**dist-packages/Django-1.4.3-**
>> py2.7.egg/django/db/models/**sql/compiler.py", line 763, in results_iter
>>     for rows in self.execute_sql(MULTI):
>>   File "/usr/local/lib/python2.7/**dist-packages/Django-1.4.3-**
>> py2.7.egg/django/db/models/**sql/compiler.py", line 818, in execute_sql
>>     cursor.execute(sql, params)
>>   File "/usr/local/lib/python2.7/**dist-packages/Django-1.4.3-**
>> py2.7.egg/django/db/backends/**mysql/base.py", line 114, in execute
>>     return self.cursor.execute(query, args)
>>   File "/usr/lib/pymodules/python2.7/**MySQLdb/cursors.py", line 166, in
>> execute
>>     self.errorhandler(self, exc, value)
>>   File "/usr/lib/pymodules/python2.7/**MySQLdb/connections.py", line 35,
>> in defaulterrorhandler
>>     raise errorclass, errorvalue
>> DatabaseError: (1054, "Unknown column 'accounts_profile.open_an_**issue'
>> in 'field list'")
>>
>> Is there any other way to get this information?
>> On Thursday, December 27, 2012 3:32:24 PM UTC-6, Christian Hammond wrote:
>>>
>>> Thanks.
>>>
>>> Can you also try to reach your admin page -> database ->
>>> Django_Evolution -> Versions, and see if anything says "Hinted Version?" If
>>> so, screenshot the page?
>>>
>>> Christian
>>>
>>> --
>>> Christian Hammond - chi...@chipx86.com
>>> Review Board - http://www.reviewboard.org
>>> VMware, Inc. - http://www.vmware.com
>>>
>>>
>>> On Thu, Dec 27, 2012 at 1:18 PM, jacob.j.rosales 
>>> <jacob.j...@gmail.com>wrote:
>>>
>>>> Here you go Christian.
>>>>
>>>>
>>>> On Thursday, December 27, 2012 3:11:49 PM UTC-6, Christian Hammond
>>>> wrote:
>>>>
>>>>> Sounds like a similar problem to what Sebastien had, which may be
>>>>> caused.
>>>>>
>>>>> Reading through that thread reminded me of what we found to be a root
>>>>> cause, which should be fixed in newer versions of Django Evolution, but 
>>>>> you
>>>>> wouldn't have that with an older version of Review Board.
>>>>>
>>>>> Can you provide an SQL dump of the django_project_version and
>>>>> django_evolution database tables?
>>>>>
>>>>> Christian
>>>>>
>>>>>
>>>>> --
>>>>> Christian Hammond - chi...@chipx86.com
>>>>>
>>>>> Review Board - http://www.reviewboard.org
>>>>> VMware, Inc. - http://www.vmware.com
>>>>>
>>>>>
>>>>> On Thu, Dec 27, 2012 at 12:36 PM, jacob.j.rosales <
>>>>> jacob.j...@gmail.com> wrote:
>>>>>
>>>>>>  All,
>>>>>>
>>>>>> I have attempted an upgrade to 1.7.1, however the site-install is
>>>>>> failing due to unapplied evolutions:
>>>>>> Looking through the other threads I was unable to find a solution for
>>>>>> my issue. Right now I am not able to get access to the UI to try the
>>>>>> proposed workaround mentioned in
>>>>>> https://groups.google.com/**foru**m/?fromgroups=#!searchin/**revie**
>>>>>> wboard/reviewboard$201.7$**20upg**rade/reviewboard/**5x6kFiKqfqQ/**
>>>>>> 7x7wej-4010J<https://groups.google.com/forum/?fromgroups=#!searchin/reviewboard/reviewboard$201.7$20upgrade/reviewboard/5x6kFiKqfqQ/7x7wej-4010J>
>>>>>>
>>>>>> In any case, I am posting the below info to see if anyone has any
>>>>>> workarounds. Thanks in advance
>>>>>>
>>>>>> Creating tables ...
>>>>>> There are unapplied evolutions for auth.
>>>>>> There are unapplied evolutions for accounts.
>>>>>> There are unapplied evolutions for diffviewer.
>>>>>> There are unapplied evolutions for reviews.
>>>>>> Adding baseline version for new models
>>>>>> Project signature has changed - an evolution is required
>>>>>> Installing custom SQL ...
>>>>>> Installing indexes ...
>>>>>> Installed 0 object(s) from 0 fixture(s)
>>>>>> The stored evolutions do not completely resolve all model changes.
>>>>>> Run `./manage.py evolve --hint` to see a suggestion for the changes
>>>>>> required.
>>>>>>
>>>>>> The following are the changes that could not be resolved:
>>>>>> In model scmtools.Repository:
>>>>>>     Field 'extra_data' has been added
>>>>>>     Field 'hosting_account' has been added
>>>>>> Error: Your models contain changes that Django Evolution cannot
>>>>>> resolve automatically.
>>>>>>
>>>>>>
>>>>>> #----- Evolution for auth
>>>>>> from django_evolution.mutations import DeleteModel
>>>>>>
>>>>>>
>>>>>> MUTATIONS = [
>>>>>>     DeleteModel('Message')
>>>>>> ]
>>>>>> #----------------------
>>>>>> #----- Evolution for accounts
>>>>>> from django_evolution.mutations import AddField
>>>>>> from django.db import models
>>>>>>
>>>>>>
>>>>>> MUTATIONS = [
>>>>>>     AddField('Profile', 'timezone', models.CharField, initial=u'UTC',
>>>>>> max_length=20),
>>>>>>     AddField('Profile', 'open_an_issue', models.BooleanField,
>>>>>> initial=True)
>>>>>> ]
>>>>>> #----------------------
>>>>>> #----- Evolution for diffviewer
>>>>>> from django_evolution.mutations import AddField, DeleteField
>>>>>> from django.db import models
>>>>>> from djblets.util.fields import Base64Field
>>>>>>
>>>>>>
>>>>>> MUTATIONS = [
>>>>>>     AddField('DiffSetHistory', 'last_diff_updated',
>>>>>> models.DateTimeField, null=True),
>>>>>>     AddField('FileDiff', 'diff_hash', models.ForeignKey, null=True,
>>>>>> related_model='diffviewer.**File**DiffData'),
>>>>>>     AddField('FileDiff', 'parent_diff_hash', models.ForeignKey,
>>>>>> null=True, related_model='diffviewer.**File**DiffData'),
>>>>>>     AddField('FileDiff', 'diff64', Base64Field, initial='',
>>>>>> db_column='diff_base64'),
>>>>>>     AddField('FileDiff', 'parent_diff64', Base64Field, initial='',
>>>>>> db_column='parent_diff_base64'****),
>>>>>>     DeleteField('FileDiff', 'parent_diff'),
>>>>>>     DeleteField('FileDiff', 'diff')
>>>>>> ]
>>>>>> #----------------------
>>>>>> #----- Evolution for reviews
>>>>>> from django_evolution.mutations import AddField, DeleteField
>>>>>> from django.db import models
>>>>>> from djblets.util.fields import JSONField
>>>>>>
>>>>>>
>>>>>> MUTATIONS = [
>>>>>>     AddField('**FileAttachmentCommen**t', 'extra_data', JSONField,
>>>>>> null=True),
>>>>>>     AddField('ReviewRequest', 'last_review_activity_**timestam**p',
>>>>>> models.DateTimeField, null=True, db_column='last_review_**timesta**
>>>>>> mp'),
>>>>>>     DeleteField('ReviewRequest', 'last_review_timestamp')
>>>>>> ]
>>>>>> #----------------------
>>>>>> #----- Evolution for scmtools
>>>>>> from django_evolution.mutations import AddField
>>>>>> from django.db import models
>>>>>> from djblets.util.fields import JSONField
>>>>>>
>>>>>>
>>>>>> MUTATIONS = [
>>>>>>     AddField('Repository', 'extra_data', JSONField, null=True),
>>>>>>     AddField('Repository', 'hosting_account', models.ForeignKey,
>>>>>> null=True, related_model='hostingsvcs.**Hos**tingServiceAccount')
>>>>>> ]
>>>>>> #----------------------
>>>>>> Trial evolution successful.
>>>>>> Run './manage.py evolve --hint --execute' to apply evolution.
>>>>>>
>>>>>>  --
>>>>>> Want to help the Review Board project? Donate today at
>>>>>> http://www.reviewboard.org/**don**ate/<http://www.reviewboard.org/donate/>
>>>>>> Happy user? Let us know at 
>>>>>> http://www.reviewboard.org/**use**rs/<http://www.reviewboard.org/users/>
>>>>>> -~----------~----~----~----~--****----~----~------~--~---
>>>>>> To unsubscribe from this group, send email to reviewboard...@**
>>>>>> googlegroups.**com
>>>>>>
>>>>>> For more options, visit this group at http://groups.google.com/**
>>>>>> group**/reviewboard?hl=en<http://groups.google.com/group/reviewboard?hl=en>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>  --
>>>> Want to help the Review Board project? Donate today at
>>>> http://www.reviewboard.org/**donate/<http://www.reviewboard.org/donate/>
>>>> Happy user? Let us know at 
>>>> http://www.reviewboard.org/**users/<http://www.reviewboard.org/users/>
>>>> -~----------~----~----~----~--**----~----~------~--~---
>>>> To unsubscribe from this group, send email to
>>>> reviewboard...@googlegroups.**com
>>>> For more options, visit this group at http://groups.google.com/**
>>>> group/reviewboard?hl=en<http://groups.google.com/group/reviewboard?hl=en>
>>>>
>>>>
>>>>
>>>
>>>
> On Thursday, December 27, 2012 4:19:15 PM UTC-6, Christian Hammond wrote:
>
>> The dashboard is inaccessible, but I'd expect you could reach /admin/
>> directly.
>>
>> Christian
>>
>>
>> On Dec 27, 2012, at 13:59, "jacob.j.rosales" <jacob.j...@gmail.com>
>> wrote:
>>
>> It looks like due to the failed upgrade I am unable to access any pages
>> outside the login page
>>
>> 2012-12-27 13:48:48,658 - ERROR - Internal Server Error: /dashboard/
>> Traceback (most recent call last):
>>   File "/usr/local/lib/python2.7/**dist-packages/Django-1.4.3-**
>> py2.7.egg/django/core/**handlers/base.py", line 89, in get_response
>>     response = middleware_method(request)
>>   File "/usr/local/lib/python2.7/**dist-packages/ReviewBoard-1.7.**
>> 1-py2.7.egg/reviewboard/**accounts/middleware.py", line 12, in
>> process_request
>>     user = Profile.objects.get(user=**request.user)
>>   File "/usr/local/lib/python2.7/**dist-packages/Django-1.4.3-**
>> py2.7.egg/django/db/models/**manager.py", line 131, in get
>>     return self.get_query_set().get(***args, **kwargs)
>>   File "/usr/local/lib/python2.7/**dist-packages/Django-1.4.3-**
>> py2.7.egg/django/db/models/**query.py", line 361, in get
>>     num = len(clone)
>>   File "/usr/local/lib/python2.7/**dist-packages/Django-1.4.3-**
>> py2.7.egg/django/db/models/**query.py", line 85, in __len__
>>     self._result_cache = list(self.iterator())
>>   File "/usr/local/lib/python2.7/**dist-packages/Django-1.4.3-**
>> py2.7.egg/django/db/models/**query.py", line 291, in iterator
>>     for row in compiler.results_iter():
>>   File "/usr/local/lib/python2.7/**dist-packages/Django-1.4.3-**
>> py2.7.egg/django/db/models/**sql/compiler.py", line 763, in results_iter
>>     for rows in self.execute_sql(MULTI):
>>   File "/usr/local/lib/python2.7/**dist-packages/Django-1.4.3-**
>> py2.7.egg/django/db/models/**sql/compiler.py", line 818, in execute_sql
>>     cursor.execute(sql, params)
>>   File "/usr/local/lib/python2.7/**dist-packages/Django-1.4.3-**
>> py2.7.egg/django/db/backends/**mysql/base.py", line 114, in execute
>>     return self.cursor.execute(query, args)
>>   File "/usr/lib/pymodules/python2.7/**MySQLdb/cursors.py", line 166, in
>> execute
>>     self.errorhandler(self, exc, value)
>>   File "/usr/lib/pymodules/python2.7/**MySQLdb/connections.py", line 35,
>> in defaulterrorhandler
>>     raise errorclass, errorvalue
>> DatabaseError: (1054, "Unknown column 'accounts_profile.open_an_**issue'
>> in 'field list'")
>>
>> Is there any other way to get this information?
>> On Thursday, December 27, 2012 3:32:24 PM UTC-6, Christian Hammond wrote:
>>>
>>> Thanks.
>>>
>>> Can you also try to reach your admin page -> database ->
>>> Django_Evolution -> Versions, and see if anything says "Hinted Version?" If
>>> so, screenshot the page?
>>>
>>> Christian
>>>
>>> --
>>> Christian Hammond - chi...@chipx86.com
>>> Review Board - http://www.reviewboard.org
>>> VMware, Inc. - http://www.vmware.com
>>>
>>>
>>> On Thu, Dec 27, 2012 at 1:18 PM, jacob.j.rosales 
>>> <jacob.j...@gmail.com>wrote:
>>>
>>>> Here you go Christian.
>>>>
>>>>
>>>> On Thursday, December 27, 2012 3:11:49 PM UTC-6, Christian Hammond
>>>> wrote:
>>>>
>>>>> Sounds like a similar problem to what Sebastien had, which may be
>>>>> caused.
>>>>>
>>>>> Reading through that thread reminded me of what we found to be a root
>>>>> cause, which should be fixed in newer versions of Django Evolution, but 
>>>>> you
>>>>> wouldn't have that with an older version of Review Board.
>>>>>
>>>>> Can you provide an SQL dump of the django_project_version and
>>>>> django_evolution database tables?
>>>>>
>>>>> Christian
>>>>>
>>>>>
>>>>> --
>>>>> Christian Hammond - chi...@chipx86.com
>>>>>
>>>>> Review Board - http://www.reviewboard.org
>>>>> VMware, Inc. - http://www.vmware.com
>>>>>
>>>>>
>>>>> On Thu, Dec 27, 2012 at 12:36 PM, jacob.j.rosales <
>>>>> jacob.j...@gmail.com> wrote:
>>>>>
>>>>>>  All,
>>>>>>
>>>>>> I have attempted an upgrade to 1.7.1, however the site-install is
>>>>>> failing due to unapplied evolutions:
>>>>>> Looking through the other threads I was unable to find a solution for
>>>>>> my issue. Right now I am not able to get access to the UI to try the
>>>>>> proposed workaround mentioned in
>>>>>> https://groups.google.com/**foru**m/?fromgroups=#!searchin/**revie**
>>>>>> wboard/reviewboard$201.7$**20upg**rade/reviewboard/**5x6kFiKqfqQ/**
>>>>>> 7x7wej-4010J<https://groups.google.com/forum/?fromgroups=#!searchin/reviewboard/reviewboard$201.7$20upgrade/reviewboard/5x6kFiKqfqQ/7x7wej-4010J>
>>>>>>
>>>>>> In any case, I am posting the below info to see if anyone has any
>>>>>> workarounds. Thanks in advance
>>>>>>
>>>>>> Creating tables ...
>>>>>> There are unapplied evolutions for auth.
>>>>>> There are unapplied evolutions for accounts.
>>>>>> There are unapplied evolutions for diffviewer.
>>>>>> There are unapplied evolutions for reviews.
>>>>>> Adding baseline version for new models
>>>>>> Project signature has changed - an evolution is required
>>>>>> Installing custom SQL ...
>>>>>> Installing indexes ...
>>>>>> Installed 0 object(s) from 0 fixture(s)
>>>>>> The stored evolutions do not completely resolve all model changes.
>>>>>> Run `./manage.py evolve --hint` to see a suggestion for the changes
>>>>>> required.
>>>>>>
>>>>>> The following are the changes that could not be resolved:
>>>>>> In model scmtools.Repository:
>>>>>>     Field 'extra_data' has been added
>>>>>>     Field 'hosting_account' has been added
>>>>>> Error: Your models contain changes that Django Evolution cannot
>>>>>> resolve automatically.
>>>>>>
>>>>>>
>>>>>> #----- Evolution for auth
>>>>>> from django_evolution.mutations import DeleteModel
>>>>>>
>>>>>>
>>>>>> MUTATIONS = [
>>>>>>     DeleteModel('Message')
>>>>>> ]
>>>>>> #----------------------
>>>>>> #----- Evolution for accounts
>>>>>> from django_evolution.mutations import AddField
>>>>>> from django.db import models
>>>>>>
>>>>>>
>>>>>> MUTATIONS = [
>>>>>>     AddField('Profile', 'timezone', models.CharField, initial=u'UTC',
>>>>>> max_length=20),
>>>>>>     AddField('Profile', 'open_an_issue', models.BooleanField,
>>>>>> initial=True)
>>>>>> ]
>>>>>> #----------------------
>>>>>> #----- Evolution for diffviewer
>>>>>> from django_evolution.mutations import AddField, DeleteField
>>>>>> from django.db import models
>>>>>> from djblets.util.fields import Base64Field
>>>>>>
>>>>>>
>>>>>> MUTATIONS = [
>>>>>>     AddField('DiffSetHistory', 'last_diff_updated',
>>>>>> models.DateTimeField, null=True),
>>>>>>     AddField('FileDiff', 'diff_hash', models.ForeignKey, null=True,
>>>>>> related_model='diffviewer.**File**DiffData'),
>>>>>>     AddField('FileDiff', 'parent_diff_hash', models.ForeignKey,
>>>>>> null=True, related_model='diffviewer.**File**DiffData'),
>>>>>>     AddField('FileDiff', 'diff64', Base64Field, initial='',
>>>>>> db_column='diff_base64'),
>>>>>>     AddField('FileDiff', 'parent_diff64', Base64Field, initial='',
>>>>>> db_column='parent_diff_base64'****),
>>>>>>     DeleteField('FileDiff', 'parent_diff'),
>>>>>>     DeleteField('FileDiff', 'diff')
>>>>>> ]
>>>>>> #----------------------
>>>>>> #----- Evolution for reviews
>>>>>> from django_evolution.mutations import AddField, DeleteField
>>>>>> from django.db import models
>>>>>> from djblets.util.fields import JSONField
>>>>>>
>>>>>>
>>>>>> MUTATIONS = [
>>>>>>     AddField('**FileAttachmentCommen**t', 'extra_data', JSONField,
>>>>>> null=True),
>>>>>>     AddField('ReviewRequest', 'last_review_activity_**timestam**p',
>>>>>> models.DateTimeField, null=True, db_column='last_review_**timesta**
>>>>>> mp'),
>>>>>>     DeleteField('ReviewRequest', 'last_review_timestamp')
>>>>>> ]
>>>>>> #----------------------
>>>>>> #----- Evolution for scmtools
>>>>>> from django_evolution.mutations import AddField
>>>>>> from django.db import models
>>>>>> from djblets.util.fields import JSONField
>>>>>>
>>>>>>
>>>>>> MUTATIONS = [
>>>>>>     AddField('Repository', 'extra_data', JSONField, null=True),
>>>>>>     AddField('Repository', 'hosting_account', models.ForeignKey,
>>>>>> null=True, related_model='hostingsvcs.**Hos**tingServiceAccount')
>>>>>> ]
>>>>>> #----------------------
>>>>>> Trial evolution successful.
>>>>>> Run './manage.py evolve --hint --execute' to apply evolution.
>>>>>>
>>>>>>  --
>>>>>> Want to help the Review Board project? Donate today at
>>>>>> http://www.reviewboard.org/**don**ate/<http://www.reviewboard.org/donate/>
>>>>>> Happy user? Let us know at 
>>>>>> http://www.reviewboard.org/**use**rs/<http://www.reviewboard.org/users/>
>>>>>> -~----------~----~----~----~--****----~----~------~--~---
>>>>>> To unsubscribe from this group, send email to reviewboard...@**
>>>>>> googlegroups.**com
>>>>>>
>>>>>> For more options, visit this group at http://groups.google.com/**
>>>>>> group**/reviewboard?hl=en<http://groups.google.com/group/reviewboard?hl=en>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>  --
>>>> Want to help the Review Board project? Donate today at
>>>> http://www.reviewboard.org/**donate/<http://www.reviewboard.org/donate/>
>>>> Happy user? Let us know at 
>>>> http://www.reviewboard.org/**users/<http://www.reviewboard.org/users/>
>>>> -~----------~----~----~----~--**----~----~------~--~---
>>>> To unsubscribe from this group, send email to
>>>> reviewboard...@googlegroups.**com
>>>> For more options, visit this group at http://groups.google.com/**
>>>> group/reviewboard?hl=en<http://groups.google.com/group/reviewboard?hl=en>
>>>>
>>>>
>>>>
>>>
>>>  --
> Want to help the Review Board project? Donate today at
> http://www.reviewboard.org/donate/
> Happy user? Let us know at http://www.reviewboard.org/users/
> -~----------~----~----~----~------~----~------~--~---
> To unsubscribe from this group, send email to
> reviewboard+unsubscr...@googlegroups.com
>
> For more options, visit this group at
> http://groups.google.com/group/reviewboard?hl=en
>
>
>

-- 
Want to help the Review Board project? Donate today at 
http://www.reviewboard.org/donate/
Happy user? Let us know at http://www.reviewboard.org/users/
-~----------~----~----~----~------~----~------~--~---
To unsubscribe from this group, send email to 
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/reviewboard?hl=en


Reply via email to