commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gilles <gil...@harfang.homelinux.org>
Subject Re: [VOTE][RC1] Commons collections 4.3
Date Wed, 26 Dec 2018 11:18:26 GMT
Hi.

On Wed, 26 Dec 2018 08:23:03 +0700, Maxim Solodovnik wrote:
> 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

I get it now!
So indeed, a "release" branch that is pushed upstream is not
necessary.[1]

And there is another couple of improvements which I could use
next time.

Thanks for sharing,
Gilles

[1] It might become useful only if the RC has problems _and_
     other people want to help with fixing (?).

>
> On Wed, 26 Dec 2018 at 08:11, Rob Tompkins <chtompki@gmail.com> 
> wrote:
>
>>
>>
>> > On Dec 25, 2018, at 8:04 PM, Maxim Solodovnik 
>> <solomax666@gmail.com>
>> 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 will be pushed, and there will be no useless
>> branches
>> > with minimal "release" changes
>> >
>>
>> Yes that is true. But so long as the vote has yet to be initiated, 
>> the tag
>> can be pushed even after the build has been made.
>>
>> -Rob
>>
>> >> On Wed, 26 Dec 2018 at 05:40, Gilles 
>> <gilles@harfang.homelinux.org>
>> wrote:
>> >>
>> >> 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 switched to it.
>> >>
>> >> Do you propose an alternative way to do it?  Please
>> >> share some link describing the process
>> >>
>>>> [...]


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Mime
View raw message