Re: [VOTE] Release Apache Jackrabbit Oak 1.9.13
[X] +1 Release this package as Apache Jackrabbit Oak 1.9.13 Everything looks good, where: [INFO] Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-04T04:39:06+09:00) [INFO] OS name: "mac os x", version: "10.14.1", arch: "x86_64", family: "mac" [INFO] Java version: 1.8.0_144, vendor: Oracle Corporation Thanks! Woonsan On Tue, Dec 11, 2018 at 1:59 AM Davide Giannella wrote: > > A candidate for the Jackrabbit Oak 1.9.13 release is available at: > > https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.9.13/ > > The release candidate is a zip archive of the sources in: > > > https://svn.apache.org/repos/asf/jackrabbit/oak/tags/jackrabbit-oak-1.9.13/ > > The SHA1 checksum of the archive is > 35bd4a1be2dc38b59870c0ef99d30045966af816. > > A staged Maven repository is available for review at: > > https://repository.apache.org/ > > The command for running automated checks against this release candidate is: > > # run in SVN checkout of > https://dist.apache.org/repos/dist/dev/jackrabbit > $ sh check-release.sh oak 1.9.13 > 35bd4a1be2dc38b59870c0ef99d30045966af816 > > Please vote on releasing this package as Apache Jackrabbit Oak 1.9.13. > The vote is open for the next 72 hours and passes if a majority of at > least three +1 Jackrabbit PMC votes are cast. > > [ ] +1 Release this package as Apache Jackrabbit Oak 1.9.13 > [ ] -1 Do not release this package because... > > D. >
Re: Why don't we move to Git?
On 11/12/2018 10:10, Francesco Mari wrote: > Hi, > > On Tue, 11 Dec 2018 at 10:56, Davide Giannella wrote: > >> Does git change always HEAD? Even if you merge something that fits >> "behind" HEAD. >> > Git always changes the head when a merge commit is performed. See [1] for > more details about how merging works in Git. I hope I understood your > concerns right. +1 then on this aspect. :) D.
Re: Why don't we move to Git?
Hi, I think this would be a good move. Today git seems to be more popular and powerful than svn. Currently we have people and tools using different SCM systems, which can sometimes be difficult and comes with a cost. I don't know how many times the GitHub mirror wasn't in sync anymore and manual intervention was necessary... Regards Marcel On 10.12.18, 10:58, "Francesco Mari" wrote: Given the recent announcement about gitbox.apache.org, the seamless integration with GitHub, and the fact that many of us already work with Git in our daily workflow, what about moving our repositories to Git?
Re: [VOTE] Release Apache Jackrabbit Oak 1.9.13
Hi, On 10.12.18, 17:59, "Davide Giannella" wrote: > Please vote on releasing this package as Apache Jackrabbit Oak 1.9.13. > The vote is open for the next 72 hours and passes if a majority of at > least three +1 Jackrabbit PMC votes are cast. All checks OK. +1 Release this package as Apache Jackrabbit Oak 1.9.13 Regards Marcel
Re: [VOTE] Release Apache Jackrabbit Oak 1.9.13
> [X] +1 Release this package as Apache Jackrabbit Oak 1.9.13 with [INFO] [INFO] Apache Maven 3.5.2 [INFO] OS name: "linux", version: "4.13.0-46-generic", arch: "amd64", family: "unix" [INFO] Java version: 1.8.0_181, vendor: Oracle Corporation [INFO] [INFO] ALL CHECKS OK [INFO] Thanks, Vikas
Re: Why don't we move to Git?
Hi, On Tue, 11 Dec 2018 at 10:56, Davide Giannella wrote: > Does git change always HEAD? Even if you merge something that fits > "behind" HEAD. > Git always changes the head when a merge commit is performed. See [1] for more details about how merging works in Git. I hope I understood your concerns right. [1]: https://www.atlassian.com/git/tutorials/using-branches/git-merge
Re: Why don't we move to Git?
Hello Fra, On 10/12/2018 14:28, Francesco Mari wrote: > Using a version composed by based version, timestamp and commit hash works > well. The qualifier is compared lexicographically, so the timestamp would > do the trick regardless of the commit hash. See this example [1] on > Versionatorr. you put 1.0-20181210-79377d5aab231f27fa7e3dc7bdd0e828 1.0-20181209-8135fa0dc4bdb394f38afc1f084336a2 which are two different timestamps. I didn't look yet at the details nor if this *would actually happen* *Release 1* HEAD 20121210 | | ... Will produce X.Y-20121210-79377d *Release 2* We want to release something that has just been merged but the merge doesn't move HEAD HEAD 20121210 | | \ | \ BRANCH 20121215 8135fa0dc ... ... Will produce again X.Y-20121210-79377d but in fact are two different binaries. Does git change always HEAD? Even if you merge something that fits "behind" HEAD. Davide
