Sigil 0.8.5 Released
 

Info and packages.

The packages link is dead.

The blog post mentions the whole lots-of-changes thing, and that there is no source revision to look at. Can I suggest for the sake of less confusion, that in the future development happens on a feature branch, and HEAD is reserved for completed changes? Then we can, like, tag a release...

It is traditional, after all...

As for FlgihtCrew, validation isn’t going away.

:D


eschwartz said the rest

This has been fixed. GitHub won't allow you to make a release without a tag.

There is now.

Um... No, that's asinine. You can easily create a branch based on a tag and use that for the basis of bug fixes. Really for each release it should get it's own maintenance branch so head isn't tied up and not able to accept changes.

Realize that even complete feature changes made to head aren't always suitable for a bug fix/maintenance, PATCH release. So this situation wouldn't have been averted by only accepting complete feature changes into head. The only way to truly allow for patch release while continuing development is for me not to be lazy and to create maintenance branches for every release so fixes like this can be tracked.

Hi,
The packages seem to be there now. At least I can see them. User-none made this release at my request purely to fix the "Disappearing CSS" bug and "Crash in Create HTML toc" that were recently reported.

Given the huge restructuring that Sigil is undergoing, we decided to handle that in master instead of the PyExperiment branch because it is effectively a one way street and we felt that the end of the 0.8.x line had been reached. I did not forsee the need for a Sigil 0.8.5 release so soon after Sigil 0.8.4 and before the alpha series of the Sigil 0.9 releases.

Take care,

KevinH

The packages link brings up a 404 error.

Jon -- the blog page has the corrected link, it is https://github.com/user-none/Sigil/releases/tag/0.8.5

John is still correct: Post 1 'packages' is bad

Um, yes... I am aware, hence why I didn't say he was wrong (not correcting him implies I agree) -- but I figured posting the corrected link would make everyone happy...

I was not sure what 'Packages' was supposed to link to.
Source Code?
or
Installable.

I can 'fix' the link once I am positive I am not going to do something else wrong :o

Hi theDucks,

I took care of that. It should now work.

KevinH

Same as this one: https://www.mobileread.com/forums/sho...d.php?t=255412 (still stickied?)
Or the packages link on the "info" page.

It points to the GitHub "release" tag, with attached Win/OSX/Source uploads.

Now Un stuck :thanks: