Re: [WWdevel] WeBWorK 2.2 prerelease, code freeze in a branch?

[Davide P. C. <dp...@un...>]

> I think this release should be 2.2. It has a few major non-bug-fix  
> features, like gateway testing (including database changes), the  
> removal of deprecated database layouts, and jsMath updates  
> (including the new fonts tarball).

That sounds good.

> However, in my opinion, we're not ready for a "final" 2.2 release,  
> since many changes went in after fall semester ended, and therefore  
> haven't received much testing.

I also agree.  Out faculty had some serious problems with the PG  
Editor when they started using it this week, and there are a number  
of problems with it.  I'll try to write something up soon.  I don't  
usually use the PG editor myself, but when I did, I really found it  
difficult and confusing.  I think I have a version that works the way  
I expect it to, but was planning to use it a bit longer before making  
suggested changes.

> I'd also like to tweak the way we track releases in CVS for this  
> series.

I'm happy to do whatever you ask, and I appreciate the examples, as I  
don't know CVS well enough to be sure I'm doing it properly.

Davide