Freemint 1.19

[sagudev]

When Freemint 1.19 will be released? Freemint 1.18 was released more than a year ago.

[ps68060]

Why not schedule an annual release and bump the version number accordingly ? ;-)

[mikrosk]

I guess there's not many reasons why not to left. Personally I'd like to take a look at #73, #41 and #32 and if @DavidGZ could find some closure to #70, that would be a really good start to think about release.

Also, it depends how much time @atic-atac has for updating README and other bits and pieces needed for a release.

Btw, 1.18.0 was released five years ago (Mar 17, 2013), Github releases can't have a custom date set so it's the date when I uploaded the archives.

[th-otto]

I think lots of other files in doc/ also need to be updated before a release, a lot of information there is not valid any more.

[mikrosk]

Yes, the docs are a mess. See also #2. Personally it hurts me to see it in such state but then again, an Atari developer's time should be invested into a better activity than sorting and converting docs. :-/

[ps68060]

I am just bumping this suggestion of going for a release of 1-19. I know some of the issues above are still open but are they likely to be closed in the near future ?

#70 is closed

[paulwratt]

is it just the docs atm, I think it would be fine/good to move to a yearly release. why were there no point releases for 1.17 onwards? How come there is also no 1.16.3 on the release page, that the last good version before 1.17.0.

[ps68060]

Mint is as stable and reliable as always and there seems to be a bit of a lull in new developments. A good time for a release ?

1.19 or 1.20 (2020) ?

[mikrosk]

Looking at the issues (even those I had mentioned earlier) I would like to see some of them fixed/sorted out. Also, Latz has been doing a wonderful job with documentation, I have a semi-final proposal pending in my mailbox.

Anyway, with all that Travis/Bintray stuff going on, why do you need it so urgently? New release will be current build + some README added.

EDIT: but I like the idea of 1.20 ~ 2020, yes. :)

[ps68060]

It's not urgent but it has been a few years since the last official release and I think it would be good to be able to announce a new version.

It's a small thing but does give a sense of achievement and an opportunity for us users to say thanks.

[ps68060]

It's been 5 1/2 years since the last release.

https://github.com/freemint/freemint/releases

Any chance of creating a new one ?

[mikrosk]

Again, see #85 (comment) -- it's actually 9 years. ;-)

I'm more and more inclined to have FreeMiNT like a rolling updates kind of "distro". One thing is missing, though -- instead of having "releases" and "snapshots" we should have just latest release in the releases section updated after each commit.

So random people looking for a working release would find it immediately even on github.

Another step could be that some particular pre-release/snapshot could be marked as stable enough or with some interesting feature and mark that as a release (for instance right now we have a really nicely working USB thanks to @Perdrix24, @czietz and @DavidGZ, that is certainly a reason to encourage users to use it more).

And yet another interesting point is the inclusion of #241 XaAES as an option.

[GokMasE]

And yet another interesting point is the inclusion of #241 XaAES as an option.

Yes, I would definitely like to see XaAES-Ozk available as an official alternative.

I suppose it needs its own branch on Github to handle that properly?

[th-otto]

As already said in other places, that is IMHO not an option. That would essentially double the efforts in maintaining FreeMint, and lead to totally confusion for users, and also for us when reading bug-reports.

[mikrosk]

It requires a separate branch but that's not a big deal (it's been already done).

@th-otto as the classic in open source development says, it is the one who writes code who makes decision. :) If there are people willing to maintain it, report bugs and use it, I don't care.

For the time being I don't mind backporting bugfixes. You may have noticed that for instance @GokMasE reports bugs to both builds, so it's the other way around, it helps me to realise whether it is a regression or missing feature altogether. Works for me.