FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Ubuntu > Launchpad User

 
 
LinkBack Thread Tools
 
Old 07-17-2008, 11:00 PM
"Martin Pool"
 
Default automatically mark bugs fixed in a release as released?

It would be really nice if Launchpad had a way to mark all
fix-committed bugs targeted to a release as fix-released when that
release comes out. Could this be added?

---------- Forwarded message ----------
From: Alexander Belchenko <bialix@ukr.net>
Date: Jul 17, 2008 8:50 PM
Subject: Re: [Bug 247585] Fix Committed/Fix released
To: mbp@sourcefrog.net


James Westby пишет:

> On Thu, 2008-07-17 at 09:49 +0000, vila wrote:
>>>>>>> "Daniel" == Daniel Watkins <daniel@daniel-watkins.co.uk> writes:
>> Daniel> Adrian,
>> Daniel> We actually use 'Fix Committed' to mean 'submitted to the ML for
>> Daniel> review' and 'Fix Released' to mean merged to bzr.dev.
>>
>> I don't think so.
>>
>> I think we use 'Fix Committed' when merged to bzr.dev and 'Fix
>> Released' when actually released and then we set the release
>> number so that users (and we) know *when* the fix is actually
>> available (or in which releases).
>>
>
> I believe that's how the field is intended to be used, but Bazaar
> currently does it the way Daniel described. There was some
> discussion at the last sprint about this, and I would favour
> switching. One of the things that was standing in the way was
> that it would be quite a lot of effort for the release manager
> to do this. I volunteered to write a script to automate this, but
> I haven't done so, my apologies.


IMO, it's the bug in Launchpad interface that you don't have any
way to mark all bugs related to some milestone as Fix Released.
Doing this by hand is terrible experience.


>
> What else would be stopping us from switching? Would having
> that script be enough?


Such script will be useful for many Launchpad-hosted projects, IMO.


--
Angle bracketed boundary lines from IIS cause failure
https://bugs.launchpad.net/bugs/247585
You received this bug notification because you are a member of Bazaar
Developers, which is the registrant for Bazaar.



--
Martin <http://launchpad.net/~mbp/>
--
launchpad-users mailing list
launchpad-users@lists.canonical.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/launchpad-users
 
Old 07-17-2008, 11:21 PM
Jamu Kakar
 
Default automatically mark bugs fixed in a release as released?

Hi,

Martin Pool wrote:
> It would be really nice if Launchpad had a way to mark all
> fix-committed bugs targeted to a release as fix-released when that
> release comes out. Could this be added?

FWIW, this is also a problem for us on the Landscape team. We use
milestones to organize our 2-week iterations, which means that we
have to deal with this regularly.

There's a second problem we have, which is related, which is that we
don't always complete all the bugs we've assigned to a milestone.
It'd be nice to have a way to push all !fix-committed bugs to the
next milestone in one fell swoop.

Thanks,
J.

--
launchpad-users mailing list
launchpad-users@lists.canonical.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/launchpad-users
 
Old 07-21-2008, 10:32 AM
Matthew Paul Thomas
 
Default automatically mark bugs fixed in a release as released?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jamu Kakar wrote on 18/07/08 00:21:
>...
> Martin Pool wrote:
>>
>> It would be really nice if Launchpad had a way to mark all
>> fix-committed bugs targeted to a release as fix-released when that
>> release comes out. Could this be added?
>
> FWIW, this is also a problem for us on the Landscape team. We use
> milestones to organize our 2-week iterations, which means that we
> have to deal with this regularly.
>...

I would rather merge Fix Committed and Fix Released into a single
status, so that you don't need to spend time on this status change at all.

The two distinct statuses were intended to help filter out long-fixed
bugs from searches. But that doesn't work, especially in large projects,
and in projects that have alpha or beta releases. I think the same
purpose could be more easily served by a time-based filter.
<http://launchpad.net/bugs/163694>

> There's a second problem we have, which is related, which is that we
> don't always complete all the bugs we've assigned to a milestone.
> It'd be nice to have a way to push all !fix-committed bugs to the
> next milestone in one fell swoop.
>...

<http://launchpad.net/bugs/3454>

Cheers
- --
Matthew Paul Thomas
http://mpt.net.nz/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIhGXa6PUxNfU6ecoRAuvlAKDGiywTRO5fhae58NgafF M7vFGacwCgu5FA
9IwssoKzu3R5XcEk3go18gc=
=RWCn
-----END PGP SIGNATURE-----

--
launchpad-users mailing list
launchpad-users@lists.canonical.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/launchpad-users
 
Old 07-22-2008, 07:52 AM
"Martin Pool"
 
Default automatically mark bugs fixed in a release as released?

On 7/21/08, Matthew Paul Thomas <mpt@canonical.com> wrote:
> > Martin Pool wrote:
> >> It would be really nice if Launchpad had a way to mark all
> >> fix-committed bugs targeted to a release as fix-released when that
> >> release comes out. Could this be added?
> >
> > FWIW, this is also a problem for us on the Landscape team. We use
> > milestones to organize our 2-week iterations, which means that we
> > have to deal with this regularly.
>
> I would rather merge Fix Committed and Fix Released into a single
> status, so that you don't need to spend time on this status change at all.
>
> The two distinct statuses were intended to help filter out long-fixed
> bugs from searches. But that doesn't work, especially in large projects,
> and in projects that have alpha or beta releases. I think the same
> purpose could be more easily served by a time-based filter.
> <http://launchpad.net/bugs/163694>

I think that is a brilliant simplification.

At present people tend to put information about when a bug was fixed
into a text comment, such as "will be fixed in 1.6b2". This is easy
to understand, and won't lose anything from merging the statuses.

--
Martin <http://launchpad.net/~mbp/>

--
launchpad-users mailing list
launchpad-users@lists.canonical.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/launchpad-users
 

Thread Tools




All times are GMT. The time now is 08:10 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org