YAM Development (#4) - Developer-Version expired, don't like it :-( (#91) - Message List

Developer-Version expired, don't like it :-(
 solved

I am using AmigaOS4 and had problems using the old 68k-Version of yam. So I wanted to try the current nightly build for os4 and it runs very well and much better than the old one. Today, yam told me that this version had expired and that I have to download a more recent version. But I don't want this! As I told, the old version runs perfectly and with a new nightly build, there is always the risk that something goes wrong. I downloaded the current nightly build and it seemed it was the same version as my old one. This is good in one way, as I know it works fine, but it was a somewhat unnecessary download with my slow modem only to get rid of that requester. So is there a way to turn off that requester and start yam anyway if it is working so well as the current version does? Maybe by setting an environment variable? If I find a bug, I can always download a new nightly build before I report it.

Thanks,

Alex.

Tree View Flat View (newer first) Flat View (older first)
  • Message #357

    What does setting the I_KNOW_YAM_IS_UNDER_DEVELOPMENT envarc var do?

    This variable only disables the Developer warning requester. The Expiration after 30 days is still valid and there is, and will be, no way to disable it. If you use a developer version you always have to update it once a months.

    That's the deal. Period. :)

  • Message #356

    No sorry, there is no way to disable just the requester and that is on purpose. The idea of using a developer version is to be aware that this is a one way process only. I am getting too often outdated bug reports on versions prior to the actual one. So if you don't want to go that one way road, please stick to the latest official stable version out, which is of course 2.4p1

    Yes, I know that. But I don't think that this is a good solution for the users who have to use the developer version, because the stable version is not stable.

    What about releasing the current (OS4) version as stable? It may not have been tested enough, but at least in my experience it is much better than the stable one.

    Another suggestion: Build a bug report facility into YAM that opens a mailer window with the correct bug report address, but BEFORE doing so, it checks if there is a newer version of YAM available and if this is the case, it tells the user to download that version first and to test if the bug is still present.

    Sorry Alex,

    but the expiration is not going to change for the developer versions. As I explained already way too often, the developer versions are not meant to be used like stable versions. They are just snapshots of the current development and should be avoided or even not used for productive systems. And of course one more reason why I am providing this nightly build system is to give interested developers the easy possibility to try the latest development version and report bug and suggestions on it, not to give them "new stable versions". normal, ordinary users should keep to the latest stable versions which is still 2.4p1.

    I know that many users just install them because they can't wait for the new official release, that's why the expiration should force them to

    1. not report bugs on old versions.
    2. occassionaly update their versions to newer versions and force them with that to overthink their decision to install a definitly NOT stable version.

    So sorry again, but I see the nightly build system as an extra service for developers and advanced users and if they appreciate it they should not have any problem in installing a new/updated version each month. All I want to avoid is that old versions are floating around in the internet which do generate confusions to many people.

    Also the nightly build mechanism on my servers do automatically regenerate new builds once each month, even no change was made to the code base.

    As for the 2.5 release, you unfortunatly still have to wait a bit more. Currently I am on vacations around Canada, but as soon as I am back in mid January I will work on YAM again and still have one or two pending things for YAM until I can safely release a 2.5 version. But the final 2.5 version is to be expected in Q1/2005.

  • Message #355

    What does setting the I_KNOW_YAM_IS_UNDER_DEVELOPMENT envarc var do?

  • Message #354

    No sorry, there is no way to disable just the requester and that is on purpose. The idea of using a developer version is to be aware that this is a one way process only. I am getting too often outdated bug reports on versions prior to the actual one. So if you don't want to go that one way road, please stick to the latest official stable version out, which is of course 2.4p1

    Yes, I know that. But I don't think that this is a good solution for the users who have to use the developer version, because the stable version is not stable.

    What about releasing the current (OS4) version as stable? It may not have been tested enough, but at least in my experience it is much better than the stable one.

    Another suggestion: Build a bug report facility into YAM that opens a mailer window with the correct bug report address, but BEFORE doing so, it checks if there is a newer version of YAM available and if this is the case, it tells the user to download that version first and to test if the bug is still present.

    Alex.

  • Message #353

    No sorry, there is no way to disable just the requester and that is on purpose. The idea of using a developer version is to be aware that this is a one way process only. I am getting too often outdated bug reports on versions prior to the actual one. So if you don't want to go that one way road, please stick to the latest official stable version out, which is of course 2.4p1

    Sorry for that, but it is definitly necessary for a smooth developer process...

Tree View Flat View (newer first) Flat View (older first)

Attachments

No attachments created.