Pete,<br><br>We followed a similar process at my last company. We found that freezing anything right before a release was not practical.<br><br>We would release the product with included English docs. Where it differs from your plan is that we did not do a follow up release - unless needed for critical bugs. The docs team worked off the tagged rev so that they were always translating the same version as the release. The dev branch was never actually frozen. When the docs were finished we posted the translated documentation on our website. In the original release we had links and information discussing the translated docs and where they could be found.<br>
<br>Both approaches have there benefits, but I would suggest we do something like this because I think that it will free more time for other tasks. <br><br>Obviously I could go either way though.<br><br>Jay<br><br><div class="gmail_quote">
On Thu, Mar 27, 2008 at 5:39 AM, Pete Muir <<a href="mailto:pmuir@bleepbleep.org.uk">pmuir@bleepbleep.org.uk</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Samson,<br>
<br>
You've previously raised the issue of how we allow the JBoss Content<br>
Team to work on translation/documentation and requested that we freeze<br>
the documentation approximately 2 weeks before we release.<br>
<br>
Having thought about this some, we don't think that this is really<br>
practical. So here is our alternative proposal:<br>
<br>
1) We release Seam <a href="http://X.Y.Z.GA" target="_blank">X.Y.Z.GA</a> with the English docs as prepared by Seam<br>
committers. This allows users quick access to the code and also to<br>
updated docs<br>
<br>
2) We freeze this branch for around 2 - 3 weeks except for any<br>
critical code fixes and documentation/translation work<br>
<br>
3) We then release Seam X.Y.Z.SP1 with any critical fixes and translations<br>
<br>
Jay,<br>
<br>
This obviously increases the QA/release managers load so I propose<br>
that only extremely critical fixes make it into the code, examples or<br>
seam-gen. As the release testing and process is increasingly automated<br>
this should become easier. What do you think?<br>
<br>
Pete<br>
<font color="#888888"><br>
--<br>
Pete Muir<br>
<a href="http://in.relation.to/Bloggers/Pete" target="_blank">http://in.relation.to/Bloggers/Pete</a><br>
<a href="http://www.seamframework.org" target="_blank">http://www.seamframework.org</a><br>
_______________________________________________<br>
seam-dev mailing list<br>
<a href="mailto:seam-dev@lists.jboss.org">seam-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/seam-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
</font></blockquote></div><br>