Re: Documentation work this week

2001-07-18 Thread Jean-Marc Lasgouttes
Mike == Mike Ressler [EMAIL PROTECTED] writes: Mike After I finish proofing the Mike current docs, I plan to declare them set in stone for any Mike possible 1.1.6fix3. When is that scheduled to happen? JMarc

Re: Documentation work this week

2001-07-18 Thread Jean-Marc Lasgouttes
Mike == Mike Ressler [EMAIL PROTECTED] writes: Mike For the devvies who may be lurking here - is the 1.2.0 CVS Mike stable enough to use to start documenting 1.2.0 specific Mike features? Or am I better off waiting a bit until Lars declares a Mike true code freeze? Some things are bound to

Re: Documentation work this week

2001-07-18 Thread Mike Ressler
On 18 Jul 2001, Jean-Marc Lasgouttes wrote: Mike == Mike Ressler [EMAIL PROTECTED] writes: Mike After I finish proofing the Mike current docs, I plan to declare them set in stone for any Mike possible 1.1.6fix3. When is that scheduled to happen? If I can get them off my laptop, I have

Re: Documentation work this week

2001-07-18 Thread Jean-Marc Lasgouttes
> "Mike" == Mike Ressler <[EMAIL PROTECTED]> writes: Mike> After I finish proofing the Mike> current docs, I plan to declare them set in stone for any Mike> possible 1.1.6fix3. When is that scheduled to happen? JMarc

Re: Documentation work this week

2001-07-18 Thread Jean-Marc Lasgouttes
> "Mike" == Mike Ressler <[EMAIL PROTECTED]> writes: Mike> For the devvies who may be lurking here - is the 1.2.0 CVS Mike> stable enough to use to start documenting 1.2.0 specific Mike> features? Or am I better off waiting a bit until Lars declares a Mike> true code freeze? Some things

Re: Documentation work this week

2001-07-18 Thread Mike Ressler
On 18 Jul 2001, Jean-Marc Lasgouttes wrote: > > "Mike" == Mike Ressler <[EMAIL PROTECTED]> writes: > Mike> After I finish proofing the > Mike> current docs, I plan to declare them set in stone for any > Mike> possible 1.1.6fix3. > > When is that scheduled to happen? If I can get them off my