You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@arrow.apache.org by GitBox <gi...@apache.org> on 2021/07/23 16:51:39 UTC
[GitHub] [arrow-datafusion] thisisnic opened a new issue #770: Confirm git tagging strategy for releases
thisisnic opened a new issue #770:
URL: https://github.com/apache/arrow-datafusion/issues/770
Please could you confirm what convention you'll be using for tagging releases?
I am currently working on a ticket in the `apache/arrow` repo which involves updating the release script that generates lists of committers and contributors for the Apache Arrow website (https://issues.apache.org/jira/browse/ARROW-12701). I'd like to make sure that contributions to the `arrow-datafusion` repository are recognised on the website and blog page.
I'd just like to check what git tags you are going to use for different releases? I think the `apache/arrow` repo uses `apache-arrow-x.y.z` and `apache/arrow-rs` uses `x.y.z` where `x.y.z` is the release version number. The script I have uses these tags to work out the numbers needed for the contributor list - I'll adapt it to take into account however you are managing this.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [arrow-datafusion] alamb commented on issue #770: Confirm git tagging strategy for releases
Posted by GitBox <gi...@apache.org>.
alamb commented on issue #770:
URL: https://github.com/apache/arrow-datafusion/issues/770#issuecomment-885877340
@andygrove / @Dandandan / @jorgecarleitao do you have any thoughts in this area?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [arrow-datafusion] alamb commented on issue #770: Confirm git tagging strategy for releases
Posted by GitBox <gi...@apache.org>.
alamb commented on issue #770:
URL: https://github.com/apache/arrow-datafusion/issues/770#issuecomment-885876926
@thisisnic -- I am not sure what our release plan for this would be.
Would it work to use the same strategy here as `arrow-rs` -- namely tags with the version numbers (4.0.0 and 5.0.0, etc)? Note that we don't actually have those tags in the datafusion repo yet
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [arrow-datafusion] alamb commented on issue #770: Confirm git tagging strategy for releases
Posted by GitBox <gi...@apache.org>.
alamb commented on issue #770:
URL: https://github.com/apache/arrow-datafusion/issues/770#issuecomment-892861203
I believe this is the strategy that @houqp is implementing in https://github.com/apache/arrow-datafusion/issues/771 so closing this ticket out
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [arrow-datafusion] alamb closed issue #770: Confirm git tagging strategy for releases
Posted by GitBox <gi...@apache.org>.
alamb closed issue #770:
URL: https://github.com/apache/arrow-datafusion/issues/770
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [arrow-datafusion] alamb closed issue #770: Confirm git tagging strategy for releases
Posted by GitBox <gi...@apache.org>.
alamb closed issue #770:
URL: https://github.com/apache/arrow-datafusion/issues/770
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [arrow-datafusion] alamb commented on issue #770: Confirm git tagging strategy for releases
Posted by GitBox <gi...@apache.org>.
alamb commented on issue #770:
URL: https://github.com/apache/arrow-datafusion/issues/770#issuecomment-892861203
I believe this is the strategy that @houqp is implementing in https://github.com/apache/arrow-datafusion/issues/771 so closing this ticket out
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [arrow-datafusion] alamb commented on issue #770: Confirm git tagging strategy for releases
Posted by GitBox <gi...@apache.org>.
alamb commented on issue #770:
URL: https://github.com/apache/arrow-datafusion/issues/770#issuecomment-885914512
Unless I hear differently I will plan to use the same strategy in
arrow-datafusion
Note it isn't clear to me when we will have a 5.0.0 release -- I have
started a conversation here:
https://github.com/apache/arrow-datafusion/issues/771
On Fri, Jul 23, 2021 at 4:44 PM Nic ***@***.***> wrote:
> @thisisnic <https://github.com/thisisnic> -- I am not sure what our
> release plan for this would be.
>
> Would it work to use the same strategy here as arrow-rs -- namely tags
> with the version numbers (4.0.0 and 5.0.0, etc)? Note that we don't
> actually have those tags in the datafusion repo yet
>
> @alamb <https://github.com/alamb> That would definitely be the simplest
> strategy for me, in terms of integrating with the current script I'm using,
> but if you'd prefer a different approach, I am happy to adapt to that.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/apache/arrow-datafusion/issues/770#issuecomment-885904282>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AADXZMM2HRWKQOCN57CHUADTZHICJANCNFSM5A4K24QA>
> .
>
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [arrow-datafusion] thisisnic commented on issue #770: Confirm git tagging strategy for releases
Posted by GitBox <gi...@apache.org>.
thisisnic commented on issue #770:
URL: https://github.com/apache/arrow-datafusion/issues/770#issuecomment-885904282
> @thisisnic -- I am not sure what our release plan for this would be.
>
> Would it work to use the same strategy here as `arrow-rs` -- namely tags with the version numbers (4.0.0 and 5.0.0, etc)? Note that we don't actually have those tags in the datafusion repo yet
@alamb That would definitely be the simplest strategy for me, in terms of integrating with the current script I'm using, but if you'd prefer a different approach, I am happy to adapt to that.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org