Write release notes for v5.0.0

[RubenVerborgh]

Include upgrade notes (see #946)

[rubensworks]

I assume this is for the CHANGELOG.md?
How is this file currently updated? Manually, or with some tool?

[kjetilk]

Yeah, I think we can put it in there. Right now, it isn't updated. I spent an hour trying to hack a tool so that we could use the DOAP changeset vocab to maintain the changelog, like I do with my Perl modules, but it wasn't that straightforward to extract out of the toolset.

[rubensworks]

the DOAP changeset vocab to maintain the changelog, like I do with my Perl modules

Oh, nice :-)

but it wasn't that straightforward to extract out of the toolset

I recently created manual-git-changelog for automating changelogs as much as possible in my projects. Not sure exactly what the release workflow for NSS is exactly, but if it matches with my workflow, then this might be a useful tool to use here.

[melvincarvalho]

Pod owners also require a script, or document, explaining back out the file system changes.

See :

#950 (comment)

[RubenVerborgh]

That's not planned at the moment; we first need evidence that more than one person in the community needs this. This change has been pending for over a year and no one else reacted or proposed a timely alternative, so I'm confident we're good.

[melvincarvalho]

@RubenVerborgh understood, but disappointed. For the record, I strongly think this should have been engineered as a switch or config option. Also the file system changes should have been in its own (major) version.

As a pod owner, the upgrade performs changes to every user's file system, without their control or consent, and without a clear way to back that out. It also breaks compatibility with every other solid server out there including every version of node solid server other than 5.0.0. This is not a change to be taken lightly.

With my solid.community hat on, we will wait until this change is considered stable on other pods, and back out instructions are established, before moving to this version. My estimate is that 1-2 weeks after the first large pod moves, we should be ready. Any and all documentation will be extremely helpful.

[rubensworks]

Just my two cents:

For the record, I strongly think this should have been engineered as a switch or config option.

This would mean that two systems need to be maintained, which requires additional effort and becomes an additional source of bugs.

Also the file system changes should have been in its own version.

5.0.0 is a major update, so IMO this is the perfect time for this transition :-)

It also breaks compatibility with every other solid server out there including every version of node solid server other than 5.0.0.

Hence the major version change.

[melvincarvalho]

@rubensworks thanks for the comments, you make good points imho. Just on one, which I think is relevant to this thread.

This would mean that two systems need to be maintained, which requires additional effort and becomes an additional source of bugs.

BTW This is pretty normal in the node ecosystem. For example, node 8 is supported for quite some time after the release of node 10. Similarly with ubuntu etc.

What is happening here is that a cliff edge is being introduced with little or no concern for those running pods. My point is that in such a scenario, documentation becomes all the more valuable.

[RubenVerborgh]

@melvincarvalho Here's how discussion works. Either you reply to my technical arguments and you bring evidence that >1 person is affected, or I refrain from further discussion and just move on as planned.

Since you have not replied to my technical points in the other thread, they still stand and there is no value in continuing.

[melvincarvalho]

@RubenVerborgh understood. Thank you for your time and responses. In general, my posts were not specifically directed at you.