Community
Participate
Working Groups
Bugzilla 3.2.x has reached End Of Life (EOL) and is now unsupported. I'm sure the other release will eventually follow. We should update to the newly released 4.0 when we have time. http://www.bugzilla.org/releases/4.0/release-notes.html#v40_feat Looks like it has some new features that could benefit our community when filing bugs. We'd also have to check if Mylyn would work against 4.0 and all that good stuff.
We're running Bugzilla 3.6, which won't be EOL for quite some time. I'd rather wait a bit on Bugzilla 4.0 -- most likely until at least after Indigo has shipped.
(In reply to comment #1) > We're running Bugzilla 3.6, which won't be EOL for quite some time. I'd rather > wait a bit on Bugzilla 4.0 -- most likely until at least after Indigo has > shipped. Sounds reasonable.
Bugzilla 4.0.1 was released recently. Steffen, is does Mylyn support BZ 4.x ? I'd like to upgrade in July.
Yes, Mylyn 3.5 (released in March 2011) supports Bugzilla 4.0 and Indigo will be as well. It would be great if we could setup a sandbox instance as soon as possible to make sure Mylyn works with the Eclipse.org configuration as well.
I've got a sandbox 4.0.1 running at https://bugs.eclipse.org/bugstest/ I haven't fully tested it out, and I haven't ported all our minor template tweaks, but at first glance it seems to work.
Thanks Denis. We'll do some testing of Mylyn against the sandbox instance.
Looking at the sandbox it looks like votes are gone. This feature has been moved to an extension, see http://www.bugzilla.org/releases/4.0/release-notes.html#v40_feat_vot_ext.
I've seen that. Looks like the voting system will eventually be going away.
(In reply to comment #8) > I've seen that. Looks like the voting system will eventually be going away. Is the extension no longer free?
I think they are pulling it out of core code because they're lacking the resources to maintain/advance it.
Sorry, I can not login using my actual account information. Thoughts?
The account (and bug info) is quite old. Perhaps try an older password? I'm scheduling the upgrade for Sunday, Aug 28 in the early AM (Eastern time). Steffen, how do things look from your perspective?
I've upgraded the sandbox to 4.0.2 since it was released recently. It all looks well.
Sorry, I didn't get around to doing any detailed testing, yet. I'll let you know tomorrow. Frank, did you have any luck logging in?
(In reply to comment #14) > Sorry, I didn't get around to doing any detailed testing, yet. I'll let you > know tomorrow. Frank, did you have any luck logging in? No, I can start after the upgrade (Sunday, Aug 28)
Steffen, you put a dependency on this bug... Is that your polite way of asking me to delay the upgrade I've warned you about in May?
I'm not sure... I just noticed that problem and wanted to track it connected to this bug so we don't loose it. I'll look into it and remove the dependency once I have a sense of what's going on.
It looks like the Eclipse.org instance retained the workflow transitions from 3.x. Unfortunately there is a bug in the Mylyn Bugzilla Connector that causes it to always assume that default transitions are used which changed in 4.0. Our automated tests only cover vanilla Bugzilla instances but not migrated ones so this wasn't caught. I'm sorry for noticing this problem so late. We will put out a fix but it won't be available before Indigo SR1. Denis, any chance the Bugzilla update could be postponed until then?
I second Steffen's request. I realize that there is benefit in getting Bugzilla 4.0 rolled out before then. However, we still have no mechanism to push a change to the Eclipse/Mylyn Bugzilla client in order to prevent this bug from affecting a large number of Eclipse users. We are only 4 weeks from SR1, when we can push the workflow-related fixes and improvements to everyone, so the relatively short delay seems a better option than a broken experience from anyone accessing bugs.eclipse.org from Eclipse.
What are the changes in workflow? I'd like to remain as close to vanilla BZ as I can, so we could look at changing the home site instead of carrying on with something that deviates from stock.
The default workflow statuses changed in 4.0: https://bugs.eclipse.org/bugstest/page.cgi?id=release-notes.html#v40_feat_workflow .
(In reply to comment #21) > What are the changes in workflow? I'd like to remain as close to vanilla BZ as > I can, so we could look at changing the home site instead of carrying on with > something that deviates from stock. We should not replace 'NEW' and 'ASSIGNED' at this point. Different components use those differently - even differently depending in which inbox a bug currently is, e.g. bugs in our inboxes are 'ASSIGNED' which means "confirmed" but after the mass-update they would be in 'IN_PROGREES'. Other major concerns: - REOPENED would completely disapper and the current state be lost - CLOSED will also go away and become VERIFIED which is just not true for us, as CLOSED FIXED bugs are not verified while VERIFIED FIXED ones are. Mass-updating all our bugs would destroy lots of useful state and teams won't have time to go and fine-tune that mass-update - and in fact some of the current state would be completely lost.
> We should not replace 'NEW' and 'ASSIGNED' at this point. OK, but at what point would we? We can continue working with the old workflow, but at some point we should plan on realigning with Bugzilla. I remember the REMIND/LATER changes we did years ago. Despite the uproar, we survived :)
If we stay with the old workflow we need to make sure that we do not use whineatnews.pl and bugzilla-submit scripts (see the link from comment #22). We need much more testing to make sure that all other places work like expected. +1 to switch now to the new workflow.
(In reply to comment #16) > (In reply to comment #14) > > Sorry, I didn't get around to doing any detailed testing, yet. I'll let you > > know tomorrow. Frank, did you have any luck logging in? > > No, I can start after the upgrade (Sunday, Aug 28) Frank, I've imported your current BZ password into the 4.0 sandbox. You should be all set.
(In reply to comment #26) > (In reply to comment #16) > > (In reply to comment #14) . . . > > Frank, I've imported your current BZ password into the 4.0 sandbox. You should > be all set. Great I start now with the tests!
For bug#354984 and bug#354987 I have two patch that need some more tests! BTW can we set the cookie path in the test version, so we not get lockout when using bugs and bugstest from the same machine?
My $0.02 on the workflow: Although bugzilla provides a default workflow, customizable workflows is a key feature of bugzilla and we shouldn't feel constrained to use the defaults. I may be mistaken but I don't think customizable workflow is something bugzilla is planning to remove at any time in the near future. Having said that, if we as a community think workflow changes would be helpful to us as Eclipse developers, that's worth talking about. We do have to keep in mind what impact the conversion would have on the current set of bugs, what data would be lost in transition, etc. IIRC, we removed REMIND/LATER not to conform to bugzilla defaults, but because as a community we didn't think those states where healthy/helpful (bug 157642).
> Denis, any chance the Bugzilla update could be postponed until [after SR1]? Steffen, SR1 is out. How do you feel about upgrading BZ in the following weeks?
Sounds good. It looks like we missed something (bug 359300) but I don't want to block the Bugzilla update any longer. We'll probably put another service release.
Steffe, thanks for the consideration. Although I'm eager to upgrade, there are no killer features that absolutely need deployment. If there's an issue with Mylyn, we can wait some more. DO you have the ability to deploy a hot fix?
Yes, I'm planning to do this as soon as we have confirmed the fix. We should have this sorted end of next week *sigh*.
The Mylyn release is now available from our main repository. I have tested that access to https://bugs.eclipse.org/bugstest works with Mylyn 3.6.3 as expected.
Plan is to do this Thursday, along with the authentication changes: http://www.eclipse.org/org/press-release/20111219_eclipse_account_changes.php
We're running 4.0.2 now.
Fixed. I'll patch up to 4.0.3 later today, since it fixes a few security holes.
