How get code upstreamed to OpenOffice.org
Contributing code to the OpenOffice.org repository is not easy, there are a lot of rules to follow.
In the past there were again questions about these rules like:
pin). I as the Release Manager for the current code line look into many child workspaces and look if a owner of a child workspace needs help or even more control. The good news is that most people involved in this are pretty good in understanding our goals and apply to the rules as needed. If there are questions left please don't hesitate to ask your project leads for guidance or help to get your child workspace finally integrated.
So the answer to the two above questions is a "no, but ...".
- Have really all child workspaces passed this rules ?
- Do I have to comply with all these rules, I only have just a small change to make ?
- keep the quality of the build, meaning we are everytime able to release
- keep integration of new or changed code smooth, don't break the build
- These rules can't ensure that no failures will happen at reasonable cost
- Understanding the objectives of these rules help to avoid integration failures
pin). I as the Release Manager for the current code line look into many child workspaces and look if a owner of a child workspace needs help or even more control. The good news is that most people involved in this are pretty good in understanding our goals and apply to the rules as needed. If there are questions left please don't hesitate to ask your project leads for guidance or help to get your child workspace finally integrated.
So the answer to the two above questions is a "no, but ...".