On 4/27/06, Craig McClanahan [EMAIL PROTECTED] wrote:
On 4/26/06, Don Brown [EMAIL PROTECTED] wrote:
The resolved/closed question is interesting. I guess they could be
resolved, but reviewed and closed by the release manager. Otherwise,
I'd agree that they seem to function the same for
Leon Rosenberg wrote:
On 4/27/06, Craig McClanahan [EMAIL PROTECTED] wrote:
On 4/26/06, Don Brown [EMAIL PROTECTED] wrote:
The resolved/closed question is interesting. I guess they could be
resolved, but reviewed and closed by the release manager. Otherwise,
I'd agree that they seem to
On 4/27/06, Don Brown [EMAIL PROTECTED] wrote:
I like that, and if they don't close it by the release, the release manager
will close it.
I don't understand why we should set this up so every ticket has to be
closed twice. The tickets are already subject to peer-review by the
PMC and all the
I agree with everything you said, save the RM difficulty level. All I'm saying is the RM should look over the list of
all fixed tickets ensuring everything is in order. Thanks to Wendy, the RM can roll a release in under a hour with most
of that time taking up waiting for Maven to do its
Speaking of taglib tests..Ted, I was chatting with Don yesterday
and I mentioned an idea that someone had brought up a while back, and
so I wanted to float it by you.
Do you remember the discussions about the taglib tests where it was
proposed (sorry, don't remember who) that we use
On 4/27/06, James Mitchell [EMAIL PROTECTED] wrote:
With the move to Maven, the taglib tests were pretty much broken and
neglected. They were not neglected due to a lack of interest, but
more for technical reasons (translated -- I didn't know how to force
Maven to do what I wanted).
So,
What does the end workflow look like? Do you just add a transition to resolve
to the close step?
Don
Brett Porter wrote:
Hi,
I've noticed that there have been 1 or 2 mails recently on this list
to reopen and close jira issues. Am I correct in assuming this is to
be able to edit the fix
We actually eliminated the resolve step since weren't using it
independantly of resolve, however this doesn't affect the other part.
I'm not exactly sure of the technical details of how we made editing
possible when it was resolved/closed - but I can find out. It doesn't
actually transition to
The resolved/closed question is interesting. I guess they could be
resolved, but reviewed and closed by the release manager. Otherwise,
I'd agree that they seem to function the same for open source projects
anyways.
Don
Brett Porter wrote:
We actually eliminated the resolve step since
On 4/26/06, Don Brown [EMAIL PROTECTED] wrote:
The resolved/closed question is interesting. I guess they could be
resolved, but reviewed and closed by the release manager. Otherwise,
I'd agree that they seem to function the same for open source projects
anyways.
In my day job scenario, we
Craig McClanahan wrote:
In my day job scenario, we have the developers who commit changes
switch an
issue to Resolved, and then QE verifies the result and switches it to
Closed. I'd hate to see us stick all of that responsibility solely on a
release manager right before a release (doubt we'd
11 matches
Mail list logo
