Nigthlies for Windows
No sure that the servor works well since yesterday.
As you see, yesterday, the Nightly "808322a" appears three times.
For now, the Nightly "1752c2c" (and I don't understand to which commit it corresponds today?) displays twice.
Thanks for advance to watch what happens.
Comments
Looks like the switch to the 2.0 branch explained here http://dev-list.musescore.org/Preparing-MuseScore-2-0-1-bug-fix-release…
is not really good yet. I tried another approach... Let see.
In reply to Looks like the switch to the by [DELETED] 5
Little problem with the server maybe today. One single Nightly for now, the "35e2f4d"
And I don't understand why since a few days, the references don't correspond, as before, to any commit of the day?
Not a big deal, except that it complicates the identification and investigation work if necessary.
e.g: "35e2f4d" corresponds to which commit of today in this list?
In reply to Little problem with the by cadiz1
From what I understand, you're seeing the commit numbers from the "2.0" branch (for the 2.01 release), not the true nightly commits and the numbers don't coincide. If you want the true nightly version, I guess you'll have to get it from my page for the time being. I'm still keeping a few online at a time.
In reply to From what I understand, by schepers
For the explanation, that's what I guessed indeed.
But for the unique Nightly today, it is something else.
Thanks for help as always.
In reply to For the explanation, that's by cadiz1
I should clarify. The nightly commit and 2.01 branch commit numbers are never the same (I said don't coincide, which doesn't mean the same thing). If you check on GitHub, and select the 2.0 branch, you will see the build numbers from the download page.
In reply to I should clarify. The nightly by schepers
If you want to help on the development process, please use the "official" nightlies, which are indeed build from the 2.0 branch and will become 2.0.1 soon.
Developers currently commits on the master branch and I manually cherry pick commit a couple of time per day and put them in the 2.0 branch. The nightly process happens only when I push these changes in the 2.0 branch.
In reply to If you want to help on the by [DELETED] 5
No Nightly today for Windows (comparing with a few for Mac)
In reply to No Nightly today for Windows by cadiz1
Check again now...
In reply to Check again now... by Jojo-Schmitz
Yes, it works from now, thanks.
In reply to Yes, it works from now, by cadiz1
The two last Nightlies for Windows are corrupted :(
In reply to The two last Nightlies for by cadiz1
see also https://musescore.org/en/node/61071
In reply to see also by Jojo-Schmitz
I'm RDP'd into my PC (it's holiday here in Canada today) and kicked off the latest nightly build. You will see the download when it's ready.
In reply to I'm RDP'd into my PC (it's by schepers
Thanks! ;-)
In reply to Thanks! ;-) by cadiz1
No Nightly for Windows for now.
The server is down?
In reply to No Nightly for Windows for by cadiz1
Hmm, and I just built the latest.
In reply to No Nightly for Windows for by cadiz1
Patch tuesday... The server is up and running again.
In reply to Patch tuesday... The server by [DELETED] 5
Sorry to repeat myself: no Nightly for Windows for today.
In reply to Sorry to repeat myself: no by cadiz1
Nightlies for may 27 and 28 are in. No nightly today yet because no commit.
In reply to Nightlies for may 27 and 28 by [DELETED] 5
Yes, I had seen, thanks. I understand quickly when there is a potential concern (when some commits have been merged since one or two hours or more, eg last Wednesday), and when there is no nightly because no new commit has been merged, as today :)
That said, a day without nightly is long as a day without bread (according to the French expression)!
In reply to Yes, I had seen, thanks. I by cadiz1
No Nightly today?
For this: https://github.com/musescore/MuseScore/commit/55c0c4ffacc8de19daecb6512…
In reply to No Nightly today? For this: by cadiz1
No news of the last nightlies for Windows.
The last ones available are: