Re: [Webwork-devel] Branch or Commit , which?

[Mike Cannon-B. <mi...@at...>]

On 5/2/02 12:24 AM, "Victor Salaman" (vsa...@ho...) penned the
words:

> Hi Rickard and fellow webworkers:
> 
> I have a ton of things I would like to commit but have been reluctant to do
> so since I don't want to add new features before 1.0 as this release has to
> be extremely stable and throughly tested. And although the stuff I'll be
> committing has been used in production as of a month ago with no problems
> whatsoever, I'd like it to be tested by the community before it goes
> mainstream.
> 
> Now my question is:
> 
> 1. Should we make some kind of "sandbox" inside webwork cvs? (for this and
> future additions)
> 2. Should we create another module in cvs (for tools relating to webwork).
> 3. Should I just commit and get it over with (least desired option)?
> 
> What are your opinions?

I vote #2.

Has any thought been given to splitting up WW slightly post 1.0, with the
parts that relate to other technologies made into separate modules (ie
Velocity integration, formproc).

It's quite possible this would enable:
- modules to have separate release schedules to WW core (which is very slow
are releasing - but it's OSS so we can't complain ;))
- the core to be simplified (hopefully?) and dependencies removed

Thoughts?

-mike