change script wording for v.1.4.0 release

neo4j-devtools / neo4j-desktop

The Neo4j Graph Platform, on your desktop OS.

19 stars 1 forks source link

change script wording for v.1.4.0 release #101

Closed jk05 closed 3 years ago

jk05 commented 3 years ago

change wording to v1.3.12 (released as v1.4.0)
didnt change any other folder naming to keep the links intact if they have been shared already (not sure if it would redirect correctly otherwise)

linuslundahl commented 3 years ago

Hmm, I think we need to rename the folder to 1.4.0 and also the title of the file. Omit any mentions of upgrade since it's not needed anymore. But I want Anurags input and maybe also @nglgzz has some input here.

jk05 commented 3 years ago

I think the upgrade one may still be needed if users haven't already done this for Canary, as its Canary specific. As for the rest of the naming, yes can wait on input to be sure.

linuslundahl commented 3 years ago

I think the upgrade script was only needed for a brief time, I'm not sure it's needed anymore? Might need to keep it around, but then I think we should separate this documentation into two files.

linuslundahl commented 3 years ago

So, upgrade scripts should stick around. But I still think we should create two separate documents/folders for this. To not confuse users, the downgrade script can be linked to from the upgrade doc since Canary users could want to downgrade too. But @nglgzz, the upgrade script will never be required for the production build, right?

nglgzz commented 3 years ago

Yeah you're right, the upgrade script is not needed for production and it probably makes sense to split the scripts in different folders to avoid confusion.

anutan76 commented 3 years ago

Linus asked me to review the feedback and I'm fine with the proposals here. Makes sense to separate into 2 files and link the two. In terms of a change in the link, I can edit the link I posted on slack. So, if it's beneficial to update it, let's do that.