Unify and fix CHANGELOG
format (or discuss why they should be not)
#3
Labels
documentation
Improvements or additions to documentation
enhancement
Improving existing functionality
I2
Regular impact
S1
Highly significant
U4
Nothing urgent
"NEOFS" part has its own format (node, gates), neo-go has a different one. I think none of them is bad but they are just different.
A new one
CHANGELOG
was born recently -- SDK. I think it is more like "NEOFS" thing, not aneo-go
one butCHANGELOG
adopted theneo-go
way.IMO, the same format allows having a better contributing/user experience. But if
neo-go
has its own and somebody has gotten used to it let it be like that. "NEOFS" repos use a well-known format (a little bit extended).NOTE: the more that issue is being ignored, the harder its solution applies to SDK (I do not think changing the format is a good thing, let it be done once at the beginning step).
I think any issue solution should be documented in that repo.
The text was updated successfully, but these errors were encountered: