Re: Jira changes

From: Andrey Razumovsky (razumovsky.andre..mail.com)
Date: Sat Nov 08 2008 - 13:52:07 EST

  • Next message: Andrus Adamchik (JIRA): "[jira] Closed: (CAY-1036) I am working in linux and I want"

    I've seen some obviously obsolete and dead issues in Jira, like CAY-1036 or
    CAY-708. It'll be great to clean out those issues and assign among us bunch
    of the most important opened ones.
    As of the versions, detail version number is great.

    About M5, I'm still not sure what should we do with CAY-1077. Switching
    between single and double click is a minute work and I'd prefer we close it
    and release M5 as fast as possible.

    About Confluence, could someone give me permission rights to edit pages?
    Username is "andrey".

    2008/11/8, Aristedes Maniatis <ar..sh.com.au>:
    >
    >
    > On 08/11/2008, at 11:08 PM, Andrus Adamchik wrote:
    >
    > On Nov 8, 2008, at 2:32 AM, Aristedes Maniatis wrote:
    >>
    >> 1. Should we point Jira emails to the svn list instead just like
    >>> Confluence emails? I think that is better since it doesn't create so much
    >>> noise. I don't want to discourage potential contributors from subscribing to
    >>> this list. If so, I can't see where this setting lives in Jira.
    >>>
    >>
    >> +0. Either list is fine with me. It should be under "notification schemes"
    >>
    >
    > I'm not seeing that. Perhaps an access rights thing. Personally, I'd love
    > to get them onto the svn list so that it is easier to track conversations.
    >
    >
    > 3. I'll go through and assign all the M5 tasks which have been done and the
    >>> ones I know are being worked on. If I feel like a mind-numbing task one
    >>> night I'll do a few more earlier milestones as well. Any objections to this
    >>> approach?
    >>>
    >>
    >> +1. A comments on the details: From experience using Jira as a release
    >> management tool on a commercial project, I'd suggest setting "Fix version"
    >> to the target milestone. Among other things this allows auto-generation of
    >> the release notes. "Affects Version/s" on the other hand should be the
    >> version <= "fix version" or null. For bugs, affected version is usually a
    >> version where a bug was discovered. For the new features it is more vague,
    >> and may even be left empty.
    >>
    >
    > Yes, that's what I've done so far. So we get something like this:
    >
    >
    > https://issues.apache.org/cayenne/secure/ReleaseNote.jspa?projectId=10000&styleName=Html&version=10120
    >
    > We'll convert our release notes file to html I guess. We can even try again
    > to do that thing with embedding Jira blocks inside Confluence although last
    > time we tried that had some problems with the export plugin we use at
    > Apache.
    >
    > Ari
    >
    >
    >
    >
    >
    > -------------------------->
    > ish
    > http://www.ish.com.au
    > Level 1, 30 Wilson Street Newtown 2042 Australia
    > phone +61 2 9550 5001 fax +61 2 9550 4001
    > GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
    >
    >
    >



    This archive was generated by hypermail 2.0.0 : Sat Nov 08 2008 - 13:52:40 EST