Post 5.0.0-alpha

[Josh Elser <jo...@gmail.com>]

Hiya,

Thanks to everyone who helped get 5.0.0-alpha out the door. A few 
book-keeping things:

* I've updated JIRA, nuking the 5.x and 5.0 fixVersions, renaming 5.0.0 
to 5.0.0-alpha, and renaming 5.1.0 to 5.0.0. 5.0.0 is the fixVersion you 
want.
* Announcement has been sent out and I think I've cleaned everything 
else up.
* 5.x-HBase-2.0 is open for your commits (with a Maven version of 
5.0.0-SNAPSHOT)
* Rajeshbabu is going to look at making sure the 5.x branch is synced up 
with the rest of the changes from 4.x which might have been skipped in 
PHOENIX-4610.
* I'll continue to monitor the 5.0.0 fixVersion, trying to keep us on a 
trajectory to make that release happen sooner than later.

- Josh

Re: Post 5.0.0-alpha

[James Taylor <ja...@apache.org>]

Sounds like a good plan, Josh. Thanks for the explanation.

On Thu, Feb 15, 2018 at 2:28 PM, Josh Elser <el...@apache.org> wrote:

> So the official release version that I set was "5.0.0-alpha" (with the
> HBase-2.0 kind of being superfluous since we weren't targeting any other
> HBase versions). To match this Maven version, I switched around the
> fixVersions on JIRA to match:
>
> Resolved issues that were previously 5.0, 5.x, or 5.0.0 are now
> 5.0.0-alpha. Everything else is now 5.0.0 -- which is what we can use for
> future changes.
>
> My hope was that this would avoid us having to announce something like
> "beware! 5.0.0 isn't stable!" (the "alpha" designation doing that for us).
>
> Happy to do something else if this isn't clear to others like it is to me
> :)
>
>
> On 2/15/18 3:08 PM, James Taylor wrote:
>
>> Thanks, Josh. Great job on the release.
>>
>> One question on the fixVersion. I've pushed a few commits for fixes after
>> the 5.0.0 release went out. Since they aren't in the release, I set the
>> fixVersion to 5.1.0 (anticipating that that'll be the next release
>> version). Should we use a different fixVersion that that for these "to be
>> release" fixes?
>>
>> On Thu, Feb 15, 2018 at 12:04 PM, Josh Elser <jo...@gmail.com>
>> wrote:
>>
>> Hiya,
>>>
>>> Thanks to everyone who helped get 5.0.0-alpha out the door. A few
>>> book-keeping things:
>>>
>>> * I've updated JIRA, nuking the 5.x and 5.0 fixVersions, renaming 5.0.0
>>> to
>>> 5.0.0-alpha, and renaming 5.1.0 to 5.0.0. 5.0.0 is the fixVersion you
>>> want.
>>> * Announcement has been sent out and I think I've cleaned everything else
>>> up.
>>> * 5.x-HBase-2.0 is open for your commits (with a Maven version of
>>> 5.0.0-SNAPSHOT)
>>> * Rajeshbabu is going to look at making sure the 5.x branch is synced up
>>> with the rest of the changes from 4.x which might have been skipped in
>>> PHOENIX-4610.
>>> * I'll continue to monitor the 5.0.0 fixVersion, trying to keep us on a
>>> trajectory to make that release happen sooner than later.
>>>
>>> - Josh
>>>
>>>
>>

Re: Post 5.0.0-alpha

[Josh Elser <el...@apache.org>]

So the official release version that I set was "5.0.0-alpha" (with the 
HBase-2.0 kind of being superfluous since we weren't targeting any other 
HBase versions). To match this Maven version, I switched around the 
fixVersions on JIRA to match:

Resolved issues that were previously 5.0, 5.x, or 5.0.0 are now 
5.0.0-alpha. Everything else is now 5.0.0 -- which is what we can use 
for future changes.

My hope was that this would avoid us having to announce something like 
"beware! 5.0.0 isn't stable!" (the "alpha" designation doing that for us).

Happy to do something else if this isn't clear to others like it is to me :)

On 2/15/18 3:08 PM, James Taylor wrote:
> Thanks, Josh. Great job on the release.
> 
> One question on the fixVersion. I've pushed a few commits for fixes after
> the 5.0.0 release went out. Since they aren't in the release, I set the
> fixVersion to 5.1.0 (anticipating that that'll be the next release
> version). Should we use a different fixVersion that that for these "to be
> release" fixes?
> 
> On Thu, Feb 15, 2018 at 12:04 PM, Josh Elser <jo...@gmail.com> wrote:
> 
>> Hiya,
>>
>> Thanks to everyone who helped get 5.0.0-alpha out the door. A few
>> book-keeping things:
>>
>> * I've updated JIRA, nuking the 5.x and 5.0 fixVersions, renaming 5.0.0 to
>> 5.0.0-alpha, and renaming 5.1.0 to 5.0.0. 5.0.0 is the fixVersion you want.
>> * Announcement has been sent out and I think I've cleaned everything else
>> up.
>> * 5.x-HBase-2.0 is open for your commits (with a Maven version of
>> 5.0.0-SNAPSHOT)
>> * Rajeshbabu is going to look at making sure the 5.x branch is synced up
>> with the rest of the changes from 4.x which might have been skipped in
>> PHOENIX-4610.
>> * I'll continue to monitor the 5.0.0 fixVersion, trying to keep us on a
>> trajectory to make that release happen sooner than later.
>>
>> - Josh
>>
> 

Re: Post 5.0.0-alpha

[James Taylor <ja...@apache.org>]

Thanks, Josh. Great job on the release.

One question on the fixVersion. I've pushed a few commits for fixes after
the 5.0.0 release went out. Since they aren't in the release, I set the
fixVersion to 5.1.0 (anticipating that that'll be the next release
version). Should we use a different fixVersion that that for these "to be
release" fixes?

On Thu, Feb 15, 2018 at 12:04 PM, Josh Elser <jo...@gmail.com> wrote:

> Hiya,
>
> Thanks to everyone who helped get 5.0.0-alpha out the door. A few
> book-keeping things:
>
> * I've updated JIRA, nuking the 5.x and 5.0 fixVersions, renaming 5.0.0 to
> 5.0.0-alpha, and renaming 5.1.0 to 5.0.0. 5.0.0 is the fixVersion you want.
> * Announcement has been sent out and I think I've cleaned everything else
> up.
> * 5.x-HBase-2.0 is open for your commits (with a Maven version of
> 5.0.0-SNAPSHOT)
> * Rajeshbabu is going to look at making sure the 5.x branch is synced up
> with the rest of the changes from 4.x which might have been skipped in
> PHOENIX-4610.
> * I'll continue to monitor the 5.0.0 fixVersion, trying to keep us on a
> trajectory to make that release happen sooner than later.
>
> - Josh
>