This is the way Wicketstuff build is performed [1]
The project consist of ~285 modules and it is wise to create tag only if
build is already in Nexus :)
[1]
https://github.com/wicketstuff/core/wiki/Wicket-Stuff-Core-Release-Process
On Wed, 26 Dec 2018 at 08:11, Rob Tompkins wrote:
>
>
> > On De
> On Dec 25, 2018, at 8:04 PM, Maxim Solodovnik wrote:
>
> In both git and svn you need a branch to create tag
> But since git has local and remote repository, steps can be:
>
> 1) create local branch
> 2) made "release" changes
> 3) create tag
> 4) push the tag
>
> In this case only tag wil
In both git and svn you need a branch to create tag
But since git has local and remote repository, steps can be:
1) create local branch
2) made "release" changes
3) create tag
4) push the tag
In this case only tag will be pushed, and there will be no useless branches
with minimal "release" change
Hello All,
I will cancel the VOTE due to issues found in this RC
Will try to create RC2 ASAP
Thanks for your help!
On Wed, 26 Dec 2018 at 05:40, Gilles wrote:
> Hi.
>
> On Tue, 25 Dec 2018 22:22:43 +0700, Maxim Solodovnik wrote:
> > Hello Gilles,
> >
> > Actually if release is made based on gi
Hi.
On Tue, 25 Dec 2018 22:22:43 +0700, Maxim Solodovnik wrote:
Hello Gilles,
Actually if release is made based on git it is not necessary to
perform commits
?
I don't know other ways to perform the release; I follow
the practice established for "svn", that was then adapted
for "git" when we
Hello Gilles,
Actually if release is made based on git it is not necessary to
perform commits into local branch you are using to create RC tag
this why I previously ask if I can drop useless branch
I can fix issues with site manually, but it will be impossible to
modify pom without canceling rele
