Above version is released and hatched in MBSE_BBS.
Also available on SF within file group 1.0.7.
This reflects the code base at least on CVS as amendment 1.0.7.11B is
not present on git or Hg.
This change and the latest is as follows as shown in Changelog but
note that this only covers changes for 2019 and Changelog_2018 covers
2008 - 2018 : @Andrew you might want to update git and hg versions.
I propose that at the next major release (1.1.0?) we drop updating the redundant repositories and all switch to using the same one. My
personal inclination is to use Git, but if there's a reason you prefer
to use SVN, I'm all ears.
Hello Vince!
16 Mar 19 18:44, you wrote to all:
Above version is released and hatched in MBSE_BBS.
Also available on SF within file group 1.0.7.
This reflects the code base at least on CVS as amendment
1.0.7.11B is not present on git or Hg.
Sourceforge has discontinued active use of CVS; I believe your changes
are in the SVN repository on Sourceforge.
This change and the latest is as follows as shown in Changelog
but note that this only covers changes for 2019 and
Changelog_2018 covers 2008 - 2018 : @Andrew you might want to
update git and hg versions.
I will update them tonight hopefully. Going forward, I think we need
to select a single source code management solution, to avoid having
multiple repositories that need to be kept in sync with each other.
I've primarily been using Hg, as that's what Michiel was using before
I got into this project. I believe that Jame was using Git in his
Debian packaging work. You have started using SVN recently.
I propose that at the next major release (1.1.0?) we drop updating the
redundant repositories and all switch to using the same one. My
personal inclination is to use Git, but if there's a reason you prefer
to use SVN, I'm all ears.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 368 |
Nodes: | 16 (2 / 14) |
Uptime: | 41:39:03 |
Calls: | 7,885 |
Calls today: | 3 |
Files: | 12,962 |
Messages: | 5,787,523 |