Re: [dev] 470 "versions" in issuezilla, can we drop a couple of hundred ?
On Tue, 2007-06-26 at 08:13 +0200, Frank Schönheit - Sun Microsystems Germany wrote: > To not end up with fruitless discussions here, I suggest somebody > (Caolan?) submits an issue to collab.net requesting the possibility to > limit the version list when submitting an issue. Then let's get Stefan > on board, and see what collab.net says about it. Well, logged as http://qa.openoffice.org/issues/show_bug.cgi?id=78883 Not sure that it is on collab's tracker as a simple against website bug. Feel free to reassign it if anyone has a better idea as to where it should go. C. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] 470 "versions" in issuezilla, can we drop a couple of hundred ?
Hi Mathias, > About the problem you > mentioned: it would need a permanent maintenance to keep the versions > updated, yes. But that happens anyway when new versions arrive. So let's > hope old versions can be removed as easy as new ones can be added. Sorry, but "let's hope" isn't a good basis. Currently there exists an administrative interface which allows to add new versions, for users which have the respective privileges. There exists, to my best knowledge, no administrative interface for the submission form. So either changes to this form require permanent issues to collab.net, or collab.net needs to create this administrative interface. The first doesn't really scale, the second doesn't sounds as if it will happen. To not end up with fruitless discussions here, I suggest somebody (Caolan?) submits an issue to collab.net requesting the possibility to limit the version list when submitting an issue. Then let's get Stefan on board, and see what collab.net says about it. Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Base http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] 470 "versions" in issuezilla, can we drop a couple of hundred ?
Frank Schönheit - Sun Microsystems Germany wrote: > Hi Caolan, > >> I'd hope that we could just remove the ability to *add* new bugs against >> those milestones. i.e. that we'd just list the last couple of milestones >> and the actual releases as options on the bug submission pages. I'm all >> for leaving the current "version" that bugs are logged against >> untouched. > > Ah! > > Not sure how that would work. In fact I think for this, we *do* need > collab.net, which would need to change the IZ installation. Hurdles for > such requests have always been high in the past ... The more since here, > we're talking about something we would need constant updates over time. IIRC it should be possible to have different entries in the listbox when submitting or when editing an issue. At least e.g. the listbox for "component" looks different in both cases. That would be enough for what Caolan suggested. About the problem you mentioned: it would need a permanent maintenance to keep the versions updated, yes. But that happens anyway when new versions arrive. So let's hope old versions can be removed as easy as new ones can be added. Ciao, Mathias -- Mathias Bauer (mba) - Project Lead OpenOffice.org Writer OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't reply to "[EMAIL PROTECTED]". I use it for the OOo lists and only rarely read other mails sent to it. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] 470 "versions" in issuezilla, can we drop a couple of hundred ?
Hi Allen, > How about just changing the UI on the website? We could make it so that > normally only the "active" versions would be displayed in the scrolling > list, but somewhere there would be a checkbox or other option to make it > display all versions. In the search screen, we could also add some > "meta-versions" to the list, i.e., "Any version", "Any v1.x", "Any v2.x", > etc. Unfortunately, things like this require changes to the IssueZilla installation. Since IssueZilla effectively is in maintainance mode only at collab.net (future version of CEE, the web hosting package provided by collab.net, on which OOo is running, will contain another bug tracking system), chances are rather low ... Even it it weren't, chances as you describe them are difficult to do in an alive production system, we would probably have to wait for a next verions, anyway. Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Base http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [dev] 470 "versions" in issuezilla, can we drop a couple of hundred ?
> > Can we cull these to at least remove all the milestones < > current - 5, > > and consider dropping the release candidates and the 1.0.X releases. > What would we do then with the issues which currently have > one of those versions set? We cannot simply remove the > versions, this would violate the data integrity. We would > have to reset this field for the affected issues. How about just changing the UI on the website? We could make it so that normally only the "active" versions would be displayed in the scrolling list, but somewhere there would be a checkbox or other option to make it display all versions. In the search screen, we could also add some "meta-versions" to the list, i.e., "Any version", "Any v1.x", "Any v2.x", etc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] 470 "versions" in issuezilla, can we drop a couple of hundred ?
Hi Caolan, > I'd hope that we could just remove the ability to *add* new bugs against > those milestones. i.e. that we'd just list the last couple of milestones > and the actual releases as options on the bug submission pages. I'm all > for leaving the current "version" that bugs are logged against > untouched. Ah! Not sure how that would work. In fact I think for this, we *do* need collab.net, which would need to change the IZ installation. Hurdles for such requests have always been high in the past ... The more since here, we're talking about something we would need constant updates over time. I think the proper way is to submit an issue requesting it. Component www, sub component IssueZilla. Then, let's ask Stefan to lobby for it - I suppose he would support us. Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Base http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] 470 "versions" in issuezilla, can we drop a couple of hundred ?
On Fri, 2007-06-22 at 20:01 +0200, Frank Schönheit - Sun Microsystems Germany wrote: > Hi Caolan, > > > There are 470, four hundred and seventy! "versions" listed by issuezilla > > for e.g. tools. > > way too much, agreed. The better solution would be if Version was a > free-text field, but alas ... > > > Can we cull these to at least remove all the milestones < current - 5, > > and consider dropping the release candidates and the 1.0.X releases. > > What would we do then with the issues which currently have one of those > versions set? We cannot simply remove the versions, this would violate > the data integrity. We would have to reset this field for the affected > issues. I'd hope that we could just remove the ability to *add* new bugs against those milestones. i.e. that we'd just list the last couple of milestones and the actual releases as options on the bug submission pages. I'm all for leaving the current "version" that bugs are logged against untouched. C. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] 470 "versions" in issuezilla, can we drop a couple of hundred ?
Hi Caolan,
> There are 470, four hundred and seventy! "versions" listed by issuezilla
> for e.g. tools.
way too much, agreed. The better solution would be if Version was a
free-text field, but alas ...
> Can we cull these to at least remove all the milestones < current - 5,
> and consider dropping the release candidates and the 1.0.X releases.
What would we do then with the issues which currently have one of those
versions set? We cannot simply remove the versions, this would violate
the data integrity. We would have to reset this field for the affected
issues.
Then, reset to which value? Issue handling guidelines say one shouldn't
touch the version field, it should contain the version of *first*
occurance. If we would want to re-version existing (open) issues to a
newer milestone where they still appear - this guideline would need to
be discussed first. Also, who will do the work to verify whether those
issues really still happen? Or do we silently assume they do?
If we re-version the existing (open) issues to something else
("indetermined" or whatever), this would be a loss of imporant
information. Not a good idea, in general. We would at least need some
script which re-adds this information to a comment. Even then, there
should be a broader consensus that this is the way to go, since the
information is more difficult to find in the comments, as opposed the
dedicated Version field.
Alternatively, let convince collab.net to change this to a free-text.
Ah, what am I saying here? Forget it, just kidding.
> Who's the contact for the versions, collabnet ?
There's a few people who have the power to administrate this aspect of
IssueZilla. So once there's an agreement, this can easily be done
without collab.net. However, the agreement is the difficult part.
Do you have some numbers about issues on older milestones? What I would
be interested in is
- About what milestones do we actually talk, more precise?
- How many unresolved issues exist which are versioned to one of those
milestones?
Without knowing this, we can, IMO, not decide what to do.
Ciao
Frank
--
- Frank Schönheit, Software Engineer [EMAIL PROTECTED] -
- Sun Microsystems http://www.sun.com/staroffice -
- OpenOffice.org Base http://dba.openoffice.org -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] 470 "versions" in issuezilla, can we drop a couple of hundred ?
On 2007.06.22. 16:45, Caolan McNamara wrote: There are 470, four hundred and seventy! "versions" listed by issuezilla for e.g. tools. Can we cull these to at least remove all the milestones < current - 5, and consider dropping the release candidates and the 1.0.X releases. this would be awesome. i've mentioned this a couple of times here and there, but that lead to nothing :) it's not like anybody would accept a bugreport for 99% of those versions anyway... and it is a pain to find the correct version in a huge dropdown. thanks for bringing this up again :) Who's the contact for the versions, collabnet ? C. -- Rich - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[dev] 470 "versions" in issuezilla, can we drop a couple of hundred ?
There are 470, four hundred and seventy! "versions" listed by issuezilla for e.g. tools. Can we cull these to at least remove all the milestones < current - 5, and consider dropping the release candidates and the 1.0.X releases. Who's the contact for the versions, collabnet ? C. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
