1.14.7 release plan #3407
Comments
|
+1 - this would help THORChain continue to provide Defi swaps between DOGE and other UTXO (BTC), EVM (ETH, AVAX, BNB), and Cosmos (ATOM) ecosystems. I have also heard from at least one wallet that they are having issues with this as well. We fully support releasing this ASAP! |
|
I'm game for this, as I believe this helps move along the mempool.space port that @alamshafil is working on, which I am a supporter of. I'm also willing help with french translations after the string freeze. |
|
Very good, I will help with any missing Italian translation strings (if any) when it's time. Following this. |
|
Added #2676 to low hanging fruit - I'm honestly not sure why this is still open in the first place. |
|
I'm able to help with translation strings for the various Chinese locales when time. |
|
Following. Would be happy to draft up some release notes as needed. Going to dig in to each of these PRs next week🙏Sent from my iPhoneOn Feb 8, 2024, at 8:33 PM, Anthony Chen ***@***.***> wrote:
I'm able to help with translation strings for the various Chinese locales when time.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
|
Added #3411 - doc update for WSL |
|
I've shifted the string freeze and final PR deadlines 1 day each because we're waiting on an important dogecoin-qt patch to be PR'd that changes strings. The shift does not change the planned release date: I'll personally simply work harder on the maintainer items. |
|
what # is the dogecoin-qt patch? |
#3412 is the PR that was preventing string freeze. |
|
Agreed on the release plan given the current situation. My runtime detection won't make it in this time, but no worries. Currently working on #3411, will build and test both 64 and 32-bit. |
|
It appears github projects have been used for past releases. Would it be
helpful to wrap these deliverables into one? Some of these appear on the
"review-merge board" but not all.
…On Wed, Feb 14, 2024 at 10:00 AM Ed ***@***.***> wrote:
Agreed on the release plan given the current situation. My runtime
detection won't make it in this time, but no worries. Currently working on
#3411 <#3411>, will build and
test both 64 and 32-bit.
—
Reply to this email directly, view it on GitHub
<#3407 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACZSY45FY6UWPCXQFLX4RSDYTT3SHAVCNFSM6AAAAABDABVLBKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNBUGMZTAOBRHE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Not really - we used board for milestones but they were kinda redundant. Do you think that doing so makes it clearer than the top post in this issue? |
|
It’s kind of tomato potato… when trying to track down the status of the issues/prs in this thread getblockstats had already been merged and it took me some digging to find it.Sent from my iPhoneOn Feb 15, 2024, at 1:08 PM, Old Dip Tracker ***@***.***> wrote:
It appears github projects have been used for past releases.
Not really - we used board for milestones but they were kinda redundant. Do you think that doing so makes it clearer than the top post in this issue?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
|
You can see it by the checkmark - I do my best to mark it as soon as I see something got merged - and the color of the PR icon (purple = merged, green is pending, grey = draft) |
|
Gotcha, thanks for clarifying. Sent from my iPhoneOn Feb 15, 2024, at 1:54 PM, Old Dip Tracker ***@***.***> wrote:
It’s kind of tomato potato… when trying to track down the status of the issues/prs in this thread getblockstats had already been merged and it took me some digging to find it
You can see it by the checkmark - I do my best to mark it as soon as I see something got merged - and the color of the PR icon (purple = merged, green is pending, grey = draft)
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
|
|
@georgeartem I cleaned up the 1.14.7 milestone, so that you can now also view the state of all PRs by querying for milestone:1.14.7 |
|
Thank you for doing that. Decentralized development practices are new to me. The type of thing I was suggesting is only really useful to help organize a full-time PM to assist with briefing “executive leadership” but since we don’t have any of that here it’s kind of up to the wisdom of the group. Appreciate you all 🙏Sent from my iPhoneOn Feb 16, 2024, at 5:09 AM, Old Dip Tracker ***@***.***> wrote:
@georgeartem I cleaned up the 1.14.7 milestone, so that you can now also view the state of all PRs by querying for milestone:1.14.7
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
|
|
As the string fixation has not been merged yet (turns out buying only 1 day was overly optimistic), I'm buying translators a week more because we cannot possibly expect all translations to be done within 2 days. I'm assuming #3413 gets merged today (2/17), so I'm shifting: translation deadline to 2/25 Still this month, not as fast as I hoped we'd be. |
This comment was marked as outdated.
This comment was marked as outdated.
|
1.14.7 is now frozen for all pull requests - except tail-end maintenance work (which is only the copyright update, any updates to release notes and version fixation). Open pull requests with a 1.14.7 milestone and mentioned above can of course still be reviewed and merged, as long as we see ACKs over the next 48h - maintainers can speed-merge anything that is non-controversial, if needed. |
|
I've removed the Arabic translation from this release target because there was no language review in time - this can be picked up on a more relaxed timeframe for the next release. Have also marked #3442 and #3448 as urgent, as they've been open for a longer time now, to not hold up the release. Thanks everyone for great work! It's been an amazing pressure cooker ❤️ |
|
Tag done: https://github.com/dogecoin/dogecoin/releases/tag/v1.14.7 I'm starting my gitian build and will report shasums here (using LXC) Attestation PR here: dogecoin/gitian.sigs#34 |
|
My Gitian checksums, from |
|
That's two matching sets. Can we get a third? |
I'm starting to prep the notarization of the macOs dmg now, because that's still a manual process under my Apple developer key, like last time (hopefully). A third match would make these binaries shippable. |
|
I can do the third build. I'll update once I get it working. |
|
I'm also trying to create the third build, but I've never done this before and I'm not sure if it'll work. |
|
I repeatedly error out here, could it be that my configuration of LXC is incorrect? |
No, it's the version. Gitian is EOL. LXC gitian only works on a bionic host due to breaking changes to debootstrap and you have to pre-download binaries too. I only run it on there because it's the best way to detect any prefix-jailbreak (like we found with xkb) because the image is created differently than docker. I'd recommend running a docker build for now unless you have a bionic host ready to use. |
|
Ah, now I feel stupid—I even remember reading #3095 around the last release. |
|
No need to feel that way! What used to be the simplest method is now an extremely complex monstrosity. Luckily we will soon start a new major and I'll take it upon myself to work on guix. Hopefully we'll be able to only need gitian 3 more times at most. |
|
I'm having other issues with docker now, from searching online it seems to be a problem with apt-cacher configuration Should my |
|
I think that's what I set |
|
The service is definitely running, and I even restarted and tried again to make sure, hmm. |
|
The specific error in the |
|
Re: lief. You need to get |
|
Thanks! I grabbed the file from another source in the meantime but the checksums line up. The build process is humming along now and I'll edit this message with my checksums,
|
|
Here are my Gitian checksums using Docker. Will update as it builds. Apologize for the delay, I had to restart the process due to issues with my computer. Gitian Sig PR: dogecoin/gitian.sigs#36 |
|
All checksums match, PR created, thanks @patricklodder and @chromatic for the support! |
|
I have merged @slightlyskepticalpotat's gitian sigs and finalized the release as draft, including notarized macOs binaries. If no objections, I'll push branches and make the binaries public in 2h from now. |
|
No objections here, looks the same as mine.
…On Wed, Feb 28, 2024, 10:55 Old Dip Tracker ***@***.***> wrote:
I have merged @slightlyskepticalpotat
<https://github.com/slightlyskepticalpotat>'s gitian sigs and finalized
the release as draft, including notarized macOs binaries.
Here's the SHA256SUMS.asc:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
b8fb8050b19283d1ab3c261aaca96d84f2a17f93b52fcff9e252f390b0564f31 dogecoin-1.14.7-aarch64-linux-gnu.tar.gz
5606ccf343a403797518072e4af4c693f1b1f826e4fb58ea1b9f3335828c83a6 dogecoin-1.14.7-arm-linux-gnueabihf.tar.gz
4c5c19fc7c561699947a9fd0bce0e037e6da767f6275c6db9eb6e36c2e395a79 dogecoin-1.14.7-i686-pc-linux-gnu.tar.gz
cbdd14693e6e4e81d53c034ef05d806495f00d7946c3c1463a5e1550629cf635 dogecoin-1.14.7-osx-signed.dmg
cdfd75a7757493e386265a0c65614b2c6062d1f5f7177bddcc2eec00bea9480b dogecoin-1.14.7-osx-unsigned.dmg
20439109506a9de9e8208b238c92c38c5f6554378f26a7660313b00d3e77f371 dogecoin-1.14.7-osx-unsigned.tar.gz
815884d43b8d386a70748626471935e83b3d794bfeea74318cdac4cbec2bae0a dogecoin-1.14.7-osx64.tar.gz
1679563488b7145b027a6801b0d3e458a012826b1447295119f94d7c615b5e5c dogecoin-1.14.7-win-unsigned.tar.gz
738e70d06263e20f06304fbbd1b0e1481a7d0da3434b675e4b1e680644c09b8a dogecoin-1.14.7-win32-setup-unsigned.exe
d870d08ea59a6f40b3f2a03048bcdcfc4150896430ffade1bc466925dda93737 dogecoin-1.14.7-win32.zip
e1bc8be88d22af22bb26c2d87cfe497a808fc54817921ced416392a1ed78c0a2 dogecoin-1.14.7-win64-setup-unsigned.exe
8475ba266761e830f2a270c542b5513a3e33892951e8d31318ca3b48cf5465f1 dogecoin-1.14.7-win64.zip
9cd22fb3ebba4d407c2947f4241b9e78c759f29cdf32de8863aea6aeed21cf8b dogecoin-1.14.7-x86_64-linux-gnu.tar.gz
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCAAdFiEE3G70qL+fGx5N4e5SLTo0W5jQ3B8FAmXfVsAACgkQLTo0W5jQ
3B9kLQf/Wlaym2nnmynUqGf9IbdNLK5K0Uj6Ktl0XKDp5rISnM6lSdrjRxyNTYWY
nB5fCXx31x7Sc/60jryUW4ysbxioGlfGmsqiVNs1GGAqBVRZyc0hgKtGMG7MlHf8
omWn7pQcZN5wY5eso86v2IC0n/3OhzRA2LxVr76dUbs4WuNaodxjcQGtJ4XMaLnr
dW9KQxwFKg+taOPnufY+isy9SqGGJWqdQ5R4vX4gKbyFPCghhhPiI0VNBPpQ7HLu
iS+6xPI/8KfjzzbRH9pN8OWFp/1fCylOYkb7sadjZwZPz3pL9PZglNQluzk2KFZG
WDoRSJdEhodqIgnOPqQvhWbo0T/p9Q==
=vEm2
-----END PGP SIGNATURE-----
If no objections, I'll push branches and make the binaries public in 2h
from now.
—
Reply to this email directly, view it on GitHub
<#3407 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHOXLYHTWZJQ2NZBM2HY6L3YV5HOFAVCNFSM6AAAAABDABVLBKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRZGI4DOOJSG4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
DONE! 🥳 |
Congrats! |
and others
I learned today that there are multiple 3rd parties desperately waiting for a release that includes #3299. To facilitate, I'm proposing to start the release pressure cooker now. This means that we would drastically reduce the scope of what is still pending towards 1.14.7, and do a release this month.
Please read this proposal carefully.
Proposed deadlines
Scope
For a full list of in-scope PRs that are currently open, you can filter the pull request view by
milestone:1.14.7Must haves
Low hanging fruit
Would be nice if this can be finished, but let’s not make any of it blocking:
AX_PTHREAD#3414 - fixes autoreconf gives warnings on 1.14.7-dev (with autoconf 2.71) #3072Documentation updates
INSTALL.md: doc: list minimum os versions #3417Pushed forward, with deep regrets
These should get love first thing after release:
Push everything else, because they're not ready
String translation updates
fr&fr_CA: Update and correction of French translation files (bitcoin_fr.ts,bitcoin_fr_CA.ts and bitcoin_fr_FR.ts) #3195zh_CN: add Chinese (zh_CN) translations to 1.14.7, full coverage #3419it: Minor Update of Italian Translation #3428ko_KR: Minor update bitcoin_ko_KR.ts #3430pl: Update of Polish Translation, 1.14.7 #3431nl: Translate dutch (nl) #3435ar: Translate arbic #3439 - postponed due to missing language review.fr_CA: Update to French-Canadian Translations #3441Maintainer tasks for release
contrib/debian/copyright: doc: update debian/copyright #3444COPYING: update in-line copyright years #3447Post-release tasks
The text was updated successfully, but these errors were encountered: