[jira] [Commented] (COMDEV-436) parsereleases produces false releases for solr
[
https://issues.apache.org/jira/browse/COMDEV-436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17764754#comment-17764754
]
Houston Putman commented on COMDEV-436:
---
Yeah, the helm charts are not official source releases, but they are official
artifacts of the release. I would really prefer to keep them there.
{quote}It's easy enough to filter out additional directories if required.
{quote}
Awesome, they are in the /helm-charts sub-directory, so it should be easy to
filter that out! Filtering out "-slim" would be good, but I'm not sure that's
as easy.
> parsereleases produces false releases for solr
> --
>
> Key: COMDEV-436
> URL: https://issues.apache.org/jira/browse/COMDEV-436
> Project: Community Development
> Issue Type: Improvement
>Reporter: Jan Høydahl
>Priority: Major
> Attachments: COMDEV-436.patch, releases.json
>
>
> When viewing [https://projects.apache.org/releases.html] and searching for
> "solr", there are too many "falase positives".
> See the "solr" section of
> [https://projects.apache.org/json/foundation/releases.json]
> {code:java}
> "solr": {
> "all.yaml": "2021-11-11",
> "index.yaml": "2021-11-11",
> "solr-0.5.0": "2021-11-11",
> "solr-0.5.0.tgz.prov": "2021-11-11",
> "solr-operator-0.5.0": "2021-11-11",
> "solr-operator-0.5.0.tgz.prov": "2021-11-11",
> "solr-operator-v0.5.0": "2021-11-11",
> "solrbackups.yaml": "2021-11-11",
> "solrclouds.yaml": "2021-11-11",
> "solrprometheusexporters.yaml": "2021-11-11",
> "zookeeperclusters.yaml": "2021-11-11"
> },
> {code}
> The script mistakes some files as releases, which are really not.
> Currently the Solr downloads repo [https://downloads.apache.org/solr/]
> contains only one release for the "solr-opereator" project, which is not a
> traditional java code release, but rather k8s Helm-charts and CRDs. The Solr
> main releases are currently in "lucene" so we don't expect them to show up
> here until the 9.0 release.
> So the expected output for the current contents is simply:
> {code:java}
> "solr": {
> "solr-operator-0.5.0": "2021-11-11",
> },
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-436) parsereleases produces false releases for solr
[
https://issues.apache.org/jira/browse/COMDEV-436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17764752#comment-17764752
]
Sebb commented on COMDEV-436:
-
Please don't stop uploading items to the download area merely to fix a problem
with the release parsing! Maybe the charts don't belong there, but that is a
separate issue.
Whilst it is not ideal for the release listing to contain lots of spurious
files, IMO it is better to include a few extras rather than omit valid releases.
It's easy enough to filter out additional directories if required.
> parsereleases produces false releases for solr
> --
>
> Key: COMDEV-436
> URL: https://issues.apache.org/jira/browse/COMDEV-436
> Project: Community Development
> Issue Type: Improvement
>Reporter: Jan Høydahl
>Priority: Major
> Attachments: COMDEV-436.patch, releases.json
>
>
> When viewing [https://projects.apache.org/releases.html] and searching for
> "solr", there are too many "falase positives".
> See the "solr" section of
> [https://projects.apache.org/json/foundation/releases.json]
> {code:java}
> "solr": {
> "all.yaml": "2021-11-11",
> "index.yaml": "2021-11-11",
> "solr-0.5.0": "2021-11-11",
> "solr-0.5.0.tgz.prov": "2021-11-11",
> "solr-operator-0.5.0": "2021-11-11",
> "solr-operator-0.5.0.tgz.prov": "2021-11-11",
> "solr-operator-v0.5.0": "2021-11-11",
> "solrbackups.yaml": "2021-11-11",
> "solrclouds.yaml": "2021-11-11",
> "solrprometheusexporters.yaml": "2021-11-11",
> "zookeeperclusters.yaml": "2021-11-11"
> },
> {code}
> The script mistakes some files as releases, which are really not.
> Currently the Solr downloads repo [https://downloads.apache.org/solr/]
> contains only one release for the "solr-opereator" project, which is not a
> traditional java code release, but rather k8s Helm-charts and CRDs. The Solr
> main releases are currently in "lucene" so we don't expect them to show up
> here until the 9.0 release.
> So the expected output for the current contents is simply:
> {code:java}
> "solr": {
> "solr-operator-0.5.0": "2021-11-11",
> },
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-436) parsereleases produces false releases for solr
[
https://issues.apache.org/jira/browse/COMDEV-436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17764706#comment-17764706
]
Jan Høydahl commented on COMDEV-436:
Thanks. Solr release section still looks ok. Except the inclusion of two helm
charts that are not official source releases of the project (solr-0.7.1 and
solr-operator-0.7.1), see
[https://downloads.apache.org/solr/solr-operator/v0.7.1/helm-charts/]
I suppose, if we required {{-src}} tgz files next to the convenience binaries,
we could use that to weed these out. Or perhaps we should stop uploading our
helm charts to the download area?
> parsereleases produces false releases for solr
> --
>
> Key: COMDEV-436
> URL: https://issues.apache.org/jira/browse/COMDEV-436
> Project: Community Development
> Issue Type: Improvement
>Reporter: Jan Høydahl
>Priority: Major
> Attachments: COMDEV-436.patch, releases.json
>
>
> When viewing [https://projects.apache.org/releases.html] and searching for
> "solr", there are too many "falase positives".
> See the "solr" section of
> [https://projects.apache.org/json/foundation/releases.json]
> {code:java}
> "solr": {
> "all.yaml": "2021-11-11",
> "index.yaml": "2021-11-11",
> "solr-0.5.0": "2021-11-11",
> "solr-0.5.0.tgz.prov": "2021-11-11",
> "solr-operator-0.5.0": "2021-11-11",
> "solr-operator-0.5.0.tgz.prov": "2021-11-11",
> "solr-operator-v0.5.0": "2021-11-11",
> "solrbackups.yaml": "2021-11-11",
> "solrclouds.yaml": "2021-11-11",
> "solrprometheusexporters.yaml": "2021-11-11",
> "zookeeperclusters.yaml": "2021-11-11"
> },
> {code}
> The script mistakes some files as releases, which are really not.
> Currently the Solr downloads repo [https://downloads.apache.org/solr/]
> contains only one release for the "solr-opereator" project, which is not a
> traditional java code release, but rather k8s Helm-charts and CRDs. The Solr
> main releases are currently in "lucene" so we don't expect them to show up
> here until the 9.0 release.
> So the expected output for the current contents is simply:
> {code:java}
> "solr": {
> "solr-operator-0.5.0": "2021-11-11",
> },
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-436) parsereleases produces false releases for solr
[
https://issues.apache.org/jira/browse/COMDEV-436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17764700#comment-17764700
]
Sebb commented on COMDEV-436:
-
The parser now runs off the find-ls listing which makes it very much quicker.
Also the matching of releases has been much simplified.
Several false positives and negatives have been addressed.
Hopefully the SOLR releases now look OK?
> parsereleases produces false releases for solr
> --
>
> Key: COMDEV-436
> URL: https://issues.apache.org/jira/browse/COMDEV-436
> Project: Community Development
> Issue Type: Improvement
>Reporter: Jan Høydahl
>Priority: Major
> Attachments: COMDEV-436.patch, releases.json
>
>
> When viewing [https://projects.apache.org/releases.html] and searching for
> "solr", there are too many "falase positives".
> See the "solr" section of
> [https://projects.apache.org/json/foundation/releases.json]
> {code:java}
> "solr": {
> "all.yaml": "2021-11-11",
> "index.yaml": "2021-11-11",
> "solr-0.5.0": "2021-11-11",
> "solr-0.5.0.tgz.prov": "2021-11-11",
> "solr-operator-0.5.0": "2021-11-11",
> "solr-operator-0.5.0.tgz.prov": "2021-11-11",
> "solr-operator-v0.5.0": "2021-11-11",
> "solrbackups.yaml": "2021-11-11",
> "solrclouds.yaml": "2021-11-11",
> "solrprometheusexporters.yaml": "2021-11-11",
> "zookeeperclusters.yaml": "2021-11-11"
> },
> {code}
> The script mistakes some files as releases, which are really not.
> Currently the Solr downloads repo [https://downloads.apache.org/solr/]
> contains only one release for the "solr-opereator" project, which is not a
> traditional java code release, but rather k8s Helm-charts and CRDs. The Solr
> main releases are currently in "lucene" so we don't expect them to show up
> here until the 9.0 release.
> So the expected output for the current contents is simply:
> {code:java}
> "solr": {
> "solr-operator-0.5.0": "2021-11-11",
> },
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
Re: [ANNOUNCE] - Establishing ALC Bangalore Chapter
Super, many congratulations to the ALC Bangalore team, and best wishes for your future activities in spreading ASF and Open Source awareness! Best Regards, Swapnil M Mane On Wed, Sep 13, 2023 at 11:25 AM Aditya Sharma wrote: > > Hello all, > > ComDev PMC is pleased to announce our next Apache Local Community [1] > Chapter - ALC Bangalore [2] and Navendu as ALC Bangalore Chapter lead. > > We have the following members in ALC Bangalore: > > 1. Atri Sharma (atri) > -- ASF Member > -- PMC (Lucene, Solr, HAWQ, MADLib, and Incubator) > -- Committer (Pinot) > > 2. Mohammad Asif Siddiqui (asifdxtreme) > -- ASF Member > -- PMC (ServiceComb and Incubator) > -- Mentor (Nuttx) > > 3. Brahma Reddy Battula (brahma) > -- PMC (Ambari & Hadoop) > -- PPMC (Livy) > > 4. Sumit Maheshwari (msumit) > -- PMC (Airflow)) > > 5. Navendu Pottekkat (navendu) > -- Committer (APISIX) > > Mentor: Aditya Sharma > -- ASF Member > -- PMC (ComDev, OFBiz and Roller) > -- Chapter Lead, ALC Indore > > > Congratulations to the ALC Bangalore Chapter and wishing them good luck for > their future events. > > [1] https://s.apache.org/alc > [2] https://s.apache.org/alc-bangalore > > > Best regards, > The Apache ComDev team, > community.apache.org - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [ANNOUNCE] - Establishing ALC Bangalore Chapter
Thank you Aditya! We look forward to bringing users, contributors, and maintainers of ASF projects together in Bangalore! - Navendu On 13/09/23 11:24 AM, Aditya Sharma wrote: Hello all, ComDev PMC is pleased to announce our next Apache Local Community [1] Chapter - ALC Bangalore [2] and Navendu as ALC Bangalore Chapter lead. We have the following members in ALC Bangalore: 1. Atri Sharma (atri) -- ASF Member -- PMC (Lucene, Solr, HAWQ, MADLib, and Incubator) -- Committer (Pinot) 2. Mohammad Asif Siddiqui (asifdxtreme) -- ASF Member -- PMC (ServiceComb and Incubator) -- Mentor (Nuttx) 3. Brahma Reddy Battula (brahma) -- PMC (Ambari & Hadoop) -- PPMC (Livy) 4. Sumit Maheshwari (msumit) -- PMC (Airflow)) 5. Navendu Pottekkat (navendu) -- Committer (APISIX) Mentor: Aditya Sharma -- ASF Member -- PMC (ComDev, OFBiz and Roller) -- Chapter Lead, ALC Indore Congratulations to the ALC Bangalore Chapter and wishing them good luck for their future events. [1] https://s.apache.org/alc [2] https://s.apache.org/alc-bangalore Best regards, The Apache ComDev team, community.apache.org - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
