[HECnet] PyDECnet

[Paul Koning]

Correct.

I'm sorry, I guess I made things confusing.  My comment was in response to Johnny's observation that those upgrading from long-ago versions would also see a bunch of other improvements and new features.  Yes, but also if you go back far enough you may need to tweak your DECnet config file.

I should have been more explicit.  And I'll also try to make sure that when I put out a new version that does include a need to change any settings or the like (i.e., something worthy of a CHANGES.txt entry) it will go out with a note in the annoucement saying so.  In other words, you should be able to rely on "if I didn't say anything to the contrary, a new version is compatible with the previous".

	paul

> On Apr 14, 2021, at 11:30 AM, Robert Armstrong <bob at jfcl.com> wrote:
> 
>  Ok, I'll bite - either I'm missing something or you're being overly
> cautious.  I just checked out version 582 and the last change reported in
> the CHANGES.txt file is for version 575.  Is it safe to say there are no
> significant incompatibilities in this version?'
> 
> Thanks,
> Bob
> 
> 
> -----Original Message-----
> From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf
> Of Paul Koning
> Sent: Wednesday, April 14, 2021 7:29 AM
> To: hecnet at update.uu.se
> Subject: Re: [HECnet] PyDECnet
> 
> Thanks Johnny.
> 
> When installing upgrades of PyDECnet, be sure to review the file CHANGES.txt
> which is in the top level directory of the repository.  It doesn't show all
> the changes (that's what the Subversion log is for); instead, it calls out
> changes that are user-visible, for example changes in how the config files
> are used.
> 
> 	paul
> 
> 
>