Yes, I agree. I will put together a release candidate today.
Dave
On Sat, Dec 11, 2021 at 5:15 PM Michael Bien wrote:
> agreed. I think going right to 6.1 would be the preferable path since I
> think enough happened that it warrants a larger increment while the changes
> itself are small enough
agreed. I think going right to 6.1 would be the preferable path since I
think enough happened that it warrants a larger increment while the
changes itself are small enough to not cause trouble during upgrade.
I would try to avoid branching into two releases if somehow possible
unless it is mot
Yes, indeed! Thanks for pushing on this Michael. I was thinking that we
should do both a 6.0.x release and something called 6.1 (from master), but
now I'm thinking we should just do one 6.1 release and encourage folks to
upgrade to that. Thoughts?
Dave
On Sat, Dec 11, 2021 at 4:32 PM Michael Bie
all PRs are integrated, would be good timing for 6.1 :)
-michael
On 18.09.21 03:19, Dave wrote:
I think that's a great idea. There have been a lot of changes since our
last release from master.
I'd be happy to manage a release, or help somebody else to do it if they'd
like to go through and l
I think that's a great idea. There have been a lot of changes since our
last release from master.
I'd be happy to manage a release, or help somebody else to do it if they'd
like to go through and learn the process.
Dave
On Thu, Sep 16, 2021 at 1:36 AM Michael Bien wrote:
> Hello Everyone,
>
>
Hello Everyone,
now that JDK 17 is out I was wondering if apache roller should get an
update release too. The master branch was compatible with Java 17 for a
while already. My blog container is also using early access builds of
Java 17 for months without problems.
maybe in next month or two,
