Definitely clean them up. It should be a step in the release wizard when aborting the failed RC or promoting the successful RC. (This is in the python code, not the yaml file.) I know it is in Solr, but maybe that got broken in the lucene release wizard after the split. Given the lucene-solr artifacts, maybe its just a messaging issue in the release manager that needs to be fixed so that this step is clearer.
- Houston On Sat, Jun 18, 2022 at 12:32 AM Anshum Gupta <ans...@anshumgupta.net> wrote: > I don't think we need them so it totally makes sense to clean them up. > > On Fri, Jun 17, 2022 at 3:28 PM Mike Drob <md...@mdrob.com> wrote: > >> Can we delete all of these? Do we still need them? Is there any reason to >> keep them? I guess they don't hurt anything by existing... >> >> $ svn ls https://dist.apache.org/repos/dist/dev/lucene/ >> lucene-9.0.0-RC1-rev-903ee94dc50643299c15dfa954410f3ee4d62075/ >> lucene-9.0.0-RC2-rev-95072f3b71e67e308d71a6149323bf7dd04c8f75/ >> lucene-9.0.0-RC3-rev-1ddce848cf3d5067efcafc6569d5f8203e56af0b/ >> lucene-9.1.0-RC1-rev-a6114b532a273e370528675d551d3ddfa02f4679/ >> lucene-9.2.0-RC1-rev-978eef5459c7683038ddcca4ec56e4baa63715d0/ >> lucene-solr-7.3.0-RC1-reveb8a5a882f879a51389b5d43f74f3aceac9e68c9/ >> lucene-solr-7.6.0-RC1-rev2d4435162774ad43b66ce0e7847bf8c1558e20a9/ >> lucene-solr-7.7.3-RC1-rev1a0d2a901dfec93676b0fe8be425101ceb754b85/ >> lucene-solr-8.1.0-RC1-reve5839fb416083fcdaeedfb1e329a9fdaa29fdc50/ >> lucene-solr-8.3.0-RC1-revd796eca84dbabe3ae9b3c27afc01ef3bee35acb1/ >> lucene-solr-8.8.0-RC2-revb10659f0fc18b58b90929cfdadde94544d202c4a/ >> >> Thanks, >> Mike >> > > > -- > Anshum Gupta >
