Thanks Attila for your input.
While this has been there - I am not sure if it is being actively followed.
I think it might be better in such a case, to enforce checks for design
changes so that devs mandatorily update design docs as part of such PRs.
Thanks
On Sat, 15 Mar 2025 at 23:43, Attila D
Hi Wei-Chiu, Abishek,
We had this process [1] for a few years now that design docs should be
created as markdown in hadoop-hdds/docs/content/design via pull
request (some examples at [2]). Rendered versions are available on
the website [3].
[1] https://ozone.apache.org/docs/edge/design/ozone-enh
Thank you for starting this discussion.
I actually had a proposal for this scenario.
For large projects like Typescript and React which are always changing,
they maintain a separate repository for tracking design documents.
This is really useful in:
1. A single place for tracking every design deci
Ok. Thanks for the heads up.
Bumping it up to Blocker.
I'm moving the rest to target 2.1.0
On Wed, Mar 12, 2025 at 2:01 PM Attila Doroszlai
wrote:
> > (the remaining tasks of HDDS-11754 don't look like must-do's)
>
> I think HDDS-12327 needs to be investigated. Finding upgrade problems
> after
