System.Data.SQLite
Check-in [ffc05d03c9]
Not logged in

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Update pre-check-in checklist.
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1: ffc05d03c93d2d44be5dc0461946e68a0da7b752
User & Date: mistachkin 2012-01-28 13:17:02
Context
2012-01-28
13:37
Update downloads page for release 1.0.79.0. check-in: fa528c9c9c user: mistachkin tags: trunk, release
13:17
Update pre-check-in checklist. check-in: ffc05d03c9 user: mistachkin tags: trunk
10:25
VS designer component installer test changes. check-in: 22a23a6461 user: mistachkin tags: trunk
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to www/checkin.wiki.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21




<title>Check-in Checklist</title>

Before every check-in:

  1.   <b>fossil diff</b> &rarr; no stray changes

  2.   <b>fossil extra</b> &rarr; no unmanaged files need to be added.

  3.   The check-in will go onto the desired branch.

  4.   "Autosync" is enabled &rarr;
       <ol>
       <li> The check-in will not cause a unintentional fork.
       <li> The local system clock is set correctly.
       </ol>

Before every check-in to <b>trunk</b>:

  5.   No compiler warnings on the development machine.

  6.   Changes will not cause problems on a future <b>bisect</b>.








|

|



|










>
>
>
>
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
<title>Check-in Checklist</title>

Before every check-in:

  1.   <b>fossil diff</b> &rarr; No stray changes.

  2.   <b>fossil extra</b> &rarr; No unmanaged files need to be added.

  3.   The check-in will go onto the desired branch.

  4.   The &quot;autosync&quot; setting is enabled. &rarr;
       <ol>
       <li> The check-in will not cause a unintentional fork.
       <li> The local system clock is set correctly.
       </ol>

Before every check-in to <b>trunk</b>:

  5.   No compiler warnings on the development machine.

  6.   Changes will not cause problems on a future <b>bisect</b>.

  7.   Build binaries as outlined on the [./build.wiki | build procedures] page.

  8.   Run unit tests as outlined on the [./test.wiki | test procedures] page.