
all bugs should be fixed in the master branch first The process I suggest for the 1.0.1 release is as follows: The 1.0.x maintenance releases will be made from thatīranch whenever enough changes have accumulated to justify a release. Theġ.1.x development releases will be made from that branch every otherģ) There is now a git "stable" branch, where only important bug fixes
#The talos principle demo gold star puzzle code
If you sent patchesĪnd they didn't get applied during code freeze, please rebase themĢ) Development will continue as usual in the git "master" branch. Shipped 1.0, here are a few notes on future development:ġ) Code freeze is over, patches are accepted again. Now that I'm starting to recover from the shock of having actually News: Stable and Development versions of Wine releasedĪ post from a few weeks ago by Alexandre Julliard concerning future Wine development:Īgain, congrats to everybody for the 1.0 release!
#The talos principle demo gold star puzzle windows
Think of it as a Windows compatibility layer. Wine is an open source implementation of the Windows API on top of X and Unix. Serves to inform you of what's going on around Wine. Its main goal is to be really really ridiculously good looking. This is the 349 issue of the Wine Weekly News publication.
