In basis branch, by another side, when it is hot, warm or warming, i.e, not near or in the release or pre-release, or after release, but attention, only in basis branch, because stage is always cool, cooler or coolest, so retaking:
In hot or warm basis branch you are free to commit very freely, like a brainstorming or drafting.
But some cares are good:
Try to always keep all core and main repositories buildable in a atomic commit. It may be not true, if you are consolidating changes from many machines, or is switching from machines with incomplete and hard or large refactoring using the repository as store. The most important, remember, is to store. If it is not buildable by some time, ok.
Try always to keep in mind ca2 code conventions , philosophies as self-healing for example and best practices. This is may be more important than just storing. It is so good to store! But to store, matterialize good practices, is much better, because they create hard good things.
And put nice commit comments. It is not automatic yet, but try to keep the date - now, it is already inserted automaticatilly by subversion - the machine from where compiling/building/developing and machine context and environment description maybe citing remote access path to the compiling/building/development machine - and if you are fond of, very very free dedicatories or graphisms as your watermark.
Try to use always yours or appropriate user when commiting. In the near future, is likeable to work with syllomatter app, that also will keep information like ip address of committing machine and automating boring parts of this commit process.