![]() |
devNote
d161101 |
0.0.0 2017-12-26 -13:17 -0800 |
Status |
Date |
Description |
|
2017-02-23 | d161101: Emphasize the use as a component and less the free-standing use, although that is still supported. | ||
2017-02-22 | d161101: Provide attribution | ||
2017-02-22 | d161101: Provide links to all of the specialized mentions in the Synopsis and the 5Ps. These could be via the "Available Materials" | ||
2016-11-23 | Provide links, when available, on toolcraft for verifying sha256 digests and openPGP signatures [dh:2016-11-25 This can now be done at the default page of d161101c-dist] | ||
2016-11-22 | Emphasize requiring only freely-available tools in VCbind.txt here as well as overall concerning Toolcraft. | ||
2016-11-22 | Add further detail about how Toolcraft, TROST, and the ability for anyone to confirm functioning of VCbind, with prerequisite preparation. | ||
2016-11-22 | The Visual Studio 2017 Release candidates do not set a common toolset environment variable. Figure out how to work without that when the full release occurs. This is the occasion for 0.2.0 and having the sample build.. [dh:2017-02-22 This is going to be later. 0.2.0 should be short of VS 2017 and also need not have all the confirmation arrangements.][dh:2017-12-26 I now know how to locate VS2017 vcvars code. It is a tricky case because there is no environment setting to use but a fixed location provides shortcuts that can be used.] | ||
2016-11-22 | Link to reference on creating and using batch scripts somewhere. There is now (Windows 10) extensive help files built in, along with more on MSDN. There is also the Command Line Administrator's Pocket Handbook. [dh:2016-11-25 I think I started that somewhere. Find it.] | ||
2016-11-22 | Verify the VCbind structure with VS2005 (080) and all subsequent VS Express and Community installs. [dh:2016-11-25 That is a good way to work the checklist.][dh:2017-12-26 Freeze 0.2.0 without VS2017, then work on getting VS 2017 working for 0.3.0.] | ||
2016-11-22 | Provide a checklist of the testing cases that apply to VCbind.bat. The full testing is needed for a release candidate and also the level of testing needs to be accounted for in a pull request. | ||
2016-11-22 | Find out what config cases never work on older toolset versions, and rule them out at the VCbind.bat level. | ||
2016-11-22 | The term for cmd.exe is "command shell." Use consistently. See <https://technet.microsoft.com/en-us/library/bb490954.aspx>. | ||
2016-11-22 | Provide/Point to "help cmd" and also point out that extensive help on the command shell is avalable off-line | ||
2016-11-22 | Beyond 0.1.0, confirm VCbind.bat, Powershell, MSYS2, CygWin and other Unix-style shells. TC also. [dh:2016-12-03 The hack for unwinding case-sensitive use of the Environment will be difficult to address.] | ||
2016-11-22 | Include a tip about making handy shortcuts for testing, either as part of toolcraft or here. There needs to be guidance or a hint about that in VCbind.txt? | ||
2016-11-22 | Testing and confirmation of VCbind.zip should be included in VCbind.zip, along with smoketest procedures and sample compilation. The first smoketest is to simply run cl.exe with no parameters. The second is to compile and then run a sample. | ||
done | 2017-12-26 | d161101d/d161101d-dist Set these up as placeholders because working GitHub materials already identify 0.2.0. | |
done 2017-02-22 |
2016-11-22 | It must be emphasized that VCbind.bat can be exercised without changing the current working directory, and it will not change that. | |
done 2017-02-22 |
2016-12-03 | d161101: Add the 5Ps for VCbind and the Design Point for VCbind | |
done 2016-12-03 |
2016-11-28 | d161101: I don't like the "VCbind: VC++ Console Build Setup" title. Need to rethink some of this. [dh:2016-12-02 I am thinking that VC++ Command-Line Setup might be better, even though longer. Use narrative on d161101 to see how close this gets.][2016-12-03 Changed to VC++ Command-Line Setup despite the ambiguity. | |
done 2016-12-02 |
2016-11-29 | d161101d-dist/default.htm: Correct the 0.0.0 date | |
done | 2016-12-02 | d161101d-dist: Change to VCbind 0.1.1 placeholder | |
done | 2016-12-02 | d161101d: Change to VCbind 0.1.1 placeholder | |
done 2016-12-02 |
2016-11-29 | Add Cluster rmaps to d161101d and d161101d-dist folders. | |
done 2016-12-02 |
2016-11-29 | d161101d: Make revision-progression URLs monospace | |
done 2016-12-02 |
2016-11-29 | d161101c: Make VCbind 0.1.0 version link monospace | |
done | 2016-11-29 | d161101/c/c-dist: Put ClustrMap on these pages | |
done | 2016-11-29 | d161101d: Create provisional page pending 0.1.0-next distribution being achieved | |
done 2016-11-29 |
2016-11-28 | d161101c: Adjust font use in links of the version progression block | |
done 2016-11-29 |
2016-11-28 | d161101: Add downloads (-dist folders) here too. | |
done | 2016-11-29 | d161101d-dist: Create placeholder subfolder with Construction Structure and Default page | |
done | 2016-11-27 | d161101c-dist: Adjust fonts and sizes for consistent appearance. Have text/plane MIME types for .asc and .sha256 | |
done 2016-11-25 |
2016-11-23 | Adapt the ODMdev revision block structure for the downloads. [dh:2016-11-25 Can link to d161101c-dist and can also link to the .txt manifest file.] | |
done | 2016-11-25 | d161101c: Correct links and other material that is hungover from the toolcraft page used as boilerplate. | |
done 2016-11-25 |
2016-11-22 | d161101c: Prepare to offer VCbind 0.1.0 as the initial stable alpha for VCbind. | |
done | 2016-11-25 | d161101c-dist: Needs a revision progression block too, even though it also links upward. | |
done | 2016-11-25 | d161101c-dist: Provide a default.htm that includes all of the download information and what the files are. | |
done 2016-11-24 |
2016-11-23 | The Zips stay shallow. VCbind.zip is intended to work that way. The source zip is versioned, so it works all right in any case. | |
done 2016-11-24 |
2016-11-23 | Provide sha256 hashes for the files as well. There is no great reason to use md5 or sha1, even though they are probably perfectly safe to use. We use sha256 as a practice simply for social reassurance. | |
done 2016-11-24 |
2016-11-23 | We can also have a VCbind-x.y.z-src.zip and its external signature. This gets interesting. This means we need the necessary files at the VCbind level. | |
done 2016-11-24 |
2016-11-23 | Clearsign the VCbind.txt files. | |
done 2016-11-24 |
2016-11-23 | Use a subfolder for each release entry so that the downloads avoid name collisions. This is primarily needed for the VCbind.zip and VCbind.zip.asc files. | |
done 2016-11-24 |
2016-11-22 | Provide a digital signature for the VCbind.zip download(s). | |
done | 2016-11-23 | d161101c-dist: Add folder for the archived distributions of the 0.1.0 release. | |
done | 2016-11-22 | Bring to here the TODOs and other text from the Adv10/dev/VCbinder/devBind soure code, simplifying the items in the source code.. | |
done | 2016-11-22 | d161101c: Introduce a version-progression block for this material. Oops. There is one already. | |
done | 2016-11-12 | Customize d161101, d161101b, d161101c as initial placeholders | |
done 0.0.0 | 2016-11-12 |
|
|
done | 2016-11-12 |
Create this page for immediate collection of action items and notes. |
![]() |
created 2016-11-12-17:51 -0800 by
orcmid |