OK, thanks for the explanation. On 06/02/2015 10:37 PM, Mike Kienenberger wrote: > I guess I should be more specific. Using resolve on fix and close on release: > > -- Allows users to see at a glance to know if the bug is unfixed, > fixed but unreleased, or released. > > -- Allows the release manager to quickly generate a list of changes. > (At least, I'm guessing it will) > > On Tue, Jun 2, 2015 at 10:34 PM, Mike Kienenberger <mkien...@gmail.com> wrote: >> I like to resolve when fixed in svn and to close when released. >> I think it's more meaningful. >> >> On Tue, Jun 2, 2015 at 10:30 PM, Sergiu Dumitriu >> <sergiu.dumit...@gmail.com> wrote: >>> Should issues be Resolved or Closed? So far I've been closing them. >>> >>> On 06/02/2015 10:25 PM, Mike Kienenberger (JIRA) wrote: >>>> >>>> [ >>>> https://issues.apache.org/jira/browse/VELOCITY-861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel >>>> ] >>>> >>>> Mike Kienenberger resolved VELOCITY-861. >>>> ---------------------------------------- >>>> Resolution: Fixed >>>> >>> >>> -- >>> Sergiu Dumitriu >>> http://purl.org/net/sergiu/ >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org >>> For additional commands, e-mail: dev-h...@velocity.apache.org >>> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org > For additional commands, e-mail: dev-h...@velocity.apache.org >
-- Sergiu Dumitriu http://purl.org/net/sergiu/ --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org For additional commands, e-mail: dev-h...@velocity.apache.org
