RC1 Release Preparation
See original GitHub issue- Migration Package: Copy mappings into github for source / nice completeness
- Migration Package - Update version
- Migration package - Check that warnings for installing nugets show correct version
- Migration package - Check that all assemblies added to .props
- Create new FWLink for ProjectLink
- Add Cake logic to check all
<attr>
nodes withinterface
in thepath
attribute do not havename="visibility"
attributes (or throw error) - Fix Material version (the artifact is 1.0.0 yet the nuget is 1.1.0x) NOT ONLY Material
- Bump to -rc1 nuget version
- Add cake logic to check that the artifact version matches the nuget version prefix
Issue Analytics
- State:
- Created 4 years ago
- Comments:9 (8 by maintainers)
Top Results From Across the Web
WordPress 6.1 Release Candidate 1 (RC1) Now Available
The first release candidate (RC1) for WordPress 6.1 is now available! This is an important milestone in the 6.1 release cycle.
Read more >Prepare 11.0 RC1 release (!19321) · Merge requests
Prepare 11.0 RC1 release · This can be done by checking out 11-0-stable-prepare-rc1 locally and using git cherry-pick -m1 MERGE_COMMIT_SHA · Remove the...
Read more >Locking the 3.12 branch in preparation of rc1 - Committers
I'm locking the 3.12 branch (for everyone but RMs/admins) in preparation for the rc1 release. It'll remained locked until the final 3.12.0 ...
Read more >Definition of release candidate | PCMag
A pre-release version of software. Sometimes software vendors make one or two release candidates (RC1, RC2, etc.) available to select customers in advance ......
Read more >Preparations for a Release - Apache Commons
This document assumes that the release is being prepared on a linux/unix system, and that steps are being executed from the command-line.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I think they are onto us! 😃
We were doing a fair bit more testing and found a few bugs that needed fixing, several improvements to the build process as well as the actual APIs. Overall, things are betting in the migration, performance and the bindings.
As for the RC release, I believe it is going out the door today…
READY TO RUMBLE