[PROPOSAL] Jetspeed change tracking

[Mark Orciuch <mo...@apache.org>]

I don't know about you but I'm getting tired of keeping the changes.xml
up-to-date with every little change I make (and then having to update the
Jakarta site which I often forget). Wouldn't it be more efficient if we
logged all changes in Bugzilla under appropriate Version and then just refer
to a Bugzilla query from changes.html. We could have a separate
Version-based query for each release, for example:

http://issues.apache.org/bugzilla/buglist.cgi?version=1.4b2
http://issues.apache.org/bugzilla/buglist.cgi?version=1.4b4-dev%20/CVS

I think that this method would be more accurate in keeping track of changes.
Let me know what you think.

Best regards,

Mark Orciuch - morciuch@apache.org
Jakarta Jetspeed - Enterprise Portal in Java
http://jakarta.apache.org/jetspeed/


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

RE: [PROPOSAL] Jetspeed change tracking

[Mark Orciuch <ma...@ngsltd.com>]

>
> It does make sense to use a change control system to automate the
> process.
> Turbine is now doing all change control using Scarab.
> I was looking at Maven, and it seems to be capable of generating a
> change log, but Im not sure how it works.
>
> Example:
> http://jakarta.apache.org/turbine/torque/changelog.html
>
> But there is nothing there. The torque and turbine projects don't seem
> to be making use of the change log feature yet.
>
> While we are discussing this, we should probably discuss switching over
> to Scarab.

I thought of Scarab but I didn't want to introduce such big task yet.

> One problem is how to convert the Bugzilla db to Scarab, if its even
> possible.

I'm not sure where Scarab stands in regards to Bugzilla import - we went
directly to Scarab. I think that this feature is in the works. One thing
that Scarab lacks is cross-issue-type reporting. We had to write a custom
portlet to be able to view all issue types on single report. I have not
looked into Maven to see if they have a plugin for that.

>
> I am -0 on this pending more research....
>

I understand perfectly.

Best regards,

Mark Orciuch - morciuch@apache.org
Jakarta Jetspeed - Enterprise Portal in Java
http://jakarta.apache.org/jetspeed/


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: [PROPOSAL] Jetspeed change tracking

[David Sean Taylor <da...@bluesunrise.com>]

On Monday, January 6, 2003, at 09:34  AM, Mark Orciuch wrote:

> I don't know about you but I'm getting tired of keeping the changes.xml
> up-to-date with every little change I make (and then having to update 
> the
> Jakarta site which I often forget). Wouldn't it be more efficient if we
> logged all changes in Bugzilla under appropriate Version and then just 
> refer
> to a Bugzilla query from changes.html. We could have a separate
> Version-based query for each release, for example:
>
> http://issues.apache.org/bugzilla/buglist.cgi?version=1.4b2
> http://issues.apache.org/bugzilla/buglist.cgi?version=1.4b4-dev%20/CVS
>
> I think that this method would be more accurate in keeping track of 
> changes.
> Let me know what you think.
>

It does make sense to use a change control system to automate the 
process.
Turbine is now doing all change control using Scarab.
I was looking at Maven, and it seems to be capable of generating a 
change log, but Im not sure how it works.

Example:
http://jakarta.apache.org/turbine/torque/changelog.html

But there is nothing there. The torque and turbine projects don't seem 
to be making use of the change log feature yet.

While we are discussing this, we should probably discuss switching over 
to Scarab.
One problem is how to convert the Bugzilla db to Scarab, if its even 
possible.

I am -0 on this pending more research....

--
David Sean Taylor
Bluesunrise Software
david@bluesunrise.com
+01 707 773-4646




--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>