You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@calcite.apache.org by Josh Elser <jo...@gmail.com> on 2016/03/14 17:23:52 UTC
Post-release Avatica 1.7.0 TODO
Logging what I've done (just in case I missed something along the way)
* Wrote up a new article for avatica 1.7.0
* Pushed artifacts to dist.a.o/release for pubsub to do its thing
* Released maven staging repo
* Sent [RESULT]
* Updated Calcite's avatica.version to 1.7.0
I think at this point, I just need to wait for pubsub to do its thing
and then:
* send msg to announcement@a.o
* Publish avatica website
* Send something out via Twitter
* Find a beer?
- Josh
Re: Post-release Avatica 1.7.0 TODO
Posted by Josh Elser <jo...@gmail.com>.
Sure thing. I'll circle back around on these. Thanks for the
recommendations.
Julian Hyde wrote:
> Thanks Josh for getting the release out!
>
> The news item and release note still need work. There are a couple of typos: ‘specifical’ and a backslash. “These release has fewer notable issues” is lukewarm (I presume you mean bugs fixed, not bugs remaining), and so I’d lead with the performance improvements paragraph. Passive voice is to be avoided! Active (or imperative) voice gets to the point in fewer words. For example, change the first sentence to “The Apache Calcite PMC is pleased to announce Avatica release 1.7.0, the first independent release of Avatica”.
>
> In both the news item and history.md, use two brackets in the .md, which will turn into one bracket and a link to issues.apache.org in the html. For example,
>
> [[CALCITE-1091](https://issues.apache.org/jira/browse/CALCITE-1091)]
>
> In history.md, can you fill in the date of release 1.7.0. Also, the sentence "Numerous improvements aimed at reducing the overall latency of Avatica RPCs was reduced” is nonsense as it stands.
>
> I think you can publish the site today, just wait til tomorrow to announce on email and twitter.
>
> I saw you already merged back to master — thanks for that. I’ll start the ball rolling for the first RC of Calcite 1.7.0.
>
> Julian
>
>
>> On Mar 14, 2016, at 9:23 AM, Josh Elser<jo...@gmail.com> wrote:
>>
>> Logging what I've done (just in case I missed something along the way)
>>
>> * Wrote up a new article for avatica 1.7.0
>> * Pushed artifacts to dist.a.o/release for pubsub to do its thing
>> * Released maven staging repo
>> * Sent [RESULT]
>> * Updated Calcite's avatica.version to 1.7.0
>>
>> I think at this point, I just need to wait for pubsub to do its thing and then:
>>
>> * send msg to announcement@a.o
>> * Publish avatica website
>> * Send something out via Twitter
>> * Find a beer?
>>
>> - Josh
>
Re: Post-release Avatica 1.7.0 TODO
Posted by Julian Hyde <jh...@apache.org>.
Thanks Josh for getting the release out!
The news item and release note still need work. There are a couple of typos: ‘specifical’ and a backslash. “These release has fewer notable issues” is lukewarm (I presume you mean bugs fixed, not bugs remaining), and so I’d lead with the performance improvements paragraph. Passive voice is to be avoided! Active (or imperative) voice gets to the point in fewer words. For example, change the first sentence to “The Apache Calcite PMC is pleased to announce Avatica release 1.7.0, the first independent release of Avatica”.
In both the news item and history.md, use two brackets in the .md, which will turn into one bracket and a link to issues.apache.org in the html. For example,
[[CALCITE-1091](https://issues.apache.org/jira/browse/CALCITE-1091)]
In history.md, can you fill in the date of release 1.7.0. Also, the sentence "Numerous improvements aimed at reducing the overall latency of Avatica RPCs was reduced” is nonsense as it stands.
I think you can publish the site today, just wait til tomorrow to announce on email and twitter.
I saw you already merged back to master — thanks for that. I’ll start the ball rolling for the first RC of Calcite 1.7.0.
Julian
> On Mar 14, 2016, at 9:23 AM, Josh Elser <jo...@gmail.com> wrote:
>
> Logging what I've done (just in case I missed something along the way)
>
> * Wrote up a new article for avatica 1.7.0
> * Pushed artifacts to dist.a.o/release for pubsub to do its thing
> * Released maven staging repo
> * Sent [RESULT]
> * Updated Calcite's avatica.version to 1.7.0
>
> I think at this point, I just need to wait for pubsub to do its thing and then:
>
> * send msg to announcement@a.o
> * Publish avatica website
> * Send something out via Twitter
> * Find a beer?
>
> - Josh