Notepad++ 7.6.5 Release Candidate
-
I asked you to separate the run command files and macros …and this is not)
-
@Alan-Kilborn said:
What am I missing? Where is this “list”?
If you grab one of the zips from Don’s link (or presumably the installer) and dig into the change.log that’s included, you can find said “list”.
-
-
@PeterJones said:
If you grab one of the zips
Ah, okay…I’m used to software where you can quickly view the changes BEFORE bothering to grab it (if you don’t want it based on said list contents!)
:)
-
@andrecool-68 said:
I asked you to separate the run command files and macros
We have to be glad for what we DID get, and not make glib remarks about what we didn’t. :)
Unless you go to the Boycott / F*ck Notepad++ area. :)
-
@Alan-Kilborn said:
view the changes BEFORE bothering to grab it
Well, yes. But this is a release candidate, not a final release.
I’m actually quite happy that Don took the RC route; hopefully, that will mean the experienced users will be able to help find problems before the general public starts asking us all sorts of repeated questions here. :-)
-
@Alan-Kilborn
I don’t need falsification …I need a solution) -
“falsification” ?
And perhaps it is time for the eternal refresher: Notepad++ is free software.
-
@Alan-KilbornI
have no desire to include insult here …I asked the author to make changes …and if I’m not mistaken you are not the author of the program) -
to all:
guys, please don’t over-post this topic !!!
let’s only focus on thorough testing, reporting eventual bugs, or showing new features.
otherwise this release candidate attempt will fail.btw: i expect that everyone who just posted here, has already downloaded, installed and tested the 7.6.5 release candidate.
-
@Meta-Chuh said:
guys, please don’t over-post this topic
Good point, sorry.
I noticed that the RC refers to itself as “7.6.5”. In the about box. This is kinda bad as if it isn’t the final release then what does one do when reporting/evaluating-reported bugs? Always have to pay attention/ask-for version AND build time ?? We don’t want to be chasing down bugs because someone is accidentally using a RC (later down the line) and keeps insisting something isn’t working in 7.6.5 (when it is working in the real 7.6.5, just not the RC). Does this make sense to people??
Or if 7.6.5 RC fails, does that mean there is no real 7.6.5 release and we go to 7.6.6 RC, etc.?
Just wanna understand what the RC scheme plan is, if there is one…
-
@Alan-Kilborn
There’s no special scheme plan.
If RC is good, then the same binaries will be published as official release. Otherwise the regression is fixed then the same version number with RC2, etc…
The RC is not supposed to be out of community, so I think it’s OK. In the worst case, we have the build time to compare with.
