I think Robert's point is that we should generate a summary page from the
details in JIRA which will avoid re-typing/aging of the information.
Regards,
Marnie
Alan Conway <[EMAIL PROTECTED]>
18/09/2006 16:29
Please respond to qpid-dev
To: [email protected]
cc:
Subject: Re: Qpid Release Process
I've seen similar approaches. Jira is the way to capture the individual
bite-sized pieces of the release, but it's not great for representing
the larger goals. The wiki is good for that, and you can have links
either way where that's helpful.
(Disclaimer - haven't used Jira yet am assuming it's similar to other
bug tracking systems. Maybe it can do more than I think.)
On Mon, 2006-09-18 at 10:57 -0400, Rajith Attapattu wrote:
> Robert,
>
> The preffered way of capturing features (and of course bug fixes) is to
open
> a JIRA.
> But it also helps if we can have a page that list down the high level
> features list/ wish list so that people know where to go to get an idea
> about the current release.
>
> All details should be in JIRA, the wiki page is just a summary and a
> convinience where you see everything in one page.
>
> Comments are most welcomed
>
> Regards,
>
> Rajith
>
> On 9/17/06, Robert Greig <[EMAIL PROTECTED]> wrote:
> >
> > > I have create a release page in wiki
> > > http://wiki.apache.org/qpid/QpidReleasePage
> > > I have captured the release process and created a sample page for M1
> > > release.
> > >
> > > Please feel free to add/edit details and lets start planning for the
M1
> > > release (or whatever name we want to give it)
> >
> > Hi,
> >
> > I have just one question, relating to this point:
> >
> > "Create a wiki page and start capturing the feature/bug fix list for
> > the release"
> >
> > Can we use Jira's release notes generation for this rather than
> > maintaining a separate page? We can just provide a link to the Jira
> > release notes.
> >
> > Actually, do we have a Jira project yet?
> >
> > RG
> >
This communication is for informational purposes only. It is not intended as an
offer or solicitation for the purchase or sale of any financial instrument or
as an official confirmation of any transaction. All market prices, data and
other information are not warranted as to completeness or accuracy and are
subject to change without notice. Any comments or statements made herein do not
necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and
affiliates.
This transmission may contain information that is privileged, confidential,
legally privileged, and/or exempt from disclosure under applicable law. If you
are not the intended recipient, you are hereby notified that any disclosure,
copying, distribution, or use of the information contained herein (including
any reliance thereon) is STRICTLY PROHIBITED. Although this transmission and
any attachments are believed to be free of any virus or other defect that might
affect any computer system into which it is received and opened, it is the
responsibility of the recipient to ensure that it is virus free and no
responsibility is accepted by JPMorgan Chase & Co., its subsidiaries and
affiliates, as applicable, for any loss or damage arising in any way from its
use. If you received this transmission in error, please immediately contact the
sender and destroy the material in its entirety, whether in electronic or hard
copy format. Thank you.
