Updating through npp occurs very late



  • I have observed that my other software updating softwares (say, PatchMyPc, Sumo) start showing npp’s new release available much earlier but if I click on npp’s Menu-?-UpdateNotepad, it keeps of shoing “No update available” for days, even week and even longer.

    Seems you are putting the update in automatic channel quite late. could you please elaborate after first release through direct download, how long it takes for update to become available through automatic update. What are your concerns and can you shorten it enough so that within 1-2 days it become available there?

    Nowadays almost all softwares are summarily auto updating whenever they wish, they don’t seem to wait a second long.

    Thanks.



  • @V-S-Rawat ,

    As has been said many times in this Community Forum, the auto-update is usually triggered 1-2 weeks after initial release, just in case there are major regressions that weren’t found during the internal testing and the release-candidate timeframe. After a sufficient time period, Don then decides to trigger the auto-update when he has time to do the triggering.

    For example, on v7.9.1, release was on Nov 1, and Don triggered auto-update on Nov 11.

    I would actually expect the trigger in the next couple days on v7.9.2, unless Don thinks that v7.9.3 is coming soon enough that he won’t bother triggering the auto-update on v7.9.2.

    Nowadays almost all softwares are summarily auto updating whenever they wish

    And I would bet that most of those have corporations behind them with full-time paid staff. Notepad++ is purely volunteer-developed, and the primary developer maintains his executive authority on all releases, because in the end, it’s his software that he’s responsible for – but his Notepad++ is just in his spare time, and not what he is paid to do for his “day job”.

    If you would like to pay his salary and benefits, so that he can work on Notepad++ full-time and give you instant gratification for new-version releases, you might want to make the offer. Otherwise, I recommend being patient for the week or two between release and auto-update triggering.



  • @V-S-Rawat

    Given your recent ranting and raving and blaming about a new version of PythonScript destroying some of your data, your new concern is somewhat at odds with this, especially since the delay is designed to protect you from a critical flaw in new software, that could in fact destroy some data or, minorly, break your workflow.

    I guess a “(not) wait a second long” stance what you’re asking for, as long as there comes a guarantee of it being being perfect software. Because if it is not perfect and bug free, oh man, I can already hear your whining about it.



  • @PeterJones said in Updating through npp occurs very late:

    I would actually expect the trigger in the next couple days on v7.9.2, unless Don thinks that v7.9.3 is coming soon enough that he won’t bother triggering the auto-update on v7.9.2.

    Hmm. I’m not a mind-reader, but I’m not sure about this one; here’s why: A lot of minor problems seem to have been uncovered with 7.9.2; more than is usual for a release. I think it will take some time to iron them all out, so I predict it will be a bit of time before 7.9.3 appears (well, unless Don has the attitude of “fixed half of them, let’s get this out and work on the other half”).



  • @Alan-Kilborn ,

    Another theory is that there are enough problems in v7.9.2 that he doesn’t want to trigger, but not enough that he needs an “emergency! get-7.9.3-out-the-door!” rush… so maybe he’s taking his time on v7.9.3, to make sure the problems are solved, but still won’t trigger auto-update on v7.9.2.

    I’m fine with that. It is always up to Don whether he feels a given release should trigger auto-update or not, and I don’t think I’ve ever disagreed with him whichever way the decision has fallen.



  • So this great group is now controlled by Trolls like @Alan-Kilborn and @PeterJones who start personally attacking members for asking a simple question or suggesting a simple change?

    If pythonscript using python3 without telling destroys my data, and I say so, then I am ranting? What do these trolls expect me to do? Should I keep silent and tolerate everything?

    This is the general change in world towards increased intolerance that things like freedom of expression have become a thing of past. May be these two are Trump sympathizer and sad to see him getting bootted out so they are taking it out on me or everyone here.

    Shame on the ilk of the two of you that you two four-handedly destroyed this great group. Millions of pythonscript or npp users never visited this forum and are still using these software, seems they were wiser than me that they avoided the filth like you two.

    If nothing can be changed, or even suggested or even requested to be considered, then close this forum, everybody will take whatever is served or leave it.

    Sad day for me.



  • I have earlier suggested one or two years ago that the solution for this wait is to differentiate between alpha, beta, release candidate and final stable release. Only final stable release can reach automatic update channel, and meanwhile interested and wiser users can do alpha, beta, release candidate testing.

    I present the suggetion again.

    Thanks.



  • Thinking about it, I think my problem is that when I see my Sumo or Patchmypc show that npp update has been release, I have to make a mental note to track that. I often run npp for no work and try to update it. and I find “No update available”, that contradicts other software.

    The underlying worry could be that I may be thinking that automatical update channel might not work some day and I will continue using older version when better one is available.

    Anyway, my another suggestion that will further infuriate these trolls is that when an update has been released and not yet triggered in automatic update channel, in those TWO WEEKS, instead of “No update available” message, show the message sort of “v6.9.2 released, Automic update channel will be triggered on 15 Jan 2021”.

    Then I can edit my mental note and will not bother you here.

    Thanks.



  • @V-S-Rawat said in Updating through npp occurs very late:

    If pythonscript using python3 without telling destroys my data, and I say so, then I am ranting?

    Yes, you turned it into one.
    But let’s not belabor that further; it’s been done.

    I have earlier suggested one or two years ago that the solution for this wait is to differentiate between alpha, beta, release candidate and final stable release.

    All we have here now is RC and (presumed) stable release.
    The reason it is, and always will be “presumed”, is that the base of users that try the RC is small compared to the size of the entire user pool. Sure, some problems are definitely detected that way, but…

    Only final stable release can reach automatic update channel

    Again, yes, that’s how it works. Or is supposed to work, due to limited knowledge about how “stable” is stable.

    I present the suggetion again.

    I didn’t know that it was YOUR suggestion.
    If so, thanks. Nice job with that.

    my another suggestion … is that when an update has been released and not yet triggered in automatic update channel, in those TWO WEEKS, instead of “No update available” message, show the message sort of “v6.9.2 released, Automic update channel will be triggered on 15 Jan 2021”.

    It isn’t always a fixed “TWO WEEKS” or any fixed time period, AFAIK.

    It isn’t a bad suggestion, but it would be up to @donho to like it and implement (something like) it.



  • the issue is - “other software reporting npp update is available” and “npp - ? - update npp - reporting ‘no update available’” — these are contradictory and thus must be confusing many users like me. I am the first one to bring the issue to your knowledge here.

    So, I suggest

    • trigger automatic update for all releases whether alpha-beta-gama-delta-RC.
    • just show in the notification from npp - ? - update npp what release it is - I mean,
      say, instead of ‘no update available’, show like this
      6.9.2 alpha update available. Update it?
      6.9.2 beta update available. Update it?
      6.9.2 RC update available. Update it?
      6.9.2 final stable release update available. Update it? remind about it? ignore it forever?

    then whoever is happy with whichever update, he/ she will update that, and others will not, and I will always wait for final stable releases.

    This will also help contributors who do wish to test trial versions, because they will get it updated through update channel immediately, instead of them going to site, downloading it and installing it manually.

    We are not here to create problem or undermine npp or to create work for developers. All what can be done automatically should be left to machine to handle. We only need to give effective instuctions to machine that will satisfy everybody’s different requirements.

    Thanks.



  • @V-S-Rawat

    Your views have been noted; well, at least by anyone that reads here.
    If you’d like someone to see it that cares and has power to do something about it, you’d have to open an official request for it on github.




Log in to reply