harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey Varlamov" <alexey.v.varla...@gmail.com>
Subject Re: [general][M3] release notes
Date Fri, 28 Sep 2007 10:46:38 GMT
2007/9/28, Sian January <sianjanuary@googlemail.com>:
> Similar to Tim's, but this one only shows issues that have been resolved
> "fixed", as opposed to "wontfix" or "invalid" etc, and doesn't include
> website issues or non-bug-differences:
>
> http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=12310050&updated%3Abefore=5%2FOct%2F07&updated%3Aafter=30%2FJun%2F07&status=5&status=6&component=12311280&component=12311279&component=12310560&component=12310327&component=12311272&component=12311442&component=12310091&component=12310353&resolution=1&sorter/field=issuekey&sorter/order=DESC
>
> I think this is a good approximation at the point in time that M3 is
> released, but if a bug is fixed after M3 but was updated in that timeframe
> then it would show up in this search wouldn't it?

Exactly, this was my assumption. There is no (visible) connection
between issue attributes and dates in query, so it select intersection
of (current status=fixed) and (updated in that interval).
>
>
>
> On 28/09/2007, Tim Ellison <t.p.ellison@gmail.com> wrote:
> >
> > Alexey Varlamov wrote:
> > > Yep, just the link to JIRA query would be the best.
> > > Though I'm also not sure Web UI allows this, unless a project uses
> > > "Due date" feature which Harmony does not.
> >
> > Well we can approximate it by querying the issues that were
> > resolved/closed between the date of M2 and the date of M3.
> >
> > The problem being that it will include issues that are not part of the
> > release per se (such as website updates):
> >
> > e.g.
> >
> > https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=12310050&updated%3Abefore=28%2FSep%2F07&updated%3Aafter=1%2FMay%2F07&status=5&status=6&sorter/field=issuekey&sorter/order=DESC
> >
> > Regards,
> > Tim
> >
> > > 2007/9/28, Sian January <sianjanuary@googlemail.com>:
> > >> Yes - I wasn't thinking that we would publish the whole list, I was
> > just
> > >> wondering if it was possible to do that kind of query in JIRA, and if
> > so, if
> > >> we could include a link to JIRA from the release notes that does the
> > query
> > >> for you.  Does that make sense?  So you click on the link and you get a
> > JIRA
> > >> search page up with the list of all the bugs fixed in M3. I know you
> > can do
> > >> it in Bugzilla but it may not be possible in JIRA (I couldn't find out
> > how
> > >> this morning).
> > >>
> > >> Otherwise (or additionally) I do think including a short list of the
> > most
> > >> important ones as you suggested would be a good idea.
> > >>
> > >> Thanks,
> > >>
> > >> Sian
> > >>
> > >>
> > >> On 28/09/2007, Nadya Morozova <nad.morozova@googlemail.com> wrote:
> > >>> Generally, i think it is a good idea to include fixed bugs (as well
as
> > >>> unfixed critical bugs) into release notes. however, i don't think we
> > need
> > >>> to
> > >>> publish them all. those interested can always query JIRA manually,
> > while
> > >>> those not particularly interested will get a longish table of info
> > they
> > >>> don't need.
> > >>> we could perhaps select the most outstanding bugs and the bugs that
> > were
> > >>> in
> > >>> known issues in M2 and are fixed in M3. what do you say?
> > >>>
> > >>> On 9/28/07, Sian January <sianjanuary@googlemail.com> wrote:
> > >>>> I'm not sure if JIRA supports this kind of query, but if it does,
> > would
> > >>> it
> > >>>> be good to include a link in the release notes to a list of all
the
> > >>> JIRAs
> > >>>> that have been fixed for M3?
> > >>>>
> > >>>>
> > >>>> On 27/09/2007, Nadya Morozova <nad.morozova@googlemail.com>
wrote:
> > >>>>> Hi all,
> > >>>>> as we're nearing the closure time for M3 snapshot, I thought
it
> > would
> > >>> be
> > >>>>> great if we started writing Release Notes for them. We managed
to do
> > >>>> that
> > >>>>> for our previous milestone M2 [1], but failed to do it on time
to
> > ship
> > >>>>> with
> > >>>>> the bundle. Let's do better this time. For convenience, I've
created
> > a
> > >>>>> Wiki
> > >>>>> page [2] to gather all things that are unlikely to be fixed
before
> > M3
> > >>> or
> > >>>>> are
> > >>>>> otherwise notable and should be in the Release Notes.
> > >>>>>
> > >>>>> I hope this way works for you. You're welcome to enter whatever
> > notes
> > >>>> you
> > >>>>> have, and I will assembly them into an HTML page and into
> > >>> site-specific
> > >>>>> XML
> > >>>>> in time for the final snapshot. Surely, an engineering review
and
> > >>>> sign-off
> > >>>>> from committers would be necessary before packaging the final
> > version.
> > >>>>>
> > >>>>> Thank you.
> > >>>>>
> > >>>>> [1]
> > >>> http://harmony.apache.org/documentation/milestones/m2-relnotes.html
> > >>>>> [2] http://wiki.apache.org/harmony/Milestone_M3_known_issues
> > >>>>>
> > >>>>> --
> > >>>>> Cheers,
> > >>>>> Nadya
> > >>>>>
> > >>>>
> > >>>>
> > >>>> --
> > >>>> Unless stated otherwise above:
> > >>>> IBM United Kingdom Limited - Registered in England and Wales with
> > number
> > >>>> 741598.
> > >>>> Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire
> > PO6
> > >>> 3AU
> > >>>
> > >>>
> > >>> --
> > >>> Cheers,
> > >>> Nadya
> > >>>
> > >>
> > >>
> > >> --
> > >> Unless stated otherwise above:
> > >> IBM United Kingdom Limited - Registered in England and Wales with
> > number
> > >> 741598.
> > >> Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6
> > 3AU
> > >>
> > >
> >
>
>
>
> --
> Unless stated otherwise above:
> IBM United Kingdom Limited - Registered in England and Wales with number
> 741598.
> Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
>

Mime
View raw message