Am 20.04.2017 um 18:51 schrieb Andrea Pescetti:
On 19/04/2017 Marcus wrote:
2. Major version (X.y.z)
But for this it's not working. Here we first need to agree at which
point we create a new branch from trunk that will be used for a new
major release.
We never release from trunk.
please read
Am 19.04.2017 um 20:52 schrieb Marcus:
> Am 19.04.2017 um 11:26 schrieb Matthias Seidel:
>> Thank you!
>>
>> But as I understand it, the SVN tag is done after the (last) RC is
>> promoted to be final. (That is the point where we know the Revision to
>> checkout). So it should be further down in the
On 19/04/2017 Marcus wrote:
2. Major version (X.y.z)
But for this it's not working. Here we first need to agree at which
point we create a new branch from trunk that will be used for a new
major release.
We never release from trunk. The initial step when considering a new
release is: the relea
Am 19.04.2017 um 11:26 schrieb Matthias Seidel:
Thank you!
But as I understand it, the SVN tag is done after the (last) RC is
promoted to be final. (That is the point where we know the Revision to
checkout). So it should be further down in the documentation.
ah, yes, please see my answer to An
Am 19.04.2017 um 18:18 schrieb Andrea Pescetti:
Matthias Seidel wrote:
But as I understand it, the SVN tag is done after the (last) RC is
promoted to be final. (That is the point where we know the Revision to
checkout). So it should be further down in the documentation.
Correct. It happens aft
Am 19.04.2017 um 18:18 schrieb Andrea Pescetti:
> Matthias Seidel wrote:
>> But as I understand it, the SVN tag is done after the (last) RC is
>> promoted to be final. (That is the point where we know the Revision to
>> checkout). So it should be further down in the documentation.
>
> Correct. It h
Matthias Seidel wrote:
But as I understand it, the SVN tag is done after the (last) RC is
promoted to be final. (That is the point where we know the Revision to
checkout). So it should be further down in the documentation.
Correct. It happens after a successful vote, and the tag is done
retroa
Hi Marcus,
Thank you!
But as I understand it, the SVN tag is done after the (last) RC is
promoted to be final. (That is the point where we know the Revision to
checkout). So it should be further down in the documentation.
A little story:
Until recently "heise Download" [1] offered only AOO 4.1.
Am 10.04.2017 um 20:38 schrieb Marcus:
Thanks for this. My intention was not to get answers to the questions.
They were more ment as rough ideas for what could be added to the cook
book. ;-)
However, I'll take them for addition, but not before Easter.
I've added the topics now to the cook book
Thanks for this. My intention was not to get answers to the questions.
They were more ment as rough ideas for what could be added to the cook
book. ;-)
However, I'll take them for addition, but not before Easter.
Marcus
Am 08.04.2017 um 10:28 schrieb Andrea Pescetti:
On 07/04/2017 Marcus w
On 07/04/2017 Marcus wrote:
Am 06.04.2017 um 00:11 schrieb Patricia Shanahan:
If it needs to be done early, put it early in the document.
Tagging is not to be done early. We tag retroactively, once a RC is
approved.
I don't care about the Github mirror very much, since it is unofficial,
po
Am 06.04.2017 um 18:54 schrieb Matthias Seidel:
Am 06.04.2017 um 00:01 schrieb Marcus:
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
Am 06.04.2017 um 00:11 schrieb Patricia Shanahan:
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
Am 06.04.2017 um 00:01 schrieb Marcus:
> 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
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 secti
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
Hello all!
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
@Andrea: I see
17 matches
Mail list logo
