If it needs to be done early, put it early in the document.
In general, what needs doing should drive the form of the "How to Cook a
Release" document. If the current form does not accommodate a necessary
step, change it. The objective is to have a complete recipe.
We currently have two sections, "Initiating a Release" and "Planning"
that discuss things that happen before the first build. My feeling is
that this issue belongs in "Initiating a Release", probably as a Release
Manager responsibility, but I would have no objection to a new section
on pre-build preparations if that would fit better.
On 4/5/2017 3:01 PM, Marcus wrote:
Am 05.04.2017 um 15:16 schrieb Matthias Seidel:
I have seen on GitHub:
https://github.com/apache/openoffice/releases
that 4.1.3 (zip/tar.gz) is missing. This seems to be a manual process on
SVN [1], so this step should be added to our cWiki:
https://cwiki.apache.org/confluence/display/OOOUSERS/How+to+Cook+a+Release
at the moment I don't see where this piece could fit. The release tag
has to be done long, long before a release build has to be started.
In general, there is no description what and how something in AOO code
has to be done in SVN as it is too special.
Or do you have an idea?
@Andrea: I see you did it for 4.1.1 and 4.1.2. Can this "tag" still be
done for 4.1.3?
[1] https://svn.apache.org/viewvc/openoffice/tags/?pathrev=1754537
Yes, please.
Marcus
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
