NOTE: This is not question about the whole testing & release management stuff on that /other/ thread. Since I'm going to be mucking about with Buildbot this weekend I'm wondering about where to put things in the SVN repo. Instead of continuing to shove stuff into the boost-root/tools tree, I'd rather move some of the testing infrastructure tools onto their own tree as we did with the beta web site. The goal, as with the web site, is to make it easier to develop without getting in the way of the release content. In particular because like the web site, testing doesn't follow the same release schedule as the libraries. The obvious location I have in mind is a top level testing dir, with subdirs as needed: svn/testing svn/testing/buildbot svn/testing/reports ... Thoughts? ...I'll assume this is OK after a short time. And move stuff around/back if people object. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo
on Fri Aug 03 2007, Rene Rivera <grafikrobot-AT-gmail.com> wrote:
NOTE: This is not question about the whole testing & release management stuff on that /other/ thread.
Since I'm going to be mucking about with Buildbot this weekend I'm wondering about where to put things in the SVN repo. Instead of continuing to shove stuff into the boost-root/tools tree, I'd rather move some of the testing infrastructure tools onto their own tree as we did with the beta web site. The goal, as with the web site, is to make it easier to develop without getting in the way of the release content. In particular because like the web site, testing doesn't follow the same release schedule as the libraries. The obvious location I have in mind is a top level testing dir, with subdirs as needed:
svn/testing svn/testing/buildbot svn/testing/reports ...
Thoughts?
If we're going to go that way, let's move all of tools/ at once. I suggest you stick your stuff under tools/ until we do that. It doesn't make sense to scatter our tools, does it? -- Dave Abrahams Boost Consulting http://www.boost-consulting.com The Astoria Seminar ==> http://www.astoriaseminar.com
David Abrahams wrote:
on Fri Aug 03 2007, Rene Rivera <grafikrobot-AT-gmail.com> wrote:
NOTE: This is not question about the whole testing & release management stuff on that /other/ thread.
Since I'm going to be mucking about with Buildbot this weekend I'm wondering about where to put things in the SVN repo. Instead of continuing to shove stuff into the boost-root/tools tree, I'd rather move some of the testing infrastructure tools onto their own tree as we did with the beta web site. The goal, as with the web site, is to make it easier to develop without getting in the way of the release content. In particular because like the web site, testing doesn't follow the same release schedule as the libraries. The obvious location I have in mind is a top level testing dir, with subdirs as needed:
svn/testing svn/testing/buildbot svn/testing/reports ...
Thoughts?
If we're going to go that way, let's move all of tools/ at once. I suggest you stick your stuff under tools/ until we do that. It doesn't make sense to scatter our tools, does it?
OK, so svn/tools/testing/* for now. Only problem is that I don't have the permission to create such a top level directory in svn. I get: CHECKOUT of '/svn/boost/!svn/ver/38432/": 403 Forbidden... -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo
on Fri Aug 03 2007, Rene Rivera <grafikrobot-AT-gmail.com> wrote:
David Abrahams wrote:
on Fri Aug 03 2007, Rene Rivera <grafikrobot-AT-gmail.com> wrote:
NOTE: This is not question about the whole testing & release management stuff on that /other/ thread.
Since I'm going to be mucking about with Buildbot this weekend I'm wondering about where to put things in the SVN repo. Instead of continuing to shove stuff into the boost-root/tools tree, I'd rather move some of the testing infrastructure tools onto their own tree as we did with the beta web site. The goal, as with the web site, is to make it easier to develop without getting in the way of the release content. In particular because like the web site, testing doesn't follow the same release schedule as the libraries. The obvious location I have in mind is a top level testing dir, with subdirs as needed:
svn/testing svn/testing/buildbot svn/testing/reports ...
Thoughts?
If we're going to go that way, let's move all of tools/ at once. I suggest you stick your stuff under tools/ until we do that. It doesn't make sense to scatter our tools, does it?
OK, so svn/tools/testing/* for now. Only problem is that I don't have the permission to create such a top level directory in svn. I get:
CHECKOUT of '/svn/boost/!svn/ver/38432/": 403 Forbidden...
I don't think I have the power to change that. Doug, is the authz file in the repo someplace that the mods can have r/w access to it? I've always thought the ideal arrangement would do something like that, with a post-commit hook that updates the actual authz file in use on the server. -- Dave Abrahams Boost Consulting http://www.boost-consulting.com The Astoria Seminar ==> http://www.astoriaseminar.com
participants (2)
-
David Abrahams -
Rene Rivera