OpenRPG

On Fri, 2003-11-21 at 20:42, Baleno wrote:
> Everyone should check out the features.xml and make sure everything is in
> there and correct.

A suggestion from the peanut gallery:  features.xml is nice, but I find
it awfully hard to read.  Maybe it could reorganized, grouped by "new
features", "bug fixes", etc.  IMO, it's not even worth giving credit to
specific people;  'cvs log' will always reveal that.

Here's an example of a 'changes' file that the Subversion project uses,
just as food for thought.  Scroll down a bit and take a look at how it's
organized... each release is grouped into "user visible" vs. "developer
visible" changes, and for easy absorption, just one line per item:

  http://svn.collab.net/repos/svn/trunk/CHANGES

So I guess the fog fix is the last thing left now that the tabs are working.

Also, Ben, I agree with you about not needing to give credit for specific 
features.  It's realy not nessasary.  I also agree that the format would be 
better broken up into features and bug fixes, etc. like you said.  The only 
thing that I didn't like about your changelog is that it had previous 
changes.  While a think a developer change log would need this I think the 
features.xml file is mostly ment for stuff thats changed since last release.  
I propose we keep a developer log like your example and insert the 
features.xml stuff into it every release.


Tom

> On Fri, 2003-11-21 at 20:42, Baleno wrote:
> > Everyone should check out the features.xml and make sure everything is in
> > there and correct.
> 
> A suggestion from the peanut gallery:  features.xml is nice, but I find
> it awfully hard to read.  Maybe it could reorganized, grouped by "new
> features", "bug fixes", etc.  IMO, it's not even worth giving credit to
> specific people;  'cvs log' will always reveal that.
> 
> Here's an example of a 'changes' file that the Subversion project uses,
> just as food for thought.  Scroll down a bit and take a look at how it's
> organized... each release is grouped into "user visible" vs. "developer
> visible" changes, and for easy absorption, just one line per item:
> 
>   http://svn.collab.net/repos/svn/trunk/CHANGES
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: SF.net Giveback Program.
> Does SourceForge.net help you be more productive?  Does it
> help you create better code?  SHARE THE LOVE, and help us help
> YOU!  Click Here: http://sourceforge.net/donate/
> _______________________________________________
> Openrpg-dev mailing list
> Openrpg-dev@...
> https://lists.sourceforge.net/lists/listinfo/openrpg-dev

Baleno wrote:

>So I guess the fog fix is the last thing left now that the tabs are working.
>  
>
Unless you want me to work up an image fix, I second that. And really, 
the fog is so bothersome I'd say release without the fix if it takes too 
long.

I just tested out the cvs copy (1.6.0rc1?) on Fedora Core 1 (
python-2.2.3-7, wxPythonGTK-py2.2-2.4.0.2-2 ). 

Fog layer seems fine, all my nodes work, mini's seem fine. Only thing I
noticed offhand was Whiteboard->Polyline w/Live refresh make the map
area flicker (refreshing so fast) as to be nearly useless. But this
issue was in 1.5.2 also so...

I think it looks good. If I have sometime later today I'll still my sons
laptop (Windows 98) and look at both together.

Mike

On Mon, 2003-11-24 at 23:11, mDuo13 wrote:
> Baleno wrote:
> 
> >So I guess the fog fix is the last thing left now that the tabs are working.
> >  
> >
> Unless you want me to work up an image fix, I second that. And really, 
> the fog is so bothersome I'd say release without the fix if it takes too 
> long.
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: SF.net Giveback Program.
> Does SourceForge.net help you be more productive?  Does it
> help you create better code?  SHARE THE LOVE, and help us help
> YOU!  Click Here: http://sourceforge.net/donate/
> _______________________________________________
> Openrpg-dev mailing list
> Openrpg-dev@...
> https://lists.sourceforge.net/lists/listinfo/openrpg-dev

Just tested 1.6.0rc1 on Windows 98 (Python 2.3 Wxpython 2.4 for
python2.3) everything looks fine.

I then started a server up on the Fedora Core box and connect both
clients and messed around with them. The fog layer issues are fixed. The
Whiteboard->Polyfine->live refresh is much better under Windows (no idea
if that the python wxpython versions or what).

All nodes that I have work and chat seems fine. The new settings to turn
off features in the chat toolbar is very nice.

I give it a thumbs up!

Mike


On Tue, 2003-11-25 at 09:03, Mike Tremaine wrote:
> I just tested out the cvs copy (1.6.0rc1?) on Fedora Core 1 (
> python-2.2.3-7, wxPythonGTK-py2.2-2.4.0.2-2 ). 
> 
> Fog layer seems fine, all my nodes work, mini's seem fine. Only thing I
> noticed offhand was Whiteboard->Polyline w/Live refresh make the map
> area flicker (refreshing so fast) as to be nearly useless. But this
> issue was in 1.5.2 also so...
> 
> I think it looks good. If I have sometime later today I'll still my sons
> laptop (Windows 98) and look at both together.
> 
> Mike
> 
> On Mon, 2003-11-24 at 23:11, mDuo13 wrote:
> > Baleno wrote:
> > 
> > >So I guess the fog fix is the last thing left now that the tabs are working.
> > >  
> > >
> > Unless you want me to work up an image fix, I second that. And really, 
> > the fog is so bothersome I'd say release without the fix if it takes too 
> > long.
> > 
> > 
> > 
> > 
> > -------------------------------------------------------
> > This SF.net email is sponsored by: SF.net Giveback Program.
> > Does SourceForge.net help you be more productive?  Does it
> > help you create better code?  SHARE THE LOVE, and help us help
> > YOU!  Click Here: http://sourceforge.net/donate/
> > _______________________________________________
> > Openrpg-dev mailing list
> > Openrpg-dev@...
> > https://lists.sourceforge.net/lists/listinfo/openrpg-dev
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: SF.net Giveback Program.
> Does SourceForge.net help you be more productive?  Does it
> help you create better code?  SHARE THE LOVE, and help us help
> YOU!  Click Here: http://sourceforge.net/donate/
> _______________________________________________
> Openrpg-dev mailing list
> Openrpg-dev@...
> https://lists.sourceforge.net/lists/listinfo/openrpg-dev

Unless someone has objections I guess it is release time.  So no more commits
(even bugfixes) until it's out.

Chris, do you want the honors (i.e. do you have time) or should I give it a go
(boy that would scare me).

On Tue, 2003-11-25 at 21:02, Baleno wrote:
> Unless someone has objections I guess it is release time.  So no more commits
> (even bugfixes) until it's out.
> 
> Chris, do you want the honors (i.e. do you have time) or should I give it a go
> (boy that would scare me).

Only the windows installer seems scary the rest should be cake.

I think these are the steps. 

1) Bump the release number in orpg_version.py commit that to cvs.
2) Run that packorpg.sh script I wrote to produce the .tar.gz .zip and
patch.zip versions. 
3) [Scary part] use whatever Windows packing software you got to packup
the .exe version.  (Save off the script and instructions for next time.)
4) Push all 4 versions up to sourceforge.
5) Edit the orpg_packages.xml file on http://www.openrpg.com to point at
the 1.6.1 release (patch.zip) file.
6) Tell the world. :)


An optional step is to tag the cvs branch of 1.6.1 but I noticed that
1.5.1 didn't get tagged.

Fun fun fun!

Mike

The installer is easy.

> I think these are the steps. 
> 
> 1) Bump the release number in orpg_version.py commit that to cvs.

Should be done (not sure though)

> 2) Run that packorpg.sh script I wrote to produce the .tar.gz .zip and
> patch.zip versions. 

Your script should not include the files in the images directory unless its a 
new file (these files don't usualy change).  This saves space and helps out 
people on dial up to get a quick update.

> 3) [Scary part] use whatever Windows packing software you got to packup
> the .exe version.  (Save off the script and instructions for next time.)

not a problem

> 4) Push all 4 versions up to sourceforge.

Again easy.

> 5) Edit the orpg_packages.xml file on http://www.openrpg.com to point at
> the 1.6.1 release (patch.zip) file.

should be already done

> 6) Tell the world. :)

easies of all tasks since you just have to tell one person and the whole user 
base updates in a matter of days ;) (well, those that aren't pig headed and 
still want to run 0.9.8 ;) )

> 
> An optional step is to tag the cvs branch of 1.6.1 but I noticed that
> 1.5.1 didn't get tagged.

We should definatly should be done.

> > 2) Run that packorpg.sh script I wrote to produce the .tar.gz .zip and
> > patch.zip versions. 
> 
> Your script should not include the files in the images directory unless its a 
> new file (these files don't usualy change).  This saves space and helps out 
> people on dial up to get a quick update.

That's tricky since it is possible to upgrade from any version to the
current release. So you'd have to either include any images that has
changed since x.x.x. Or exclude images by default and have a another
patch file with just the images. The update code can be expanded to
handle more then 1 type of update. For instance you could add a /update
images or something like that. I don't my first reaction was hell I can
just add -x \*images\* to the patch.zip line and the image directory
would be excluded, then I could either ask the user for a list of images
to include and run another zip instance with -g -i <image/file> for each
or....Getting really tricky I could call cvs to see what is new or
changed in the images directory. (But at that point I think I would
rather do this in perl or python :) ) 

I'll see if I can come up with something. Otherwise the -x \*images*\
and and dialog to add image files seems most likely.

Mike

Ok for what it is worth ;), I add this change new file is at

 http://www.stellarcore.net/downloads/packorpg.sh

Now it excludes the images dir in the patch.zip and then it asks you if
you want to add any images to the patch.zip and you can type in a
filename and it will get added. This is a loop so you can do this all
day. Sort of ugly if you have a major update of images but great for 1
or 2. Guess I could add a switch to include exclude images and trigger
this loop... Oh well its really just so you don;t have to remember how
to invoke tar and zip everytime you need to make a release.

Mike

On Wed, 2003-11-26 at 08:53, Mike Tremaine wrote:
> > > 2) Run that packorpg.sh script I wrote to produce the .tar.gz .zip and
> > > patch.zip versions. 
> > 
> > Your script should not include the files in the images directory unless its a 
> > new file (these files don't usualy change).  This saves space and helps out 
> > people on dial up to get a quick update.
> 
> That's tricky since it is possible to upgrade from any version to the
> current release. So you'd have to either include any images that has
> changed since x.x.x. Or exclude images by default and have a another
> patch file with just the images. The update code can be expanded to
> handle more then 1 type of update. For instance you could add a /update
> images or something like that. I don't my first reaction was hell I can
> just add -x \*images\* to the patch.zip line and the image directory
> would be excluded, then I could either ask the user for a list of images
> to include and run another zip instance with -g -i <image/file> for each
> or....Getting really tricky I could call cvs to see what is new or
> changed in the images directory. (But at that point I think I would
> rather do this in perl or python :) ) 
> 
> I'll see if I can come up with something. Otherwise the -x \*images*\
> and and dialog to add image files seems most likely.
> 
> Mike
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: SF.net Giveback Program.
> Does SourceForge.net help you be more productive?  Does it
> help you create better code?  SHARE THE LOVE, and help us help
> YOU!  Click Here: http://sourceforge.net/donate/
> _______________________________________________
> Openrpg-dev mailing list
> Openrpg-dev@...
> https://lists.sourceforge.net/lists/listinfo/openrpg-dev

Baleno wrote:

>Unless someone has objections I guess it is release time.  So no more commits
>(even bugfixes) until it's out.
>  
>
Wonderful. No objections -- I'm glad it's finally coming out. I'll be 
sure to make a plugin patch ASAP, too. ;)

Great!  When you get the item done below I will update rthe website and post news everywhere.  
I'm pretty good at PR now. ;)

-chris

> I think these are the steps. 
> 
> 1) Bump the release number in orpg_version.py commit that to cvs.
> 2) Run that packorpg.sh script I wrote to produce the .tar.gz .zip and
> patch.zip versions. 
> 3) [Scary part] use whatever Windows packing software you got to packup
> the .exe version.  (Save off the script and instructions for next time.)
> 4) Push all 4 versions up to sourceforge.
> 5) Edit the orpg_packages.xml file on http://www.openrpg.com to point at
> the 1.6.1 release (patch.zip) file.
> 6) Tell the world. :)
> 
> 
> An optional step is to tag the cvs branch of 1.6.1 but I noticed that
> 1.5.1 didn't get tagged.
> 
> Fun fun fun!
> 
> Mike
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: SF.net Giveback Program.
> Does SourceForge.net help you be more productive?  Does it
> help you create better code?  SHARE THE LOVE, and help us help
> YOU!  Click Here: http://sourceforge.net/donate/
> _______________________________________________
> Openrpg-dev mailing list
> Openrpg-dev@...
> https://lists.sourceforge.net/lists/listinfo/openrpg-dev
> 
>

> Great!  When you get the item done below I will update rthe website and post
news everywhere.  
> I'm pretty good at PR now. ;)

You have to be other wise its washing car windows with your spit and sleeping
in cardboard boxes ;)

Tom

> 
> -chris
> 
> > I think these are the steps. 
> > 
> > 1) Bump the release number in orpg_version.py commit that to cvs.
> > 2) Run that packorpg.sh script I wrote to produce the .tar.gz .zip and
> > patch.zip versions. 
> > 3) [Scary part] use whatever Windows packing software you got to packup
> > the .exe version.  (Save off the script and instructions for next time.)
> > 4) Push all 4 versions up to sourceforge.
> > 5) Edit the orpg_packages.xml file on http://www.openrpg.com to point at
> > the 1.6.1 release (patch.zip) file.
> > 6) Tell the world. :)
> > 
> > 
> > An optional step is to tag the cvs branch of 1.6.1 but I noticed that
> > 1.5.1 didn't get tagged.
> > 
> > Fun fun fun!
> > 
> > Mike
> > 
> > 
> > 
> > 
> > -------------------------------------------------------
> > This SF.net email is sponsored by: SF.net Giveback Program.
> > Does SourceForge.net help you be more productive?  Does it
> > help you create better code?  SHARE THE LOVE, and help us help
> > YOU!  Click Here: http://sourceforge.net/donate/
> > _______________________________________________
> > Openrpg-dev mailing list
> > Openrpg-dev@...
> > https://lists.sourceforge.net/lists/listinfo/openrpg-dev
> > 
> > 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: SF.net Giveback Program.
> Does SourceForge.net help you be more productive?  Does it
> help you create better code?  SHARE THE LOVE, and help us help
> YOU!  Click Here: http://sourceforge.net/donate/
> _______________________________________________
> Openrpg-dev mailing list
> Openrpg-dev@...
> https://lists.sourceforge.net/lists/listinfo/openrpg-dev