> put it up on the website in the developer section
We have this, maybe not overly perfect:
https://thrift.apache.org/docs/committers/ReleaseManagement.html
A lot of things have been effectively moved out and linked only during
the last CMS switch. We in fact had the contents pulled in from
On Thu, Apr 27, 2023 at 3:54 PM Jens Geyer wrote:
>
> Hello,
>
>
> > For what it's worth, you don't actually need to release more frequently to
> > declare additional versions as current or active. You could still make that
> > rare, and only do it for very critical issues.
>
> When there is
Hello,
For what it's worth, you don't actually need to release more frequently to
declare additional versions as current or active. You could still make that
rare, and only do it for very critical issues.
When there is opportunity people will use it, I'd guess.
There still might be value
Definitely off topic there (sorry!). Thanks for changing the venue for this
discussion.
I have never looked up who is on the Thrift PMC, so I don't even know who
is part of that and who isn't. But I wonder if there might be an issue of
not a large enough PMC if there isn't enough people on it
Hi,
this is to continue the slightly offtopic discussion that emerged on
https://github.com/apache/thrift/pull/2785
> > > You can still keep up the latest version in any release series
that you consider "currently active". Accumulo has the latest 1.10.x and
2.1.x right now. Hadoop has the
