Hey all, Just wanted to give a quick update: I didn't quite get to starting the release process last week, I'm currently blocked/waiting on some help from INFRA. (solr-operator releases require dockerhub karma that I don't currently have. I've asked for that here: https://issues.apache.org/jira/browse/INFRA-23517).
But with any luck I'll be able to start the release as soon as that's cleared up. Best, Jason On Wed, Jul 20, 2022 at 12:06 PM Houston Putman <[email protected]> wrote: > > This sounds good to me. We have whittled the v0.6.0 issue list down quite a > bit, so it should be close to ready. > > Tim, I added that issue as a blocker for the release. > > Jason, when going through the release steps you can move #436 to the next > milestone, as we won't get to it for this release. > > Thanks for volunteering Jason! > > On Tue, Jul 12, 2022 at 3:47 PM Timothy Potter <[email protected]> wrote: > > > sounds good Jason ... I have some code in the works for issue 390 (pr > > up soon) and will probably take a look at the other TLS related issues > > over the next few days as well. > > > > On Mon, Jul 11, 2022 at 11:27 AM Jason Gerlowski <[email protected]> > > wrote: > > > > > > Hi all, > > > > > > solr-operator has had a good few bugfixes and improvements since we > > > did 0.5.1 this past March, so I wanted to volunteer to RM an 0.6.0 > > > towards the end of July. > > > > > > The "milestone" (https://github.com/apache/solr-operator/milestone/7) > > > we use to track remaining work for 0.6.0 shows that all but one issue > > > has a linked PR. Hopefully we can get these merged sometime in the > > > next, say, 2 weeks, and I can target July 25th to start working on the > > > release process? > > > > > > If anyone has issues in mind that _aren't_ currently in the milestone, > > > please add those sometime early this week so there's time to fix or > > > triage them before the end of July > > > > > > Best, > > > > > > Jason > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
