You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Documentation/Development/ReleaseProcess.md
+7-3
Original file line number
Diff line number
Diff line change
@@ -18,12 +18,14 @@ Well, useful is probably the wrong word. More like entertaining. Here we go.
18
18
19
19
* Make sure all issues in the milestone are closed - click Issues, Milestones, and it'll show the percent complete. If there's any issues you want to bump to the next round, add the next round's milestone and tag the issues with it.
20
20
* When enough PRs are in dev, do a round of code testing in 2008-2016 in the cloud lab.
21
-
* Copy all newly synced scripts to each VM and install in master
21
+
* Merge scripts into two files:
22
+
* copy /b /y sp_Blitz*.sql Install_Core_Blitz.sql
23
+
* copy /b /y *.sql Install-All-Procs.sql
24
+
* The easiest way to get a command prompt to the folder location is to navigate there with Windows Explorer and then type 'cmd' in the address bar.
25
+
* These get moved to AWS for testing
22
26
* Run _TestBed.sql: this has stored proc calls with common parameters. May have to add in new scenarios if new features are added.
23
27
* If it passes, bump all the version numbers inside the scripts.
24
28
* sp_foreachdb (no version number yet)
25
-
* sp_BlitzTrace (no version number yet)
26
-
* sp-BlitzRS (no version number yet)
27
29
* sp_BlitzWho @Version and @VersionDate
28
30
* sp_BlitzIndex @Version and @VersionDate
29
31
* sp_BlitzFirst @VersionDate (no version)
@@ -32,6 +34,8 @@ Well, useful is probably the wrong word. More like entertaining. Here we go.
0 commit comments