I went ahead and tagged AOO-4.1.6RC1. If it passes then we can copy that tag to the GA.
> On Oct 26, 2018, at 10:56 AM, Matthias Seidel <[email protected]> > wrote: > > Hi Marcus, > > Am 25.10.18 um 23:56 schrieb Marcus: >> Am 25.10.2018 um 23:42 schrieb Andrea Pescetti: >>> On 23/10/2018 Matthias Seidel wrote: >>>> Am 23.10.18 um 13:06 schrieb Jim Jagielski: >>>>> r1844555 was the SVN version of HEAD at the time of the email. >>>> Yes, and it increases by the time of writing... >>>> So it gives no information about what revision the RC should be >>>> build upon? >>> >>> This has always been an issue to the structure of our SVN repository, >>> but fortunately it is only cosmetic. >>> >>> All the ASF projects use the same SVN repository, and the revision >>> number increases (obviously) any time someone commits to any part of >>> the repository. So a commit to another project will increase the >>> overall revision number while the OpenOffice code remains the same. >>> >>> This means there is always a range of SVN HEAD revisions that >>> correspond to the same OpenOffice code. Only running "svn log" in the >>> OpenOffice checkout will tell you the last "real" OpenOffice revision. >> >> isn't this the reason (or one of some) that we put a SVN tag to a >> specific revision, so that all can talk about the same revision for a >> specific release? > > Yes, we tag the final release to "document" that specific revision. > > This was more about clear communicating: > > - when a Release Candidate is to be build > - and what revision it is exactly based on > > Earlier builds/releases were done by one Release Manager only, but now > we are a team of three. > That needs some kind of coordination. > > Matthias > >> >> Marcus >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> <mailto:[email protected]> >> For additional commands, e-mail: [email protected] >> <mailto:[email protected]>
