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 > Redhat > Fedora Development

 
 
LinkBack Thread Tools
 
Old 10-28-2009, 08:39 PM
TK009
 
Default Upcoming Bugzilla Changes

The time is almost here to reap the harvest on which so many have toiled and
enjoy the bounty that is Fedora 12. With each new Fedora release comes some
Bugzilla housekeeping. This e-mail is designed to let you know about two things
happening around November 17, 2009 (Fedora 12 release day) and
what you need to do, if anything.

(1) We will be automatically changing the version all rawhide bugs to Fedora 12.
This will result in regular bugs reported against rawhide during the Fedora 12
development cycle being changed to version '12' instead of their current
assignment, 'rawhide'. This is done in order to more accurately tell where in
the lineage of releases the bug was last reported because over time 'rawhide'
becomes ambiguous.

Note that this procedure does not apply to bugs that are against component
'Package Review' or bugs that have the 'FutureFeature' or 'Tracking' keywords
set.
They will stay open as rawhide bugs indefinitely.

If you do not want your bugs changed to version '12', add the FutureFeature
keyword.
If you need help changing a large amount of bugs manually, we'd be glad to help.
Stop by #fedora-bugzappers on irc.freenode.net and we'll help you.

(2) All bugs for upcoming EOL releases (at this point, Fedora 10) will get a
comment on release day, explaining that one month of maintenance remains.
These bugs must move to a later version if still applicable or they will be
automatically closed in one month with a resolution of WONTFIX.

More about these processes is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping

Thanks for reading,
Edward Kirk
Fedora Bug Triage Team

_______________________________________________
Fedora-devel-announce mailing list
Fedora-devel-announce@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-announce

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 03-05-2010, 02:53 AM
TK009
 
Default Upcoming Bugzilla Changes

Greetings

I hope everyone is well. With the worst of the “snowpocalypse" behind us 
(here in the Northern Hemisphere) and the branching of Fedora 13, there
is a bit of ‘spring cleaning’ the the bugzappers need to do. This
e-mail is designed to
let you know about the upcoming bugzilla changes happening around March 9, 2010
(Rawhide bug rebase) and what you need to do, if anything.

We will be automatically changing the version all rawhide bugs to Fedora 13.
This will result in regular bugs reported against rawhide during the Fedora 13
development cycle being changed to version ‘13' instead of their
current assignment,
‘rawhide’. This is to align with the branching of Fedora 13 from
rawhide and to more
accurately tell where in the lineage of releases the bug was last reported.

Note that this procedure does not apply to bugs that are against component
‘Package Review’ or bugs that have the ‘FutureFeature’ or ‘Tracking’
keywords set.
They will stay open as rawhide bugs indefinitely.

If you do not want your bugs changed to version ‘13‘, add the
FutureFeature keyword.
If you need help changing a large amount of bugs manually, we’d be
glad to help.
Stop by #fedora-bugzappers on irc.freenode.net and we’ll help you.

More about these processes is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping

“Rock It !"
Edward Kirk
Fedora Volunteer Bug Triage Team
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 
Old 03-05-2010, 10:08 AM
Mike Chambers
 
Default Upcoming Bugzilla Changes

On Thu, 2010-03-04 at 22:53 -0500, TK009 wrote:

> We will be automatically changing the version all rawhide bugs to Fedora 13.
> This will result in regular bugs reported against rawhide during the Fedora 13
> development cycle being changed to version ‘13' instead of their
> current assignment,
> ‘rawhide’. This is to align with the branching of Fedora 13 from
> rawhide and to more
> accurately tell where in the lineage of releases the bug was last reported.
>
> Note that this procedure does not apply to bugs that are against component
> ‘Package Review’ or bugs that have the ‘FutureFeature’ or ‘Tracking’
> keywords set.
> They will stay open as rawhide bugs indefinitely.

Since rawhide is based now on F14, will the change/scripts make sure
that if the bug reported is against F13 and not an F14 package?


--
Mike Chambers
Madisonville, KY

"Best lil town on Earth!"

--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 
Old 03-05-2010, 11:27 AM
Till Maas
 
Default Upcoming Bugzilla Changes

On Thu, Mar 04, 2010 at 10:53:54PM -0500, TK009 wrote:

> I hope everyone is well. With the worst of the “snowpocalypse" behind us 
> (here in the Northern Hemisphere) and the branching of Fedora 13, there
> is a bit of ‘spring cleaning’ the the bugzappers need to do. This
> e-mail is designed to
> let you know about the upcoming bugzilla changes happening around March 9, 2010
> (Rawhide bug rebase) and what you need to do, if anything.

> More about these processes is here:
> https://fedoraproject.org/wiki/BugZappers/HouseKeeping

| rawhide always refers the release currently under development which
| has not been released or reached GA (general availability)
[...]
| The new version number for the next Fedora release is added to
| Bugzilla on the day of general availability (GA).
| Changes to this policy require review and approval by FESCo.

Before you do anything that is described on that wiki page, it needs to
be updated to match the current no frozen rawhide situation. Since it
requires FESCo approval, targeting 2010-03-09 seems to be kind of
unrealistic.

Especially it needs to be made sure that only bugs created prior to
adding "F13" to RedHat Bugzilla or the branching of F13, depending on
what happened later, are touched by the "Rawhide bug rebase".

Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 
Old 03-05-2010, 01:11 PM
Kevin Kofler
 
Default Upcoming Bugzilla Changes

Till Maas wrote:
> Before you do anything that is described on that wiki page, it needs to
> be updated to match the current no frozen rawhide situation. Since it
> requires FESCo approval, targeting 2010-03-09 seems to be kind of
> unrealistic.

Quite the opposite, the switchover needs to happen ASAP so the bugs which
need to be manually reset to rawhide get minimized.

> Especially it needs to be made sure that only bugs created prior to
> adding "F13" to RedHat Bugzilla or the branching of F13, depending on
> what happened later, are touched by the "Rawhide bug rebase".

Unfortunately there's no metric that actually works to magically figure that
out. Date of creation does not work because the targeted release can get
changed after the fact. So fixing things manually where the script makes an
unwanted change or doesn't make a wanted change is the only way.

Kevin Kofler

--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 
Old 03-05-2010, 01:42 PM
Till Maas
 
Default Upcoming Bugzilla Changes

On Fri, Mar 05, 2010 at 03:11:23PM +0100, Kevin Kofler wrote:
> Till Maas wrote:

> > Especially it needs to be made sure that only bugs created prior to
> > adding "F13" to RedHat Bugzilla or the branching of F13, depending on
> > what happened later, are touched by the "Rawhide bug rebase".
>
> Unfortunately there's no metric that actually works to magically figure that
> out. Date of creation does not work because the targeted release can get
> changed after the fact. So fixing things manually where the script makes an
> unwanted change or doesn't make a wanted change is the only way.

Afaics it is possible to query for bugs, where the version has changed:
https://bugzilla.redhat.com/query.cgi?format=advanced
-> "where one or more of the following changed:"

So this should work:

1) get a list of all bugs with version rawhide created before the F13 event ->
rawhide-bugs
2) get a list of all bugs with version rawhide created before the F13
event, where the version has changed after the F13 event -> intended-rawhide-bugs
3) change the version for all bugs in rawhide-bugs that are not in
intended-rawhide-bugs (this logic needs to be implemented in the script)

Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 
Old 03-05-2010, 03:08 PM
Till Maas
 
Default Upcoming Bugzilla Changes

On Fri, Mar 05, 2010 at 03:42:57PM +0100, Till Maas wrote:
> On Fri, Mar 05, 2010 at 03:11:23PM +0100, Kevin Kofler wrote:
> > Till Maas wrote:
>
> > > Especially it needs to be made sure that only bugs created prior to
> > > adding "F13" to RedHat Bugzilla or the branching of F13, depending on
> > > what happened later, are touched by the "Rawhide bug rebase".
> >
> > Unfortunately there's no metric that actually works to magically figure that
> > out. Date of creation does not work because the targeted release can get
> > changed after the fact. So fixing things manually where the script makes an
> > unwanted change or doesn't make a wanted change is the only way.
>
> Afaics it is possible to query for bugs, where the version has changed:
> https://bugzilla.redhat.com/query.cgi?format=advanced
> -> "where one or more of the following changed:"
>
> So this should work:
>
> 1) get a list of all bugs with version rawhide created before the F13 event ->
> rawhide-bugs
> 2) get a list of all bugs with version rawhide created before the F13
> event, where the version has changed after the F13 event -> intended-rawhide-bugs
> 3) change the version for all bugs in rawhide-bugs that are not in
> intended-rawhide-bugs (this logic needs to be implemented in the script)

Unless this logic is broken, it takes only some seconds to generate this
list using python-bugzilla:

http://till.fedorapeople.org/tmp/get-f13-bugs.py

Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 
Old 03-05-2010, 03:14 PM
Adam Williamson
 
Default Upcoming Bugzilla Changes

On Fri, 2010-03-05 at 13:27 +0100, Till Maas wrote:

> Especially it needs to be made sure that only bugs created prior to
> adding "F13" to RedHat Bugzilla or the branching of F13, depending on
> what happened later, are touched by the "Rawhide bug rebase".

We already did that, though tk009 forgot to mention it. If you look at
the proposed query, it's cut off at the date of the branch announcement.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net

--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 
Old 03-06-2010, 06:07 PM
Till Maas
 
Default Upcoming Bugzilla Changes

On Fri, Mar 05, 2010 at 08:14:38AM -0800, Adam Williamson wrote:
> On Fri, 2010-03-05 at 13:27 +0100, Till Maas wrote:
>
> > Especially it needs to be made sure that only bugs created prior to
> > adding "F13" to RedHat Bugzilla or the branching of F13, depending on
> > what happened later, are touched by the "Rawhide bug rebase".
>
> We already did that, though tk009 forgot to mention it. If you look at
> the proposed query, it's cut off at the date of the branch announcement.

The query I was given in IRC does not take into account, which version
was specified when the bug was created. In the other subthread I
provided a script to work around this limitation.

Regards
Till
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 
Old 03-08-2010, 05:09 PM
Adam Williamson
 
Default Upcoming Bugzilla Changes

On Sat, 2010-03-06 at 20:07 +0100, Till Maas wrote:
> On Fri, Mar 05, 2010 at 08:14:38AM -0800, Adam Williamson wrote:
> > On Fri, 2010-03-05 at 13:27 +0100, Till Maas wrote:
> >
> > > Especially it needs to be made sure that only bugs created prior to
> > > adding "F13" to RedHat Bugzilla or the branching of F13, depending on
> > > what happened later, are touched by the "Rawhide bug rebase".
> >
> > We already did that, though tk009 forgot to mention it. If you look at
> > the proposed query, it's cut off at the date of the branch announcement.
>
> The query I was given in IRC does not take into account, which version
> was specified when the bug was created. In the other subthread I
> provided a script to work around this limitation.

I don't see any reason that would be more accurate than considering the
current specified version. We've never done that with previous rebase
queries. Why do you think it would be more accurate?
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net

--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 

Thread Tools




All times are GMT. The time now is 11:51 AM.

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