Closed Bug 1752817 Opened 3 years ago Closed 3 years ago

Please move JSS::*** into the graveyard

Categories

(bugzilla.mozilla.org :: Graveyard Tasks, task)

Production
task
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: calixte, Assigned: dkl)

References

(Blocks 1 open bug)

Details

The last bug has been reported 4 years ago and according to:
https://developer.mozilla.org/en-US/docs/Mozilla/Projects/NSS/JSS
the project has been moved on github.
I guess it's time to move it into the graveyard.

We will need to mass close the remaining open bugs with some sort of comment explaining why they are being closed. Can you provide a brief comment that I can add using my closure script?

https://bugzilla.mozilla.org/buglist.cgi?product=JSS&resolution=---

Flags: needinfo?(cdenizet)

:beurdouche, could you provide this comment please ?

Flags: needinfo?(cdenizet) → needinfo?(bbeurdouche)

Hi Calixte,
I am ok with this, thank you. : )

@Alexander, @Bob, can you please confirm that this is fine with you?

Thanks!
Benjamin

Flags: needinfo?(rrelyea)
Flags: needinfo?(bbeurdouche)
Flags: needinfo?(alexander.m.scheel)

I think that's fine.

Flags: needinfo?(rrelyea)

I'm OK closing as well and confirmed with Endi and the present team that they're fine with this.

Perhaps a message like:

JSS development has moved from the Mozilla community to the Dogtag PKI community.

Please re-file this bug at https://github.com/dogtagpki/jss if it is still relevant.

Thank you!

  • A
Flags: needinfo?(alexander.m.scheel)

(In reply to Alexander Scheel from comment #5)

JSS development has moved from the Mozilla community to the Dogtag PKI community.

Please re-file this bug at https://github.com/dogtagpki/jss if it is still relevant.

Thank you!

Are we OK with the above closure message? If so I can do these steps today.

Flags: needinfo?(cdenizet)

Yes, that message looks ok ! Thank you!

All done.

Assignee: nobody → dkl
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Flags: needinfo?(cdenizet)
You need to log in before you can comment on or make changes to this bug.