What's the reason for #3 - changing the main branch name from "trunk" to "main"? I'm not particularly opposed, but it seems to me "trunk" works just fine as a name - is there a specific reason to rename?
-MR On Wed, May 19, 2021 at 3:13 AM Konrad Windszus <[email protected]> wrote: > Currently the page at > http://jackrabbit.apache.org/jcr/creating-releases.html < > http://jackrabbit.apache.org/jcr/creating-releases.html> only refers to > Jackrabbit 2 and Oak releases. FileVault releases have never been > documented there as they have slight differences. I will add a link though > to the jackrabbit documentation. > In the context of https://issues.apache.org/jira/browse/OAK-9440 < > https://issues.apache.org/jira/browse/OAK-9440> this page may need some > updates, but again, the handling with dist stays the same (still SVN) and > maven-release-plugin takes care of the rest, so currently I don't see any > changes necessary on the actual release steps (only on some links, > additional explanation, ....) > > Konrad > > > On 19. May 2021, at 11:03, Julian Reschke <[email protected]> wrote: > > > > Am 19.05.2021 um 10:56 schrieb Konrad Windszus: > >> Releasing FileVault works as before (as maven-release-plugin deals with > Git/SVN). The steps are documented at > http://jackrabbit.apache.org/filevault/howto_release.html and > https://jackrabbit.apache.org/filevault-package-maven-plugin/howto_release.html > . > >> Konrad > >> ... > > > > Ah, that is already a fork of the "main" page. > > > > So, if I understand correctly, most steps are indeed the same, as the > > actual release still goes into Apache SVN. > > > > If this is the case, it would be good if we could update that page so > > that it is correct both for SVN and GIT. > > > > Best regards, Julian > >
