Import Status: Pending Review

Asked by 开阖软件 Jeff Wang

My new project on LP is openerp-china

This branch is an import of the Subversion branch from http://openerp-china.googlecode.com/svn/trunk/.

But 5 days pass, It's still pending review, This branch has not been imported yet.

How long I will wait or If I missed anything ?

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Launchpad Janitor (janitor) said :
#1

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Revision history for this message
Max Bowsher (maxb) said :
#2

Hi,

Sorry about that. At the moment there isn't any sort of organized rota for reviewing code imports - but various people do so when they have time. It happened that you experienced a time when all of the pool of people who frequently review code imports were busy with other matters.

It may be that a more organized approach to code import reviewing is needed.

Revision history for this message
Tim Penhey (thumper) said :
#3

Ah... I think I dealt with the import but not the question.

Revision history for this message
开阖软件 Jeff Wang (jeff.osbzr.com) said :
#4

Yes, the import is working for me, many thanks.

I just cannot find the question and update my thanks on that, sorry

Thanks again Tim

Jeff
 ------------------ 原始邮件 ------------------
发件人: "Tim Penhey"<email address hidden>;
发送时间: 2010年11月16日(星期二) 下午5:42
收件人: "wjfonhand"<email address hidden>;

主题: Re: [Question #131740]: Import Status: Pending Review

Your question #131740 on Launchpad Bazaar Integration changed:
https://answers.launchpad.net/launchpad-code/+question/131740

Tim Penhey posted a new comment:
Ah... I think I dealt with the import but not the question.

--
You received this question notification because you are a direct
subscriber of the question.

Revision history for this message
Aaron Bentley (abentley) said :
#5

User reports the issue is solved.