You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by GitBox <gi...@apache.org> on 2021/02/12 17:28:18 UTC
[GitHub] [lucene-site] chatman opened a new pull request #39: Adding slack links to community and discussion pages
chatman opened a new pull request #39:
URL: https://github.com/apache/lucene-site/pull/39
There are more options for support these days than the community page mentions. Lets add as much info as possible.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org
[GitHub] [lucene-site] chatman commented on pull request #39: Adding slack links to community and discussion pages
Posted by GitBox <gi...@apache.org>.
chatman commented on pull request #39:
URL: https://github.com/apache/lucene-site/pull/39#issuecomment-779595824
This is very cumbersome, esp for a RM during a release.
On Tue, 16 Feb, 2021, 11:00 am Anshum Gupta, <no...@github.com>
wrote:
> Cherry picking seems to cause issues with the workflow that is documented.
> The best way is to not cherry pick but at any point just create a PR from
> master to production, and nothing will get missed from being merged plus
> the histories would be same in terms of chronology of commits.
>
> The ideal steps are:
>
> 1. Create a PR from your branch to apache/lucene-site:master
> 2. Merge the PR into master
> 3. Create a PR from master -> production
>
> —
> You are receiving this because you modified the open/close state.
> Reply to this email directly, view it on GitHub
> <https://github.com/apache/lucene-site/pull/39#issuecomment-779591890>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ABDCR5CMX3JPBPSFOTNVH73S7H7G3ANCNFSM4XRBRCUQ>
> .
>
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org
[GitHub] [lucene-site] chatman commented on pull request #39: Adding slack links to community and discussion pages
Posted by GitBox <gi...@apache.org>.
chatman commented on pull request #39:
URL: https://github.com/apache/lucene-site/pull/39#issuecomment-779604166
> Cherry picking seems to cause issues with the workflow that is documented.
This is an unfounded assertion. Assuming master and production were both at sync before any of my changes, two commits added to master's tip (via this PR) when cherry-picked (without conflicts) to tip of production should be no different from a merge to production.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org
[GitHub] [lucene-site] anshumg commented on pull request #39: Adding slack links to community and discussion pages
Posted by GitBox <gi...@apache.org>.
anshumg commented on pull request #39:
URL: https://github.com/apache/lucene-site/pull/39#issuecomment-778357060
Thanks for adding this information, @chatman
Can you please highlight and may be list the unofficial channels separately? You may list those as "Third Party" perhaps?
You've mentioned this already but just wanted to be sure that the channels aren't perceived as official ones even accidentally.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org
[GitHub] [lucene-site] anshumg commented on pull request #39: Adding slack links to community and discussion pages
Posted by GitBox <gi...@apache.org>.
anshumg commented on pull request #39:
URL: https://github.com/apache/lucene-site/pull/39#issuecomment-780138505
I would like to think so as well but have just seen otherwise. Again, I'm fine with any workflow as long as it's convenient for everyone - no reason to add extra steps :)
I'm not sure if cherry-pick messes up something as w.r.t. the code, it's identical.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org
[GitHub] [lucene-site] chatman commented on pull request #39: Adding slack links to community and discussion pages
Posted by GitBox <gi...@apache.org>.
chatman commented on pull request #39:
URL: https://github.com/apache/lucene-site/pull/39#issuecomment-778366288
Thanks for the review, @epugh , @anshumg !
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org
[GitHub] [lucene-site] janhoy commented on pull request #39: Adding slack links to community and discussion pages
Posted by GitBox <gi...@apache.org>.
janhoy commented on pull request #39:
URL: https://github.com/apache/lucene-site/pull/39#issuecomment-779502419
Why was Solr slack info added to the Lucene-java webpage? https://lucene.apache.org/core/discussion.html#slack
That page does not list any other Solr mailing lists or resources.
And just curious - how did you merge this PR to production branch? When I compare production and master branches the edits show up as diffs.
Finally, please delete the now-unused feature branch.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org
[GitHub] [lucene-site] anshumg commented on pull request #39: Adding slack links to community and discussion pages
Posted by GitBox <gi...@apache.org>.
anshumg commented on pull request #39:
URL: https://github.com/apache/lucene-site/pull/39#issuecomment-779591890
Cherry picking seems to cause issues with the workflow that is documented. The best way is to not cherry pick but at any point just create a PR from master to production, and nothing will get missed from being merged plus the histories would be same in terms of chronology of commits.
The ideal steps are:
1. Create a PR from your branch to apache/lucene-site:master
2. Merge the PR into master
3. Create a PR from master -> production
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org
[GitHub] [lucene-site] chatman commented on pull request #39: Adding slack links to community and discussion pages
Posted by GitBox <gi...@apache.org>.
chatman commented on pull request #39:
URL: https://github.com/apache/lucene-site/pull/39#issuecomment-778332733
@epugh FYI, contains a link to the OSC slack.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org
[GitHub] [lucene-site] chatman closed pull request #39: Adding slack links to community and discussion pages
Posted by GitBox <gi...@apache.org>.
chatman closed pull request #39:
URL: https://github.com/apache/lucene-site/pull/39
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org
[GitHub] [lucene-site] janhoy commented on pull request #39: Adding slack links to community and discussion pages
Posted by GitBox <gi...@apache.org>.
janhoy commented on pull request #39:
URL: https://github.com/apache/lucene-site/pull/39#issuecomment-781332947
I just demonstrated this with #44 - it is really simple, just create the PR `master->production` and then merge it with *merge commit*, not a squash! This is now documented in README.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org
[GitHub] [lucene-site] chatman edited a comment on pull request #39: Adding slack links to community and discussion pages
Posted by GitBox <gi...@apache.org>.
chatman edited a comment on pull request #39:
URL: https://github.com/apache/lucene-site/pull/39#issuecomment-779559744
> Finally, please delete the now-unused feature branch.
Done.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org
[GitHub] [lucene-site] chatman commented on pull request #39: Adding slack links to community and discussion pages
Posted by GitBox <gi...@apache.org>.
chatman commented on pull request #39:
URL: https://github.com/apache/lucene-site/pull/39#issuecomment-779559744
> Finally, please delete the now-unused feature branch.
Done.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org
[GitHub] [lucene-site] epugh commented on a change in pull request #39: Adding slack links to community and discussion pages
Posted by GitBox <gi...@apache.org>.
epugh commented on a change in pull request #39:
URL: https://github.com/apache/lucene-site/pull/39#discussion_r575407662
##########
File path: content/pages/core/discussion.md
##########
@@ -86,7 +86,9 @@ but developers should be careful to transfer all the official decisions or usefu
## Slack
-The project's Slack channel is the **#lucene-dev** channel in the **the-asf** organization. Link: <https://the-asf.slack.com/messages/CE70MDPMF>
+- The project's Slack channel are the `#lucene-dev` and `#solr-dev` channels in the `the-asf` organization. These are primarily for developer discussions and not meant as support channels. Link: <https://the-asf.slack.com/messages/CE70MDPMF>
+- For Solr support, there is a (community maintained/unofficial) Slack organization that relays messages bi-directionally to/from the officially supported IRC channels. Link: https://s.apache.org/solr-slack
+- For relevance related discussions (Solr or other search engines), there's an unofficial Slack organization: https://opensourceconnections.com/slack
Review comment:
This slack communities name is "Relevance Slack", the invite code just happens to be through OSC. So how about "For relevance related discussions (Solr or other search engines), join Relevance Slack: http://opensourceconnections.com/slack"
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org
[GitHub] [lucene-site] chatman commented on pull request #39: Adding slack links to community and discussion pages
Posted by GitBox <gi...@apache.org>.
chatman commented on pull request #39:
URL: https://github.com/apache/lucene-site/pull/39#issuecomment-779555551
> And just curious - how did you merge this PR to production branch? When I compare production and master branches the edits show up as diffs.
I merged the PR to master and cherry-picked the commits to production.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org