Jeff Jensen a écrit :
I like the changes page as a "simplified, user-friendly" list of notable changes
made for each release. The defect/RFE tracking system has the details for the
initiated users when desired.
Quoting Stephane Nicoll <[EMAIL PROTECTED]>:
On 12/27/06, Jason van Zyl <[EMAI
On 27/12/06, Mike Perham <[EMAIL PROTECTED]> wrote:
changes.xml is also very useful where module:JIRA project is not 1:1.
We have jira projects for each subsystem, not module.
It's also handy when you're not using JIRA ;) See MCHANGES-58 [1] and
MCHANGES-59 [2].
I'd have no probs moving the c
changes.xml is also very useful where module:JIRA project is not 1:1.
We have jira projects for each subsystem, not module.
On 12/27/06, Jeff Jensen <[EMAIL PROTECTED]> wrote:
I like the changes page as a "simplified, user-friendly" list of notable changes
made for each release. The defect/RFE
I like the changes page as a "simplified, user-friendly" list of notable changes
made for each release. The defect/RFE tracking system has the details for the
initiated users when desired.
Quoting Stephane Nicoll <[EMAIL PROTECTED]>:
> On 12/27/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
> >
>
On 12/27/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
I never really understood the changes.xml myself, as I don't want to
keep things in an issue tracking system and changes.xml or is this
for folks who don't employ an issue tracking system?
Yes and no. I've always seen it as a "technical" ch
Jason van Zyl wrote:
On 27 Dec 06, at 7:17 AM 27 Dec 06, Dennis Lundberg wrote:
Hi
I've been trying to get the changes plugin into a releasable state.
But it has been going on for too long, I did however manage to get a
2.0-beta-2 out there.
The main hurdle that I have seen is that the pl
On 27 Dec 06, at 7:17 AM 27 Dec 06, Dennis Lundberg wrote:
Hi
I've been trying to get the changes plugin into a releasable state.
But it has been going on for too long, I did however manage to get
a 2.0-beta-2 out there.
The main hurdle that I have seen is that the plugin does too much
Dennis Lundberg wrote:
Hi
I've been trying to get the changes plugin into a releasable state. But
it has been going on for too long, I did however manage to get a
2.0-beta-2 out there.
I just checked to see if there were any differences between 2.0-beta-2
and the current SVN trunk. The chan
Hi
I've been trying to get the changes plugin into a releasable state. But
it has been going on for too long, I did however manage to get a
2.0-beta-2 out there.
The main hurdle that I have seen is that the plugin does too much at the
same time. This has also been seen on the user list where
Definitely +1
Stéphane
On 12/27/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
Hi,
Is anyone actually using this because I'd like to sync this up with
the reporting we're doing for voting. The JIRA stuff in the changes
plugin is now obsoleted by the Swizzle (it just kicks ass), and I
would like
We use the changes plugin but only the changes.xml report generator.
+1 on your changes.
On 12/26/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
Hi,
Is anyone actually using this because I'd like to sync this up with
the reporting we're doing for voting. The JIRA stuff in the changes
plugin is n
+1
You can do the same for m1 ;-)
Arnaud
On 12/27/06, Brett Porter <[EMAIL PROTECTED]> wrote:
+1
On 27/12/2006, at 11:59 AM, Jason van Zyl wrote:
> Hi,
>
> Is anyone actually using this because I'd like to sync this up with
> the reporting we're doing for voting. The JIRA stuff in the change
+1
On 27/12/2006, at 11:59 AM, Jason van Zyl wrote:
Hi,
Is anyone actually using this because I'd like to sync this up with
the reporting we're doing for voting. The JIRA stuff in the changes
plugin is now obsoleted by the Swizzle (it just kicks ass), and I
would like to remove the mail
Hi,
Is anyone actually using this because I'd like to sync this up with
the reporting we're doing for voting. The JIRA stuff in the changes
plugin is now obsoleted by the Swizzle (it just kicks ass), and I
would like to remove the mail sending stuff and put it in an
announcement component
14 matches
Mail list logo