I will update the upgrade to be a real upgrade command. that is, to read and replace things that matter, keeping any other customizations.
I will be done by tomorrow. On Sat, Oct 29, 2022 at 11:03 AM Clebert Suconic <clebert.suco...@gmail.com> wrote: > > We should actually review this before we release. > > > our scripts in artemis are a bit messy. > > The idea of the artemis.profile was to be a single point o update > between releases, but now variables and locations have spread into > artemis, artemis.cmd, bootstrap.xml, jass-security-manager.. > > > Is there a way we could clean this up so on future releases we only > have to change the artemis.profile for a release? (mostly) > > > if semantics have changed and we require a new setting is one thing.. > .but anything about the instance and locations should be in the > artemis.profile > > > > otherwise we just get rid of it, and place everything on artemis > initial script itself. (if we can't have a single point anyway). > > > > > > > > > > On Fri, Oct 28, 2022 at 6:11 PM Clebert Suconic > <clebert.suco...@gmail.com> wrote: > > > > We should finish https://github.com/apache/activemq-artemis/pull/4246 > > before we do a release. > > > > > > We should probably update the upgrade nodes with the new ./artemis > > upgrade command.. .which I will do next week... but I would appreciate > > any feedback so we can finish it before we release. > > > > On Mon, Oct 24, 2022 at 4:36 PM Justin Bertram <jbert...@apache.org> wrote: > > > > > > I would like to put Artemis 2.27.0 up for vote next week mainly due to > > > CVE-2022-42889 [1] [2]. Please send any PRs you want in this release ASAP. > > > > > > > > > Justin > > > > > > [1] https://nvd.nist.gov/vuln/detail/CVE-2022-42889 > > > [2] https://issues.apache.org/jira/browse/ARTEMIS-4060 > > > > > > > > -- > > Clebert Suconic > > > > -- > Clebert Suconic -- Clebert Suconic
