Doh! Thanks for the explanation. I don't know why I thought this was a stable release.
Yea, automating these types of things is tricky (I had the same problem with the Meld installer I maintained). IMO, Meld stable releases are frequent enough that we're probably OK without MSIs for unstable builds. If Windows users really want to get the unstable release, they can do it the old fashioned way (installing Python and extracting the tarball). On Mon, Jul 13, 2015 at 4:31 AM, Kai Willadsen <[email protected]> wrote: > On 12 July 2015 at 15:16, Keegan Witt <[email protected]> wrote: > > Awesome! Don't forget to update the download links on the homepage when > you > > get a chance. > > Ah, I assume you're referring to the Windows MSI link? > > So... 3.13.3 is a development release (because Meld does odd/even > stable/unstable numbering). I haven't been providing Windows MSIs for > unstable releases, simply because it takes me at least as long to do > the MSI release as the whole of the rest of the release process > combined. I did one for 3.13.3 because someone asked for it, and > because I'm hoping to release 3.14 soon. > > If there's interest in unstable Windows releases, I could look at > trying to automate the Windows releases a little more, but I haven't > found the time so far. > > But anyway, there's no link to the MSI simply because it's still > unstable, so the recommended Windows release for download is still the > latest 3.12. > > cheers, > Kai >
_______________________________________________ meld-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/meld-list
