Closed
Bug 8025
Opened 25 years ago
Closed 15 years ago
[FEATURE] Integrate mail/news wizard into profile wizard
Categories
(SeaMonkey :: MailNews: Account Configuration, enhancement, P4)
Tracking
(Not tracked)
RESOLVED
WONTFIX
Future
People
(Reporter: selmer, Unassigned)
References
Details
The new plan is that the profile wizard will instantiate the mail wizard to fill
in the initial settings when the profile is created. Since their wizard will be
designed to handle multiple mail accounts, we should get that for free under the
new plan. That's scheduled to come in for M8. Marking this bug for M9 unless
tighter coordination is discovered to be possible.
Reporter | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M9
Reporter | ||
Comment 2•25 years ago
|
||
P3s aren't going to make it in M10. Bulk moving to M11.
Reporter | ||
Updated•25 years ago
|
Summary: Integrate mail/news wizard into profile wizard → [FEATURE] Integrate mail/news wizard into profile wizard
Reporter | ||
Comment 3•25 years ago
|
||
Added [FEATURE] to summary.
Component: Profile Manager → Localization
Product: Browser → MailNews
Reporter | ||
Comment 7•25 years ago
|
||
Not a profile manager tracker, removing from the PM tracking bug.
(I'm temporarily changing the component to Front End since we can't have any
existing bugs when I change Profile Manager component to Account Setup
component.)
Updated•25 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M11 → M14
Comment 9•25 years ago
|
||
Hrm. This doesn't really need to be fixed for PR1, since:
1) we aren't doing webmail for PR1, so this doesn't have to be synced
w/netcenter
2) the account dialog will come up automatically if there are no accounts when
you open messenger.
Since this requires signifigant changes to the account wizard, I'm moving this
to post PR1.
Updated•25 years ago
|
Component: Front End → Account Manager
Updated•25 years ago
|
Target Milestone: M14 → M15
Updated•25 years ago
|
Target Milestone: M15 → M17
Comment 10•25 years ago
|
||
Do we really need to do this? Seems like a reasonable simplification to leave it
as it is (mail account wizard not connected to profile wizard)
Reporter | ||
Comment 11•25 years ago
|
||
The thing we lose is the ability for the user to set up their mail information
at the same time they create the profile. I think we've generally converged on
not wanting that very much anymore. Perhaps this should move to help wanted.
Reporter | ||
Comment 13•25 years ago
|
||
[FEATURE] bugs past M16 are OUT for this release. Marking M20. If you disagree
with this action, please help me explain it to the PDT.
Target Milestone: M17 → M20
Comment 14•24 years ago
|
||
Moving feature bugs to target milestone "Future" for next release consideration.
Severity: normal → enhancement
Target Milestone: M20 → Future
Comment 15•24 years ago
|
||
massive reassign of account manager bugs -> sspitzer
please feel free to put me back on the CC if you have any questions/comments
Assignee: alecf → sspitzer
Status: ASSIGNED → NEW
Comment 16•24 years ago
|
||
mass re-assign of account manager bugs to racham.
Assignee: sspitzer → racham
Comment 17•23 years ago
|
||
Just curious- since this hasn't been touched for 1.25 yr (and not discussed for
two years), what's the status of this bug? Is it a WONTFIX as per comment 10? Or
will it be fixed sometime in the post-1.0 stage?
Reporter | ||
Comment 18•23 years ago
|
||
Daniel, we sometimes have enhancement/future bugs as a way to say "we wouldn't
mind having this, but we're not going to work on it anytime soon." If we close
it wontfix, that would mean that we wouldn't want this even if a patch were
available. That _may_ be the right answer, but I don't think it would be
related to the age of the bug.
Updated•20 years ago
|
Product: Browser → Seamonkey
Updated•20 years ago
|
Assignee: sspitzer → mail
Comment 20•15 years ago
|
||
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.
If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.
Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
Comment 21•15 years ago
|
||
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.
If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.
Query tag for this change: mass-UNCONFIRM-20090614
Comment 22•15 years ago
|
||
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.
If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.
Query tag for this change: mass-UNCONFIRM-20090614
Comment 23•15 years ago
|
||
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.
If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.
Query tag for this change: mass-UNCONFIRM-20090614
Comment 24•15 years ago
|
||
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.
If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.
Query tag for this change: mass-UNCONFIRM-20090614
Comment 25•15 years ago
|
||
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.
If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.
Query tag for this change: mass-UNCONFIRM-20090614
Comment 26•15 years ago
|
||
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.
Because of this, we're resolving the bug as EXPIRED.
If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.
Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•