[GitHub] Missing tag for 4.1.3 release

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
17 messages Options
Reply | Threaded
Open this post in threaded view
|

[GitHub] Missing tag for 4.1.3 release

Matthias Seidel
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 you did it for 4.1.1 and 4.1.2. Can this "tag" still be
done for 4.1.3?

Kind regards, Matthias

[1] https://svn.apache.org/viewvc/openoffice/tags/?pathrev=1754537



smime.p7s (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: [GitHub] Missing tag for 4.1.3 release

Marcus (OOo)
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: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [GitHub] Missing tag for 4.1.3 release

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 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: [hidden email]
> For additional commands, e-mail: [hidden email]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [GitHub] Missing tag for 4.1.3 release

Matthias Seidel
In reply to this post by Marcus (OOo)
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:

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?

Hi Marcus,

I think it is the counterpart of opening a branch. Some kind of "code checkout" when the last RC is promoted to be final.
In case of 4.1.3 it would be SVN r1761381?

So it would fit in "Uploads" after "Release Vote"
But maybe Andrea has a better explanation what this procedure is for.

Matthias


@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: [hidden email]
For additional commands, e-mail: [hidden email]




smime.p7s (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: [GitHub] Missing tag for 4.1.3 release

Marcus (OOo)
In reply to this post by Patricia Shanahan
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 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.

then I think this makes most sense. Let's create a new section like
"Build Preparations" and put the following stuff (and more, of course)
there:

- How to create new SVN tag?
- How to check out code?
- How to do a build with release options?
- Where/How to upload pre-build releases?

Thanks

Marcus



> 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: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [GitHub] Missing tag for 4.1.3 release

Marcus (OOo)
In reply to this post by Matthias Seidel
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 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?
>
> Hi Marcus,
>
> I think it is the counterpart of opening a branch. Some kind of "code
> checkout" when the last RC is promoted to be final.
> In case of 4.1.3 it would be SVN r1761381?
>
> So it would fit in "Uploads" after "Release Vote"
> But maybe Andrea has a better explanation what this procedure is for.

IMHO has made the best suggestions. See my answer there.

Marcus



>>> @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: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [GitHub] Missing tag for 4.1.3 release

Andrea Pescetti-2
In reply to this post by Marcus (OOo)
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,
poorly maintained, it shows wrong numbers and it even stopped working
for many months last year. That said, the issue Matthias raised affect
SVN too, so it is still relevant:

http://svn.apache.org/viewvc/openoffice/tags/

Also note: Github "releases" based on tags are not the same as our
official releases; it's the same source code of course, but there are
minor packaging details. So the Github releases in themselves (like the
Github repository overall) have no value. Ask me to expand if this is
unclear.

> Let's create a new section like
> "Build Preparations" and put the following stuff (and more, of course)
> there:
> - How to create new SVN tag?

Again, this happens retroactively, when a specific RC is voted. At that
point, you simply SVN copy the branch to the tag.

How do you do this?

1. Double-check what version was built (for 4.1.3 it's Rev. 1761381, you
find it even in the About Box); of course, if this happens during the
release process, the Release Manager knows it.

2. Find the relevant branch in
http://svn.apache.org/viewvc/openoffice/branches/ (in this case it's
AOO413 and revision number is indeed 1761381) and check it is aligned
(it is, since the two revisions match).

3. SVN copy the branch to the tag. You can do it locally but it's much
more efficient to do it remotely. So, from anywhere on a machine with
SVN access, just run:

$ svn copy https://svn.apache.org/repos/asf/openoffice/branches/AOO413 
https://svn.apache.org/repos/asf/openoffice/tags/AOO413 -m "AOO revision
1761381 from branch AOO413 was voted to be released as Apache OpenOffice
4.1.3 in October 2016"

Committed revision 1790662.

This results in the new tag appearing at
http://svn.apache.org/viewvc/openoffice/tags/ (while at it I fixed the
missing 4.1.3 tag, so I did run the command above).

> - How to check out code?

Just "svn checkout" the relevant branch. Starting with 4.1.3 we have
been using dedicated branches, so naming is now obvious (we had been
reusing branches in precedence, like AOO410 was used for 4.1.0, 4.1.1
and 4.1.2). Branches are listed at
http://svn.apache.org/viewvc/openoffice/branches/

So:

$ svn checkout https://svn.apache.org/repos/asf/openoffice/branches/AOO413

> - How to do a build with release options?

Use the scripts at
http://svn.apache.org/viewvc/openoffice/devtools/build-scripts/

The 4.1.2 scripts are correct, for 4.1.3 it is unreliable since people
uploaded there scripts that were not used for building. See

https://lists.apache.org/thread.html/96b7085351f7ab7975ac56c5bc7c42852b8a888da53e0a67864d3396@%3Cdev.openoffice.apache.org%3E

> - Where/How to upload pre-build releases?

When they are RCs, they belong in the dev area. See

https://lists.apache.org/thread.html/05d175d207b2bdc1ed83c8c4884630e91663a953daf12fe8612e98c5@%3Cdev.openoffice.apache.org%3E

Regards,
   Andrea.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [GitHub] Missing tag for 4.1.3 release

Marcus (OOo)
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 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,
> poorly maintained, it shows wrong numbers and it even stopped working
> for many months last year. That said, the issue Matthias raised affect
> SVN too, so it is still relevant:
>
> http://svn.apache.org/viewvc/openoffice/tags/
>
> Also note: Github "releases" based on tags are not the same as our
> official releases; it's the same source code of course, but there are
> minor packaging details. So the Github releases in themselves (like the
> Github repository overall) have no value. Ask me to expand if this is
> unclear.
>
>> Let's create a new section like
>> "Build Preparations" and put the following stuff (and more, of course)
>> there:
>> - How to create new SVN tag?
>
> Again, this happens retroactively, when a specific RC is voted. At that
> point, you simply SVN copy the branch to the tag.
>
> How do you do this?
>
> 1. Double-check what version was built (for 4.1.3 it's Rev. 1761381, you
> find it even in the About Box); of course, if this happens during the
> release process, the Release Manager knows it.
>
> 2. Find the relevant branch in
> http://svn.apache.org/viewvc/openoffice/branches/ (in this case it's
> AOO413 and revision number is indeed 1761381) and check it is aligned
> (it is, since the two revisions match).
>
> 3. SVN copy the branch to the tag. You can do it locally but it's much
> more efficient to do it remotely. So, from anywhere on a machine with
> SVN access, just run:
>
> $ svn copy https://svn.apache.org/repos/asf/openoffice/branches/AOO413
> https://svn.apache.org/repos/asf/openoffice/tags/AOO413 -m "AOO revision
> 1761381 from branch AOO413 was voted to be released as Apache OpenOffice
> 4.1.3 in October 2016"
>
> Committed revision 1790662.
>
> This results in the new tag appearing at
> http://svn.apache.org/viewvc/openoffice/tags/ (while at it I fixed the
> missing 4.1.3 tag, so I did run the command above).
>
>> - How to check out code?
>
> Just "svn checkout" the relevant branch. Starting with 4.1.3 we have
> been using dedicated branches, so naming is now obvious (we had been
> reusing branches in precedence, like AOO410 was used for 4.1.0, 4.1.1
> and 4.1.2). Branches are listed at
> http://svn.apache.org/viewvc/openoffice/branches/
>
> So:
>
> $ svn checkout https://svn.apache.org/repos/asf/openoffice/branches/AOO413
>
>> - How to do a build with release options?
>
> Use the scripts at
> http://svn.apache.org/viewvc/openoffice/devtools/build-scripts/
>
> The 4.1.2 scripts are correct, for 4.1.3 it is unreliable since people
> uploaded there scripts that were not used for building. See
>
> https://lists.apache.org/thread.html/96b7085351f7ab7975ac56c5bc7c42852b8a888da53e0a67864d3396@%3Cdev.openoffice.apache.org%3E
>
>
>> - Where/How to upload pre-build releases?
>
> When they are RCs, they belong in the dev area. See
>
> https://lists.apache.org/thread.html/05d175d207b2bdc1ed83c8c4884630e91663a953daf12fe8612e98c5@%3Cdev.openoffice.apache.org%3E
>
>
> Regards,
>   Andrea.


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [GitHub] Missing tag for 4.1.3 release

Marcus (OOo)
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 [1] and incorporated them
into the "Initiating a Release" section. After looking twice they seem
to fit very well there.

[1]
https://cwiki.apache.org/confluence/display/OOOUSERS/How+to+Cook+a+Release

Marcus



> Am 08.04.2017 um 10:28 schrieb Andrea Pescetti:
>> 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,
>> poorly maintained, it shows wrong numbers and it even stopped working
>> for many months last year. That said, the issue Matthias raised affect
>> SVN too, so it is still relevant:
>>
>> http://svn.apache.org/viewvc/openoffice/tags/
>>
>> Also note: Github "releases" based on tags are not the same as our
>> official releases; it's the same source code of course, but there are
>> minor packaging details. So the Github releases in themselves (like the
>> Github repository overall) have no value. Ask me to expand if this is
>> unclear.
>>
>>> Let's create a new section like
>>> "Build Preparations" and put the following stuff (and more, of course)
>>> there:
>>> - How to create new SVN tag?
>>
>> Again, this happens retroactively, when a specific RC is voted. At that
>> point, you simply SVN copy the branch to the tag.
>>
>> How do you do this?
>>
>> 1. Double-check what version was built (for 4.1.3 it's Rev. 1761381, you
>> find it even in the About Box); of course, if this happens during the
>> release process, the Release Manager knows it.
>>
>> 2. Find the relevant branch in
>> http://svn.apache.org/viewvc/openoffice/branches/ (in this case it's
>> AOO413 and revision number is indeed 1761381) and check it is aligned
>> (it is, since the two revisions match).
>>
>> 3. SVN copy the branch to the tag. You can do it locally but it's much
>> more efficient to do it remotely. So, from anywhere on a machine with
>> SVN access, just run:
>>
>> $ svn copy https://svn.apache.org/repos/asf/openoffice/branches/AOO413
>> https://svn.apache.org/repos/asf/openoffice/tags/AOO413 -m "AOO revision
>> 1761381 from branch AOO413 was voted to be released as Apache OpenOffice
>> 4.1.3 in October 2016"
>>
>> Committed revision 1790662.
>>
>> This results in the new tag appearing at
>> http://svn.apache.org/viewvc/openoffice/tags/ (while at it I fixed the
>> missing 4.1.3 tag, so I did run the command above).
>>
>>> - How to check out code?
>>
>> Just "svn checkout" the relevant branch. Starting with 4.1.3 we have
>> been using dedicated branches, so naming is now obvious (we had been
>> reusing branches in precedence, like AOO410 was used for 4.1.0, 4.1.1
>> and 4.1.2). Branches are listed at
>> http://svn.apache.org/viewvc/openoffice/branches/
>>
>> So:
>>
>> $ svn checkout
>> https://svn.apache.org/repos/asf/openoffice/branches/AOO413
>>
>>> - How to do a build with release options?
>>
>> Use the scripts at
>> http://svn.apache.org/viewvc/openoffice/devtools/build-scripts/
>>
>> The 4.1.2 scripts are correct, for 4.1.3 it is unreliable since people
>> uploaded there scripts that were not used for building. See
>>
>> https://lists.apache.org/thread.html/96b7085351f7ab7975ac56c5bc7c42852b8a888da53e0a67864d3396@%3Cdev.openoffice.apache.org%3E
>>
>>
>>
>>> - Where/How to upload pre-build releases?
>>
>> When they are RCs, they belong in the dev area. See
>>
>> https://lists.apache.org/thread.html/05d175d207b2bdc1ed83c8c4884630e91663a953daf12fe8612e98c5@%3Cdev.openoffice.apache.org%3E


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [GitHub] Missing tag for 4.1.3 release

Matthias Seidel
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.2.
Andrea did the SVN tag on Saturday, 8. April. On Monday, 10. April heise
updated their page to AOO 4.1.3.
So I think, they monitor the tags either on GitHub or SVN to see if a
new version is available.

[1] https://www.heise.de/download/product/openoffice-9375

Regards, Matthias


Am 17.04.2017 um 16:18 schrieb Marcus:

> 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 [1] and incorporated them
> into the "Initiating a Release" section. After looking twice they seem
> to fit very well there.
>
> [1]
> https://cwiki.apache.org/confluence/display/OOOUSERS/How+to+Cook+a+Release
>
> Marcus
>
>
>
>> Am 08.04.2017 um 10:28 schrieb Andrea Pescetti:
>>> 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,
>>> poorly maintained, it shows wrong numbers and it even stopped working
>>> for many months last year. That said, the issue Matthias raised affect
>>> SVN too, so it is still relevant:
>>>
>>> http://svn.apache.org/viewvc/openoffice/tags/
>>>
>>> Also note: Github "releases" based on tags are not the same as our
>>> official releases; it's the same source code of course, but there are
>>> minor packaging details. So the Github releases in themselves (like the
>>> Github repository overall) have no value. Ask me to expand if this is
>>> unclear.
>>>
>>>> Let's create a new section like
>>>> "Build Preparations" and put the following stuff (and more, of course)
>>>> there:
>>>> - How to create new SVN tag?
>>>
>>> Again, this happens retroactively, when a specific RC is voted. At that
>>> point, you simply SVN copy the branch to the tag.
>>>
>>> How do you do this?
>>>
>>> 1. Double-check what version was built (for 4.1.3 it's Rev. 1761381,
>>> you
>>> find it even in the About Box); of course, if this happens during the
>>> release process, the Release Manager knows it.
>>>
>>> 2. Find the relevant branch in
>>> http://svn.apache.org/viewvc/openoffice/branches/ (in this case it's
>>> AOO413 and revision number is indeed 1761381) and check it is aligned
>>> (it is, since the two revisions match).
>>>
>>> 3. SVN copy the branch to the tag. You can do it locally but it's much
>>> more efficient to do it remotely. So, from anywhere on a machine with
>>> SVN access, just run:
>>>
>>> $ svn copy https://svn.apache.org/repos/asf/openoffice/branches/AOO413
>>> https://svn.apache.org/repos/asf/openoffice/tags/AOO413 -m "AOO
>>> revision
>>> 1761381 from branch AOO413 was voted to be released as Apache
>>> OpenOffice
>>> 4.1.3 in October 2016"
>>>
>>> Committed revision 1790662.
>>>
>>> This results in the new tag appearing at
>>> http://svn.apache.org/viewvc/openoffice/tags/ (while at it I fixed the
>>> missing 4.1.3 tag, so I did run the command above).
>>>
>>>> - How to check out code?
>>>
>>> Just "svn checkout" the relevant branch. Starting with 4.1.3 we have
>>> been using dedicated branches, so naming is now obvious (we had been
>>> reusing branches in precedence, like AOO410 was used for 4.1.0, 4.1.1
>>> and 4.1.2). Branches are listed at
>>> http://svn.apache.org/viewvc/openoffice/branches/
>>>
>>> So:
>>>
>>> $ svn checkout
>>> https://svn.apache.org/repos/asf/openoffice/branches/AOO413
>>>
>>>> - How to do a build with release options?
>>>
>>> Use the scripts at
>>> http://svn.apache.org/viewvc/openoffice/devtools/build-scripts/
>>>
>>> The 4.1.2 scripts are correct, for 4.1.3 it is unreliable since people
>>> uploaded there scripts that were not used for building. See
>>>
>>> https://lists.apache.org/thread.html/96b7085351f7ab7975ac56c5bc7c42852b8a888da53e0a67864d3396@%3Cdev.openoffice.apache.org%3E
>>>
>>>
>>>
>>>
>>>> - Where/How to upload pre-build releases?
>>>
>>> When they are RCs, they belong in the dev area. See
>>>
>>> https://lists.apache.org/thread.html/05d175d207b2bdc1ed83c8c4884630e91663a953daf12fe8612e98c5@%3Cdev.openoffice.apache.org%3E
>>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>


smime.p7s (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: [GitHub] Missing tag for 4.1.3 release

Andrea Pescetti-2
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
retroactively (but usually a few hours/days later, not six months later
as it happened this time!).

> Until recently "heise Download" [1] offered only AOO 4.1.2.
> Andrea did the SVN tag on Saturday, 8. April. On Monday, 10. April heise
> updated their page to AOO 4.1.3.

As said, this Github mirror is unreliable and it contains a lot of wrong
things. I hope nobody relies on it without being aware of its limitations.

Regards,
   Andrea.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [GitHub] Missing tag for 4.1.3 release

Matthias Seidel
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 after a successful vote, and the tag is done
> retroactively (but usually a few hours/days later, not six months
> later as it happened this time!).
>
>> Until recently "heise Download" [1] offered only AOO 4.1.2.
>> Andrea did the SVN tag on Saturday, 8. April. On Monday, 10. April heise
>> updated their page to AOO 4.1.3.
>
> As said, this Github mirror is unreliable and it contains a lot of
> wrong things. I hope nobody relies on it without being aware of its
> limitations.
No, I think they only monitor it (or SVN) for updates.

Regards, Matthias

>
> Regards,
>   Andrea.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>



smime.p7s (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: [GitHub] Missing tag for 4.1.3 release

Marcus (OOo)
In reply to this post by Matthias Seidel
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 Andrea's mail.

> A little story:
>
> Until recently "heise Download" [1] offered only AOO 4.1.2.
> Andrea did the SVN tag on Saturday, 8. April. On Monday, 10. April heise
> updated their page to AOO 4.1.3.
> So I think, they monitor the tags either on GitHub or SVN to see if a
> new version is available.
>
> [1] https://www.heise.de/download/product/openoffice-9375

Then I really hope they have learned from this error. Sure, Apache
software is in the very most cases the source code itself and not the
binaries - when there are any at all. But for OpenOffice it's different.
They should know us long enough to know this difference.

PS:
It's never forbidden to ask for facts. ;-)

Marcus



> Am 17.04.2017 um 16:18 schrieb Marcus:
>> 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 [1] and incorporated them
>> into the "Initiating a Release" section. After looking twice they seem
>> to fit very well there.
>>
>> [1]
>> https://cwiki.apache.org/confluence/display/OOOUSERS/How+to+Cook+a+Release
>>
>> Marcus
>>
>>
>>
>>> Am 08.04.2017 um 10:28 schrieb Andrea Pescetti:
>>>> 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,
>>>> poorly maintained, it shows wrong numbers and it even stopped working
>>>> for many months last year. That said, the issue Matthias raised affect
>>>> SVN too, so it is still relevant:
>>>>
>>>> http://svn.apache.org/viewvc/openoffice/tags/
>>>>
>>>> Also note: Github "releases" based on tags are not the same as our
>>>> official releases; it's the same source code of course, but there are
>>>> minor packaging details. So the Github releases in themselves (like the
>>>> Github repository overall) have no value. Ask me to expand if this is
>>>> unclear.
>>>>
>>>>> Let's create a new section like
>>>>> "Build Preparations" and put the following stuff (and more, of course)
>>>>> there:
>>>>> - How to create new SVN tag?
>>>>
>>>> Again, this happens retroactively, when a specific RC is voted. At that
>>>> point, you simply SVN copy the branch to the tag.
>>>>
>>>> How do you do this?
>>>>
>>>> 1. Double-check what version was built (for 4.1.3 it's Rev. 1761381,
>>>> you
>>>> find it even in the About Box); of course, if this happens during the
>>>> release process, the Release Manager knows it.
>>>>
>>>> 2. Find the relevant branch in
>>>> http://svn.apache.org/viewvc/openoffice/branches/ (in this case it's
>>>> AOO413 and revision number is indeed 1761381) and check it is aligned
>>>> (it is, since the two revisions match).
>>>>
>>>> 3. SVN copy the branch to the tag. You can do it locally but it's much
>>>> more efficient to do it remotely. So, from anywhere on a machine with
>>>> SVN access, just run:
>>>>
>>>> $ svn copy https://svn.apache.org/repos/asf/openoffice/branches/AOO413
>>>> https://svn.apache.org/repos/asf/openoffice/tags/AOO413 -m "AOO
>>>> revision
>>>> 1761381 from branch AOO413 was voted to be released as Apache
>>>> OpenOffice
>>>> 4.1.3 in October 2016"
>>>>
>>>> Committed revision 1790662.
>>>>
>>>> This results in the new tag appearing at
>>>> http://svn.apache.org/viewvc/openoffice/tags/ (while at it I fixed the
>>>> missing 4.1.3 tag, so I did run the command above).
>>>>
>>>>> - How to check out code?
>>>>
>>>> Just "svn checkout" the relevant branch. Starting with 4.1.3 we have
>>>> been using dedicated branches, so naming is now obvious (we had been
>>>> reusing branches in precedence, like AOO410 was used for 4.1.0, 4.1.1
>>>> and 4.1.2). Branches are listed at
>>>> http://svn.apache.org/viewvc/openoffice/branches/
>>>>
>>>> So:
>>>>
>>>> $ svn checkout
>>>> https://svn.apache.org/repos/asf/openoffice/branches/AOO413
>>>>
>>>>> - How to do a build with release options?
>>>>
>>>> Use the scripts at
>>>> http://svn.apache.org/viewvc/openoffice/devtools/build-scripts/
>>>>
>>>> The 4.1.2 scripts are correct, for 4.1.3 it is unreliable since people
>>>> uploaded there scripts that were not used for building. See
>>>>
>>>> https://lists.apache.org/thread.html/96b7085351f7ab7975ac56c5bc7c42852b8a888da53e0a67864d3396@%3Cdev.openoffice.apache.org%3E
>>>>
>>>>
>>>>
>>>>
>>>>> - Where/How to upload pre-build releases?
>>>>
>>>> When they are RCs, they belong in the dev area. See
>>>>
>>>> https://lists.apache.org/thread.html/05d175d207b2bdc1ed83c8c4884630e91663a953daf12fe8612e98c5@%3Cdev.openoffice.apache.org%3E


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [GitHub] Missing tag for 4.1.3 release

Marcus (OOo)
In reply to this post by Andrea Pescetti-2
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 after a successful vote, and the tag is done
> retroactively (but usually a few hours/days later, not six months later
> as it happened this time!).

before changing the documentation I want to clarify the following:

OK, but then we need to make a difference which version type we are
talking about.

1. Mirco (x.y.Z) or minor version (x.Y.z)

This may work as we continue the work on an already branched code. So,
it's OK to do some hacking until the final release and then to tag the
specific SVN revision.

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.

As our last major release is long ago, it's not that common in our
processes. ;-)

Marcus


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [GitHub] Missing tag for 4.1.3 release

Andrea Pescetti-2
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 release manager creates a dedicated branch (say, AOO420
or AOO500). Then the release is still a "tag" on that branch, exactly
the same as we did for the AOO413 branch for OpenOffice 4.1.3.

So, in short: creating the branch is one of the first steps; creating
the tag is one of the last steps.

Regards,
   Andrea.


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [GitHub] Missing tag for 4.1.3 release

Matthias Seidel
In reply to this post by Marcus (OOo)
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 documentation.
>
> ah, yes, please see my answer to Andrea's mail.
>
>> A little story:
>>
>> Until recently "heise Download" [1] offered only AOO 4.1.2.
>> Andrea did the SVN tag on Saturday, 8. April. On Monday, 10. April heise
>> updated their page to AOO 4.1.3.
>> So I think, they monitor the tags either on GitHub or SVN to see if a
>> new version is available.
>>
>> [1] https://www.heise.de/download/product/openoffice-9375
>
> Then I really hope they have learned from this error. Sure, Apache
> software is in the very most cases the source code itself and not the
> binaries - when there are any at all. But for OpenOffice it's
> different. They should know us long enough to know this difference.
>
> PS:
> It's never forbidden to ask for facts. ;-)
Heise has been a good source for information... 20 years ago...
Now they are not relevant anymore.

Matthias

>
> Marcus
>
>
>
>> Am 17.04.2017 um 16:18 schrieb Marcus:
>>> 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 [1] and incorporated them
>>> into the "Initiating a Release" section. After looking twice they seem
>>> to fit very well there.
>>>
>>> [1]
>>> https://cwiki.apache.org/confluence/display/OOOUSERS/How+to+Cook+a+Release
>>>
>>>
>>> Marcus
>>>
>>>
>>>
>>>> Am 08.04.2017 um 10:28 schrieb Andrea Pescetti:
>>>>> 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,
>>>>> poorly maintained, it shows wrong numbers and it even stopped working
>>>>> for many months last year. That said, the issue Matthias raised
>>>>> affect
>>>>> SVN too, so it is still relevant:
>>>>>
>>>>> http://svn.apache.org/viewvc/openoffice/tags/
>>>>>
>>>>> Also note: Github "releases" based on tags are not the same as our
>>>>> official releases; it's the same source code of course, but there are
>>>>> minor packaging details. So the Github releases in themselves
>>>>> (like the
>>>>> Github repository overall) have no value. Ask me to expand if this is
>>>>> unclear.
>>>>>
>>>>>> Let's create a new section like
>>>>>> "Build Preparations" and put the following stuff (and more, of
>>>>>> course)
>>>>>> there:
>>>>>> - How to create new SVN tag?
>>>>>
>>>>> Again, this happens retroactively, when a specific RC is voted. At
>>>>> that
>>>>> point, you simply SVN copy the branch to the tag.
>>>>>
>>>>> How do you do this?
>>>>>
>>>>> 1. Double-check what version was built (for 4.1.3 it's Rev. 1761381,
>>>>> you
>>>>> find it even in the About Box); of course, if this happens during the
>>>>> release process, the Release Manager knows it.
>>>>>
>>>>> 2. Find the relevant branch in
>>>>> http://svn.apache.org/viewvc/openoffice/branches/ (in this case it's
>>>>> AOO413 and revision number is indeed 1761381) and check it is aligned
>>>>> (it is, since the two revisions match).
>>>>>
>>>>> 3. SVN copy the branch to the tag. You can do it locally but it's
>>>>> much
>>>>> more efficient to do it remotely. So, from anywhere on a machine with
>>>>> SVN access, just run:
>>>>>
>>>>> $ svn copy
>>>>> https://svn.apache.org/repos/asf/openoffice/branches/AOO413
>>>>> https://svn.apache.org/repos/asf/openoffice/tags/AOO413 -m "AOO
>>>>> revision
>>>>> 1761381 from branch AOO413 was voted to be released as Apache
>>>>> OpenOffice
>>>>> 4.1.3 in October 2016"
>>>>>
>>>>> Committed revision 1790662.
>>>>>
>>>>> This results in the new tag appearing at
>>>>> http://svn.apache.org/viewvc/openoffice/tags/ (while at it I fixed
>>>>> the
>>>>> missing 4.1.3 tag, so I did run the command above).
>>>>>
>>>>>> - How to check out code?
>>>>>
>>>>> Just "svn checkout" the relevant branch. Starting with 4.1.3 we have
>>>>> been using dedicated branches, so naming is now obvious (we had been
>>>>> reusing branches in precedence, like AOO410 was used for 4.1.0, 4.1.1
>>>>> and 4.1.2). Branches are listed at
>>>>> http://svn.apache.org/viewvc/openoffice/branches/
>>>>>
>>>>> So:
>>>>>
>>>>> $ svn checkout
>>>>> https://svn.apache.org/repos/asf/openoffice/branches/AOO413
>>>>>
>>>>>> - How to do a build with release options?
>>>>>
>>>>> Use the scripts at
>>>>> http://svn.apache.org/viewvc/openoffice/devtools/build-scripts/
>>>>>
>>>>> The 4.1.2 scripts are correct, for 4.1.3 it is unreliable since
>>>>> people
>>>>> uploaded there scripts that were not used for building. See
>>>>>
>>>>> https://lists.apache.org/thread.html/96b7085351f7ab7975ac56c5bc7c42852b8a888da53e0a67864d3396@%3Cdev.openoffice.apache.org%3E
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>> - Where/How to upload pre-build releases?
>>>>>
>>>>> When they are RCs, they belong in the dev area. See
>>>>>
>>>>> https://lists.apache.org/thread.html/05d175d207b2bdc1ed83c8c4884630e91663a953daf12fe8612e98c5@%3Cdev.openoffice.apache.org%3E
>>>>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>


smime.p7s (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: [GitHub] Missing tag for 4.1.3 release

Marcus (OOo)
In reply to this post by Andrea Pescetti-2
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 my mail again, I never wrote it that way!

 > The initial step when considering a new
> release is: the release manager creates a dedicated branch (say, AOO420
> or AOO500). Then the release is still a "tag" on that branch, exactly
> the same as we did for the AOO413 branch for OpenOffice 4.1.3.
>
> So, in short: creating the branch is one of the first steps; creating
> the tag is one of the last steps.

Ah, I mixed-up branch and tag. Sure, the tag is coming always much later
than creating a branch.

Marcus


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]