https://github.com/apache/solr/pull/5067
I'll merge this after the conference, if I get no feedback to the contrary. On Fri, Oct 9, 2026 at 12:29 PM David Smiley <[email protected]> wrote: > > I'm going to remove them from the release wizard. The release > specific CI jobs themselves can be disabled until we are sure we don't > want them. > > On Thu, Oct 1, 2026 at 1:15 PM Eric Pugh via dev <[email protected]> wrote: > > > > I think simplifying is fine, and if we find issues we can always re-add > > them back? > > > > On 2026-09-28 16:40 UTC David Smiley wrote: > > > In the interest of streamlining releases (e.g. the release process) > > > and maintenance generally, I question the value of CI jobs for > > > releases. There is toil in making those jobs and removing/copying > > > them. A release branch is generally pretty darned close to the dev > > > branch it came from (e.g. branch_9x). Furthermore, IMO, the release > > > process itself should sufficiently validate the release. Contributors > > > do as well on their OSs & JVMs. > > > > > > I only see one gap so far -- docker tests. It'd be easy to add that > > > as a step for the smoke tester, maybe conditionally if the docker > > > daemon is running. The alternative of depending on CI means adding to > > > docker-nightly.yml on each release, and forgetting or eventually > > > remembering to remove. Not to mention, those nightly runs are costing > > > somebody money for dubious value. > > > > > > ~ David Smiley > > > Apache Lucene/Solr Search Developer > > > http://www.linkedin.com/in/davidwsmiley > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > > > > > > > > Disclaimer > > > > The information contained in this communication from the sender is > > confidential. It is intended solely for use by the recipient and others > > authorized to receive it. If you are not the recipient, you are hereby > > notified that any disclosure, copying, distribution or taking action in > > relation of the contents of this information is strictly prohibited and may > > be unlawful. > > > > This email has been scanned for viruses and malware, and may have been > > automatically archived by Mimecast, a leader in email security and cyber > > resilience. Mimecast integrates email defenses with brand protection, > > security awareness training, web security, compliance and other essential > > capabilities. Mimecast helps protect large and small organizations from > > malicious activity, human error and technology failure; and to lead the > > movement toward building a more resilient world. To find out more, visit > > our website. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
