As mentioned, wikis can provide a streamlined collaborative editing
workflow that's less labor intensive than updating a website. They can
promote collaboration by providing specific tooling to support comments,
revisions and iteration.
In terms of preservation, GH wikis act just like any other
I would like to try a wiki for design documents, I think it would be
less cumbersome than the website and we can always link from the
website and issues to the wiki. I think its ok to give it a try and
abandon it in the future, if abandoned would just need to properly
communicate that. The
You would need to upgrade both.
On Sat, Feb 25, 2023, 07:08 Logan Jones wrote:
> Christopher,
>
> Understood. For an Accumulo upgrade, do I need to upgrade clients and
> servers simultaneously? Or are the 1.10 clients compatible with 2.1
> servers?
>
> -Logan
>
> On Sat, Feb 25, 2023 at 4:48 AM
I am +1 on the idea of using some sort of Wiki (either Github or
Apache confluence cwiki) for design discussions and related docs. A
wiki is so much easier to update information quickly rather than
trying to use SVN or the website repo and when working on design
changes as document updates can
I reverted the change. I didn't think it would be a big deal, but if it
requires discussion, then let's discuss it.
I'm looking for a place to host information related to internal design
discussions. I envision these to be living documents that will be updated over
time as the
Christopher,
Understood. For an Accumulo upgrade, do I need to upgrade clients and
servers simultaneously? Or are the 1.10 clients compatible with 2.1 servers?
-Logan
On Sat, Feb 25, 2023 at 4:48 AM Christopher wrote:
> Thrift makes a lot of breaking changes between releases. It is not a
Thrift makes a lot of breaking changes between releases. It is not a simple
operation to bump it. We have already made the change to do it and included
updates in 2.0 and 2.1. 1.10 is the legacy version that is to remain stable
until it is EOL in November. If libthrift bugs are a concern to you, I
I don't recall a discussion about this change, but I think it goes against
previous efforts to make the website the one canonical location for our
documentation. I don't even think infra is backing up wiki repos, so there
wouldn't even be a record of the wiki contents in ASF spaces (vs. the main
