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: [email protected] > For additional commands, e-mail: [email protected] > >
smime.p7s
Description: S/MIME Cryptographic Signature
