Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move Jira issues from Java.net #18

Open
ralphlange opened this issue Jul 31, 2016 · 3 comments
Open

Move Jira issues from Java.net #18

ralphlange opened this issue Jul 31, 2016 · 3 comments

Comments

@ralphlange
Copy link
Contributor

On 30/07/2016 01:37, Sarah Naugle wrote:

You are receiving this note because you are an administrator on at least one project hosted on Java.net or Kenai.com.

We will be closing both websites on April 28, 2017. You may request a tarball of your project assets and get instructions to download a copy of your bugs here: https://community.oracle.com/community/java/javanet-forge-sunset

What should we do with the 25 unresolved Jira issues on Java.net?

@shroffk
Copy link
Contributor

shroffk commented Aug 2, 2016

I will look into this in detail tomorrow
hope everything else is fine


From: Ralph Lange [[email protected]]
Sent: Sunday, July 31, 2016 10:48 AM
To: ChannelFinder/ChannelFinderService
Subject: [ChannelFinder/ChannelFinderService] Move Jira issues from Java.net (#18)

On 30/07/2016 01:37, Sarah Naugle wrote:

You are receiving this note because you are an administrator on at least one project hosted on Java.net or Kenai.com.

We will be closing both websites on April 28, 2017. You may request a tarball of your project assets and get instructions to download a copy of your bugs here: https://community.oracle.com/community/java/javanet-forge-sunset

What should we do with the 25 unresolved Jira issues on Java.net?


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/ChannelFinder/ChannelFinderService/issues/18, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ACA3SHcAYdZLEMXNOHEp6hgSIeV80uevks5qbLWkgaJpZM4JZC8m.

@ralphlange
Copy link
Contributor Author

There's no real hurry - we just have to move whatever is still useful, and close the rest. And rather do it sooner than later to consolidate.

@shroffk
Copy link
Contributor

shroffk commented Aug 2, 2016

I agree...
Also, now with 3 sites actively running the new ChannelFinder I feel more confident in calling it ready for production and make a new cleaned up release. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants