Masterview devel - Jun 2006 - I have uploaded latest docs to masterview.org

I updated the docs some and have uploaded the latest docs to masterview.org,
did you say you had created a toolbar for the pages? It wasn''t in the
one in
svn.

If you could do one last check of your svn,  then if you give me the ok
we''ll do a release and send out an announcement.

Thanks for all your hard work!! The docs you reworked look great!!

Jeff
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://rubyforge.org/pipermail/masterview-devel/attachments/20060621/fbc7d268/attachment.html

Yep, lost some of the changes I put in late yesterday morning in the doc
files.  I''ll recheck all the changes I put in yesterday morning (doc
files
and some changes in release notes,change log...)
 
Upgrading and reinstalling my firewall seems to have solved the baffling
problems I''ve been having since last week with file edits not resulting
in
updated mtimes.  grrrr....
 
One more thought about the release message: we should include a short note
on upgrading from prev. release of MV, existing users *must* redo their
config setups if customized and need to review where their template files
live.  
 
We need to have a stable url that we can point to where the latest
release''s
release note are posted so users always have a reliable place to go to get a
preview of changes and upgrade notes before picking up new build.  Drive me
nuts when packages don''t provide this info (well geez... what happened
and
do I need to know anything important before I install newer version??)
 
~ Deb

  _____  

From: Jeff Barczewski [mailto:jeff.barczewski at gmail.com] 
Sent: Wednesday, June 21, 2006 7:30 AM
To: dlewis at glaivestone.com; masterview-devel at rubyforge.org
Subject: I have uploaded latest docs to masterview.org


I updated the docs some and have uploaded the latest docs to masterview.org,
did you say you had created a toolbar for the pages? It wasn''t in the
one in
svn.

If you could do one last check of your svn,  then if you give me the ok
we''ll do a release and send out an announcement. 

Thanks for all your hard work!! The docs you reworked look great!!

Jeff

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://rubyforge.org/pipermail/masterview-devel/attachments/20060621/ffeca10c/attachment.html

On 6/21/06, Deb Lewis <dlewis at glaivestone.com>
wrote:
>
>  Yep, lost some of the changes I put in late yesterday morning in the doc
> files.  I''ll recheck all the changes I put in yesterday morning
(doc files
> and some changes in release notes,change log...)
>
Sounds great, just let me know when things are ready and we can do the
release then.


Upgrading and reinstalling my firewall seems to have solved the
baffling
> problems I''ve been having since last week with file edits not
resulting in
> updated mtimes.  grrrr....
>
> One more thought about the release message: we should include a short note
> on upgrading from prev. release of MV, existing users *must* redo their
> config setups if customized and need to review where their template files
> live.
>
Yes, I will add something about that.


We need to have a stable url that we can point to where the latest
release''s
> release note are posted so users always have a reliable place to go to get
a
> preview of changes and upgrade notes before picking up new build.  Drive me
> nuts when packages don''t provide this info (well geez... what
happened and
> do I need to know anything important before I install newer version??)
>
Agreed. Our change_log will be a living document, but it probably
doesn''t
have the details needed for what you described.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://rubyforge.org/pipermail/masterview-devel/attachments/20060621/49a3408e/attachment.html