> On Nov 12, 2017, at 5:25 AM, sebb wrote:
>
> On 12 November 2017 at 04:26, Matt Benson wrote:
>> On Nov 11, 2017 9:32 PM, "Rob Tompkins" wrote:
>>
>>
>>
>>> On Nov 11, 2017, at 10:24 PM, Gary Gregory
On 12 November 2017 at 04:26, Matt Benson wrote:
> On Nov 11, 2017 9:32 PM, "Rob Tompkins" wrote:
>
>
>
>> On Nov 11, 2017, at 10:24 PM, Gary Gregory wrote:
>>
>>> On Sat, Nov 11, 2017 at 8:19 PM, Rob Tompkins
Take a look at how the maven team votes and publishes
Chas
> On Nov 11, 2017, at 8:26 PM, Matt Benson wrote:
>
> On Nov 11, 2017 9:32 PM, "Rob Tompkins" wrote:
>
>
>
>>> On Nov 11, 2017, at 10:24 PM, Gary Gregory wrote:
>>>
On Nov 11, 2017 9:32 PM, "Rob Tompkins" wrote:
> On Nov 11, 2017, at 10:24 PM, Gary Gregory wrote:
>
>> On Sat, Nov 11, 2017 at 8:19 PM, Rob Tompkins wrote:
>>
>> Hello all,
>>
>> I was wondering if we might think about a 2.X
> On Nov 11, 2017, at 10:24 PM, Gary Gregory wrote:
>
>> On Sat, Nov 11, 2017 at 8:19 PM, Rob Tompkins wrote:
>>
>> Hello all,
>>
>> I was wondering if we might think about a 2.X line in the [build-plugin]
>> to better facilitate our release
On Sat, Nov 11, 2017 at 8:19 PM, Rob Tompkins wrote:
> Hello all,
>
> I was wondering if we might think about a 2.X line in the [build-plugin]
> to better facilitate our release mechanics so that we don’t have to jump
> through all of these hoops that we do when building a
Hello all,
I was wondering if we might think about a 2.X line in the [build-plugin] to
better facilitate our release mechanics so that we don’t have to jump through
all of these hoops that we do when building a release candidate?
Steps:
1. Move the commons-build-plugin to git.
2. Fully rewrite