Michał Minicki wrote:
I vote for keeping the docs in LINKED external svn. So anyone who
wants to get the manual in fact can get it painlessly. Be it deployment
or any other need.
I'd like to do that. My recollection is that Darby and Gavin and I
looked at this issue in November and could not come up with a good
solution for modularizing the tree without creating a lot of work.
The purpose of revision control is configuration management, not only
release management. Every software engineering methodology counts
configuration management as crucial for the success of any project.
This is especially true for open-source projects. So in my view it's an
absolute requirement that we can track code and docs in sync. If we can
do that through svn externals, that'd be great.
I'll do some tests to see if there is a solution that will satisfy both
modularization and configuration management.
Please try to understand me too -- It's not that setting it up is
technically difficult, it's the ongoing maintenance that I'm more
concerned about. We have no dedicated config management administrator on
this project. We have no dedicated documentation team (except for the
translators). We, the developers, need to manage the infrastructure,
and any additional complexity in the infrastructure means time taken
away from development. It is very clear that finishing the
implementation of Zend Framework 1.0 is the highest priority. We have
to be extremely conservative about how much time we invest into
developing and managing the infrastructure. That may mean that there
are some tools and practices that we simply cannot afford.
But I agree that some types of infrastructure management can benefit us
with greater productivity toward finishing development of ZF 1.0. So I
will look into finding an svn externals solution.
Regards,
Bill Karwin
- Re: [fw-general] Remove demos from svn? Bill Karwin
-
