Hi, I just read the submission process page and being a bit new to this, I have some questions. The page states that all the files making up a library should be compressed into a zip file and posted in the Vault upon submission. - Wouldn't it be better to use the Sandbox for this? After all, this seems to be quite the goal of SVN. It would also allow bugfixes who might appear between submission and review. This leads us to the next question. - Does it mean that while the library is in the review queue, it cannot be changed? I understand this is a long process and it would be nice to correct problems which might appear during this time. It would be also sad to stop development too early. Sorry if I ask stuff which is already broadly known. Christophe
----- Original Message ----- From: "Christophe Henry" <christophe.j.henry@googlemail.com> To: <boost@lists.boost.org> Sent: Sunday, February 01, 2009 11:36 PM Subject: [boost] Review process question
Hi,
I just read the submission process page and being a bit new to this, I have some questions. The page states that all the files making up a library should be compressed into a zip file and posted in the Vault upon submission. - Wouldn't it be better to use the Sandbox for this? After all, this seems to be quite the goal of SVN. It would also allow bugfixes who might appear between submission and review. This leads us to the next question. - Does it mean that while the library is in the review queue, it cannot be changed? I understand this is a long process and it would be nice to correct problems which might appear during this time. It would be also sad to stop development too early.
Sorry if I ask stuff which is already broadly known.
Hi, The library under review needs to be a fixed one, stored in a compressed file in the Vault or elsewhere. This do not means that you can not use the Sandbox to do your developement even during the code review. Of course it could be good to show to the reviewers how you are taking in account his remarks on the Sandbox but what will be more important is to show it on this ML. Just my opinion, Vicente
On Mon, Feb 2, 2009 at 12:06 AM, vicente.botet <vicente.botet@wanadoo.fr> wrote:
The library under review needs to be a fixed one, stored in a compressed file in the Vault or elsewhere.
Using subversion there is still no need to do anything special with the code to be reviewed. It is enough to specify which revision that is to be reviewed. Tagging this revision is a good idea, but not necessary. It is easier to keep up to date with changes, and to see what has been changed, if the trunk is used. /$
participants (3)
-
Christophe Henry -
Henrik Sundberg -
vicente.botet