[[Hudson-Dev]] The Future of Hudson

All, Now that the fork has happened, we can start to put this saga
behind us and get back to work.  At this point we want to reassure you
that Hudson-ci continues and has our full commitment. We have a
dedicated team that includes people from Oracle, as well as some of our
partners and current Hudson community members who will continue to
build and grow the Hudson project and community.
 
Your current installations will continue to run fine, and you won't
need to change any code. You can still come to the newly designed
http://www.hudson-ci.org/ for all things Hudson. Later this week we
will announce a new release of Hudson. This release will primarily
de-couple the Hudson code from the old auto-update center back to the
official Hudson update center. If you use auto-update with version
1.395 or earlier, the auto-update will take you to a site that will ask
you to install jenkins which will remove your Hudson installation.  If
you want to continue to use Hudson, you should install Hudson v1.396 or
later when it becomes available later this week
 
We have reverted to using the Hudson mailing lists on java.net but are
open to discussion about creating a new google group.  In addition
java.net provides a forum that can be used to discuss user problems,
ideas and other issues. There is a link to get to that at the top of
the hudson-ci.org website.  I would urge you to engage with other
users.
 
Also as part of the fork, the Hudson github project has been taken
away. We have a current git repository on hudson.java.net where people
can continue to check things in. We can also discuss moving this back
to github once we get things settled.  If you are interested in getting
involved, and are not already registered as a committer, please let us
know.  This is your opportunity to help shape the future of Hudson.
 
Our primary goals over the next months will be to fix high-priority
bugs in the current edition of Hudson and formalize a development and
release process that will allow users of Hudson to have more insight
into what is being changed, why it is being changed, and when their
bugs will be fixed. We will also continue the discussion that Winston
started last month about what the next version of Hudson (v2) looks
like. I look forward to working closely with the community on where to
go from here.

regards

Susan

[Paul Jimenez]

unsubscribe

On 02/01/2011 12:20 PM, [hidden email] wrote:

> All, Now that the fork has happened, we can start to put this saga
> behind us and get back to work.  At this point we want to reassure you
> that Hudson-ci continues and has our full commitment. We have a
> dedicated team that includes people from Oracle, as well as some of our
> partners and current Hudson community members who will continue to
> build and grow the Hudson project and community.
>
> Your current installations will continue to run fine, and you won't
> need to change any code. You can still come to the newly designed
> http://www.hudson-ci.org/ for all things Hudson. Later this week we
> will announce a new release of Hudson. This release will primarily
> de-couple the Hudson code from the old auto-update center back to the
> official Hudson update center. If you use auto-update with version
> 1.395 or earlier, the auto-update will take you to a site that will ask
> you to install jenkins which will remove your Hudson installation.  If
> you want to continue to use Hudson, you should install Hudson v1.396 or
> later when it becomes available later this week
>
> We have reverted to using the Hudson mailing lists on java.net but are
> open to discussion about creating a new google group.  In addition
> java.net provides a forum that can be used to discuss user problems,
> ideas and other issues. There is a link to get to that at the top of
> the hudson-ci.org website.  I would urge you to engage with other
> users.
>
> Also as part of the fork, the Hudson github project has been taken
> away. We have a current git repository on hudson.java.net where people
> can continue to check things in. We can also discuss moving this back
> to github once we get things settled.  If you are interested in getting
> involved, and are not already registered as a committer, please let us
> know.  This is your opportunity to help shape the future of Hudson.
>
> Our primary goals over the next months will be to fix high-priority
> bugs in the current edition of Hudson and formalize a development and
> release process that will allow users of Hudson to have more insight
> into what is being changed, why it is being changed, and when their
> bugs will be fixed. We will also continue the discussion that Winston
> started last month about what the next version of Hudson (v2) looks
> like. I look forward to working closely with the community on where to
> go from here.
>
> regards
>
> Susan
>

[darbour]

unsubscribe

On Tue, Feb 1, 2011 at 2:06 PM, Paul Jimenez <[hidden email]> wrote:

unsubscribe

On 02/01/2011 12:20 PM, [hidden email] wrote:

All, Now that the fork has happened, we can start to put this saga
behind us and get back to work.  At this point we want to reassure you
that Hudson-ci continues and has our full commitment. We have a
dedicated team that includes people from Oracle, as well as some of our
partners and current Hudson community members who will continue to
build and grow the Hudson project and community.

Your current installations will continue to run fine, and you won't
need to change any code. You can still come to the newly designed
http://www.hudson-ci.org/ for all things Hudson. Later this week we
will announce a new release of Hudson. This release will primarily
de-couple the Hudson code from the old auto-update center back to the
official Hudson update center.  If you use auto-update with version
1.395 or earlier, the auto-update will take you to a site that will ask
you to install jenkins which will remove your Hudson installation.  If
you want to continue to use Hudson, you should install Hudson v1.396 or
later when it becomes available later this week

We have reverted to using the Hudson mailing lists on java.net but are
open to discussion about creating a new google group.  In addition
java.net provides a forum that can be used to discuss user problems,
ideas and other issues. There is a link to get to that at the top of
the hudson-ci.org website.  I would urge you to engage with other
users.

Also as part of the fork, the Hudson github project has been taken
away. We have a current git repository on hudson.java.net where people
can continue to check things in. We can also discuss moving this back
to github once we get things settled.  If you are interested in getting
involved, and are not already registered as a committer, please let us
know.  This is your opportunity to help shape the future of Hudson.

Our primary goals over the next months will be to fix high-priority
bugs in the current edition of Hudson and formalize a development and
release process that will allow users of Hudson to have more insight
into what is being changed, why it is being changed, and when their
bugs will be fixed. We will also continue the discussion that Winston
started last month about what the next version of Hudson (v2) looks
like. I look forward to working closely with the community on where to
go from here.

regards

Susan

[Bogdan Iosif]

unsubscribe

On Tue, Feb 1, 2011 at 20:20, <[hidden email]> wrote:

All, Now that the fork has happened, we can start to put this saga
behind us and get back to work.  At this point we want to reassure you
that Hudson-ci continues and has our full commitment. We have a
dedicated team that includes people from Oracle, as well as some of our
partners and current Hudson community members who will continue to
build and grow the Hudson project and community.

Your current installations will continue to run fine, and you won't
need to change any code. You can still come to the newly designed
http://www.hudson-ci.org/ for all things Hudson. Later this week we
will announce a new release of Hudson. This release will primarily
de-couple the Hudson code from the old auto-update center back to the
official Hudson update center.  If you use auto-update with version
1.395 or earlier, the auto-update will take you to a site that will ask
you to install jenkins which will remove your Hudson installation.  If
you want to continue to use Hudson, you should install Hudson v1.396 or
later when it becomes available later this week

We have reverted to using the Hudson mailing lists on java.net but are
open to discussion about creating a new google group.  In addition
java.net provides a forum that can be used to discuss user problems,
ideas and other issues. There is a link to get to that at the top of
the hudson-ci.org website.  I would urge you to engage with other
users.

Also as part of the fork, the Hudson github project has been taken
away. We have a current git repository on hudson.java.net where people
can continue to check things in. We can also discuss moving this back
to github once we get things settled.  If you are interested in getting
involved, and are not already registered as a committer, please let us
know.  This is your opportunity to help shape the future of Hudson.

Our primary goals over the next months will be to fix high-priority
bugs in the current edition of Hudson and formalize a development and
release process that will allow users of Hudson to have more insight
into what is being changed, why it is being changed, and when their
bugs will be fixed. We will also continue the discussion that Winston
started last month about what the next version of Hudson (v2) looks
like. I look forward to working closely with the community on where to
go from here.

regards

Susan

[stephenconnolly]

unsubscribe

On 1 February 2011 18:20,  <[hidden email]> wrote:

> All, Now that the fork has happened, we can start to put this saga
> behind us and get back to work.  At this point we want to reassure you
> that Hudson-ci continues and has our full commitment. We have a
> dedicated team that includes people from Oracle, as well as some of our
> partners and current Hudson community members who will continue to
> build and grow the Hudson project and community.
>
> Your current installations will continue to run fine, and you won't
> need to change any code. You can still come to the newly designed
> http://www.hudson-ci.org/ for all things Hudson. Later this week we
> will announce a new release of Hudson. This release will primarily
> de-couple the Hudson code from the old auto-update center back to the
> official Hudson update center.  If you use auto-update with version
> 1.395 or earlier, the auto-update will take you to a site that will ask
> you to install jenkins which will remove your Hudson installation.  If
> you want to continue to use Hudson, you should install Hudson v1.396 or
> later when it becomes available later this week
>
> We have reverted to using the Hudson mailing lists on java.net but are
> open to discussion about creating a new google group.  In addition
> java.net provides a forum that can be used to discuss user problems,
> ideas and other issues. There is a link to get to that at the top of
> the hudson-ci.org website.  I would urge you to engage with other
> users.
>
> Also as part of the fork, the Hudson github project has been taken
> away. We have a current git repository on hudson.java.net where people
> can continue to check things in. We can also discuss moving this back
> to github once we get things settled.  If you are interested in getting
> involved, and are not already registered as a committer, please let us
> know.  This is your opportunity to help shape the future of Hudson.
>
> Our primary goals over the next months will be to fix high-priority
> bugs in the current edition of Hudson and formalize a development and
> release process that will allow users of Hudson to have more insight
> into what is being changed, why it is being changed, and when their
> bugs will be fixed. We will also continue the discussion that Winston
> started last month about what the next version of Hudson (v2) looks
> like. I look forward to working closely with the community on where to
> go from here.
>
> regards
>
> Susan
>

[Brian Bouterse]

unsubscribe

On Tue, Feb 1, 2011 at 2:22 PM, Stephen Connolly <[hidden email]> wrote:

unsubscribe

On 1 February 2011 18:20,  <[hidden email]> wrote:
> All, Now that the fork has happened, we can start to put this saga
> behind us and get back to work.  At this point we want to reassure you
> that Hudson-ci continues and has our full commitment. We have a
> dedicated team that includes people from Oracle, as well as some of our
> partners and current Hudson community members who will continue to
> build and grow the Hudson project and community.
>
> Your current installations will continue to run fine, and you won't
> need to change any code. You can still come to the newly designed
> http://www.hudson-ci.org/ for all things Hudson. Later this week we
> will announce a new release of Hudson. This release will primarily
> de-couple the Hudson code from the old auto-update center back to the
> official Hudson update center.  If you use auto-update with version
> 1.395 or earlier, the auto-update will take you to a site that will ask
> you to install jenkins which will remove your Hudson installation.  If
> you want to continue to use Hudson, you should install Hudson v1.396 or
> later when it becomes available later this week
>
> We have reverted to using the Hudson mailing lists on java.net but are
> open to discussion about creating a new google group.  In addition
> java.net provides a forum that can be used to discuss user problems,
> ideas and other issues. There is a link to get to that at the top of
> the hudson-ci.org website.  I would urge you to engage with other
> users.
>
> Also as part of the fork, the Hudson github project has been taken
> away. We have a current git repository on hudson.java.net where people
> can continue to check things in. We can also discuss moving this back
> to github once we get things settled.  If you are interested in getting
> involved, and are not already registered as a committer, please let us
> know.  This is your opportunity to help shape the future of Hudson.
>
> Our primary goals over the next months will be to fix high-priority
> bugs in the current edition of Hudson and formalize a development and
> release process that will allow users of Hudson to have more insight
> into what is being changed, why it is being changed, and when their
> bugs will be fixed. We will also continue the discussion that Winston
> started last month about what the next version of Hudson (v2) looks
> like. I look forward to working closely with the community on where to
> go from here.
>
> regards
>
> Susan
>

--
Brian Bouterse
ITng Services

[Romain PELISSE]

unsubscribe

On 1 February 2011 20:31, Brian Bouterse <[hidden email]> wrote:

unsubscribe

On Tue, Feb 1, 2011 at 2:22 PM, Stephen Connolly <[hidden email]> wrote:

unsubscribe

On 1 February 2011 18:20,  <[hidden email]> wrote:
> All, Now that the fork has happened, we can start to put this saga
> behind us and get back to work.  At this point we want to reassure you
> that Hudson-ci continues and has our full commitment. We have a
> dedicated team that includes people from Oracle, as well as some of our
> partners and current Hudson community members who will continue to
> build and grow the Hudson project and community.
>
> Your current installations will continue to run fine, and you won't
> need to change any code. You can still come to the newly designed
> http://www.hudson-ci.org/ for all things Hudson. Later this week we
> will announce a new release of Hudson. This release will primarily
> de-couple the Hudson code from the old auto-update center back to the
> official Hudson update center.  If you use auto-update with version
> 1.395 or earlier, the auto-update will take you to a site that will ask
> you to install jenkins which will remove your Hudson installation.  If
> you want to continue to use Hudson, you should install Hudson v1.396 or
> later when it becomes available later this week
>
> We have reverted to using the Hudson mailing lists on java.net but are
> open to discussion about creating a new google group.  In addition
> java.net provides a forum that can be used to discuss user problems,
> ideas and other issues. There is a link to get to that at the top of
> the hudson-ci.org website.  I would urge you to engage with other
> users.
>
> Also as part of the fork, the Hudson github project has been taken
> away. We have a current git repository on hudson.java.net where people
> can continue to check things in. We can also discuss moving this back
> to github once we get things settled.  If you are interested in getting
> involved, and are not already registered as a committer, please let us
> know.  This is your opportunity to help shape the future of Hudson.
>
> Our primary goals over the next months will be to fix high-priority
> bugs in the current edition of Hudson and formalize a development and
> release process that will allow users of Hudson to have more insight
> into what is being changed, why it is being changed, and when their
> bugs will be fixed. We will also continue the discussion that Winston
> started last month about what the next version of Hudson (v2) looks
> like. I look forward to working closely with the community on where to
> go from here.
>
> regards
>
> Susan
>

--
Brian Bouterse
ITng Services

--
Romain PELISSE,
"The trouble with having an open mind, of course, is that people will insist on coming along and trying to put things in it" -- Terry Pratchett
http://belaran.eu/wordpress/belaran

[Sankaran, Nambi]

Don’t spam other.

 

From: Romain Pelisse [mailto:[hidden email]]
Sent: Tuesday, February 01, 2011 11:38 AM
To: Brian Bouterse
Cc: Stephen Connolly; [hidden email]; [hidden email]; [hidden email]
Subject: [Hudson-Dev] Re: [] The Future of Hudson

 

unsubscribe

On 1 February 2011 20:31, Brian Bouterse <[hidden email]> wrote:

unsubscribe

 

On Tue, Feb 1, 2011 at 2:22 PM, Stephen Connolly <[hidden email]> wrote:

unsubscribe

On 1 February 2011 18:20,  <[hidden email]> wrote:
> All, Now that the fork has happened, we can start to put this saga
> behind us and get back to work.  At this point we want to reassure you
> that Hudson-ci continues and has our full commitment. We have a
> dedicated team that includes people from Oracle, as well as some of our
> partners and current Hudson community members who will continue to
> build and grow the Hudson project and community.
>
> Your current installations will continue to run fine, and you won't
> need to change any code. You can still come to the newly designed
> http://www.hudson-ci.org/ for all things Hudson. Later this week we
> will announce a new release of Hudson. This release will primarily
> de-couple the Hudson code from the old auto-update center back to the
> official Hudson update center.  If you use auto-update with version
> 1.395 or earlier, the auto-update will take you to a site that will ask
> you to install jenkins which will remove your Hudson installation.  If
> you want to continue to use Hudson, you should install Hudson v1.396 or
> later when it becomes available later this week
>
> We have reverted to using the Hudson mailing lists on java.net but are
> open to discussion about creating a new google group.  In addition
> java.net provides a forum that can be used to discuss user problems,
> ideas and other issues. There is a link to get to that at the top of
> the hudson-ci.org website.  I would urge you to engage with other
> users.
>
> Also as part of the fork, the Hudson github project has been taken
> away. We have a current git repository on hudson.java.net where people
> can continue to check things in. We can also discuss moving this back
> to github once we get things settled.  If you are interested in getting
> involved, and are not already registered as a committer, please let us
> know.  This is your opportunity to help shape the future of Hudson.
>
> Our primary goals over the next months will be to fix high-priority
> bugs in the current edition of Hudson and formalize a development and
> release process that will allow users of Hudson to have more insight
> into what is being changed, why it is being changed, and when their
> bugs will be fixed. We will also continue the discussion that Winston
> started last month about what the next version of Hudson (v2) looks
> like. I look forward to working closely with the community on where to
> go from here.
>
> regards
>
> Susan
>

--
Brian Bouterse
ITng Services

--
Romain PELISSE,
"The trouble with having an open mind, of course, is that people will insist on coming along and trying to put things in it" -- Terry Pratchett
http://belaran.eu/wordpress/belaran

[emanuele.zattin]

unsubscribe
________________________________________
From: ext Sankaran, Nambi [[hidden email]]
Sent: Tuesday, February 01, 2011 8:40 PM
To: Romain Pelisse; Brian Bouterse
Cc: Stephen Connolly; [hidden email]; [hidden email]; [hidden email]
Subject: [Hudson-Dev] Re: [] The Future of Hudson

Don’t spam other.

From: Romain Pelisse [mailto:[hidden email]]
Sent: Tuesday, February 01, 2011 11:38 AM
To: Brian Bouterse
Cc: Stephen Connolly; [hidden email]; [hidden email]; [hidden email]
Subject: [Hudson-Dev] Re: [] The Future of Hudson

unsubscribe
On 1 February 2011 20:31, Brian Bouterse <[hidden email]<mailto:[hidden email]>> wrote:
unsubscribe

On Tue, Feb 1, 2011 at 2:22 PM, Stephen Connolly <[hidden email]<mailto:[hidden email]>> wrote:
unsubscribe

On 1 February 2011 18:20,  <[hidden email]<mailto:[hidden email]>> wrote:

> All, Now that the fork has happened, we can start to put this saga
> behind us and get back to work.  At this point we want to reassure you
> that Hudson-ci continues and has our full commitment. We have a
> dedicated team that includes people from Oracle, as well as some of our
> partners and current Hudson community members who will continue to
> build and grow the Hudson project and community.
>
> Your current installations will continue to run fine, and you won't
> need to change any code. You can still come to the newly designed
> http://www.hudson-ci.org/ for all things Hudson. Later this week we
> will announce a new release of Hudson. This release will primarily
> de-couple the Hudson code from the old auto-update center back to the
> official Hudson update center.  If you use auto-update with version
> 1.395 or earlier, the auto-update will take you to a site that will ask
> you to install jenkins which will remove your Hudson installation.  If
> you want to continue to use Hudson, you should install Hudson v1.396 or
> later when it becomes available later this week
>
> We have reverted to using the Hudson mailing lists on java.net<http://java.net> but are
> open to discussion about creating a new google group.  In addition
> java.net<http://java.net> provides a forum that can be used to discuss user problems,
> ideas and other issues. There is a link to get to that at the top of
> the hudson-ci.org<http://hudson-ci.org> website.  I would urge you to engage with other
> users.
>
> Also as part of the fork, the Hudson github project has been taken
> away. We have a current git repository on hudson.java.net<http://hudson.java.net> where people
> can continue to check things in. We can also discuss moving this back
> to github once we get things settled.  If you are interested in getting
> involved, and are not already registered as a committer, please let us
> know.  This is your opportunity to help shape the future of Hudson.
>
> Our primary goals over the next months will be to fix high-priority
> bugs in the current edition of Hudson and formalize a development and
> release process that will allow users of Hudson to have more insight
> into what is being changed, why it is being changed, and when their
> bugs will be fixed. We will also continue the discussion that Winston
> started last month about what the next version of Hudson (v2) looks
> like. I look forward to working closely with the community on where to
> go from here.
>
> regards
>
> Susan
>

--
Brian Bouterse
ITng Services



--
Romain PELISSE,
"The trouble with having an open mind, of course, is that people will insist on coming along and trying to put things in it" -- Terry Pratchett
http://belaran.eu/wordpress/belaran

[heimojuh]

unsubscribe

On Tue, Feb 1, 2011 at 9:49 PM,  <[hidden email]> wrote:

> unsubscribe
> ________________________________________
> From: ext Sankaran, Nambi [[hidden email]]
> Sent: Tuesday, February 01, 2011 8:40 PM
> To: Romain Pelisse; Brian Bouterse
> Cc: Stephen Connolly; [hidden email]; [hidden email]; [hidden email]
> Subject: [Hudson-Dev] Re: [] The Future of Hudson
>
> Don’t spam other.
>
> From: Romain Pelisse [mailto:[hidden email]]
> Sent: Tuesday, February 01, 2011 11:38 AM
> To: Brian Bouterse
> Cc: Stephen Connolly; [hidden email]; [hidden email]; [hidden email]
> Subject: [Hudson-Dev] Re: [] The Future of Hudson
>
> unsubscribe
> On 1 February 2011 20:31, Brian Bouterse <[hidden email]<mailto:[hidden email]>> wrote:
> unsubscribe
>
> On Tue, Feb 1, 2011 at 2:22 PM, Stephen Connolly <[hidden email]<mailto:[hidden email]>> wrote:
> unsubscribe
>
> On 1 February 2011 18:20,  <[hidden email]<mailto:[hidden email]>> wrote:
>> All, Now that the fork has happened, we can start to put this saga
>> behind us and get back to work.  At this point we want to reassure you
>> that Hudson-ci continues and has our full commitment. We have a
>> dedicated team that includes people from Oracle, as well as some of our
>> partners and current Hudson community members who will continue to
>> build and grow the Hudson project and community.
>>
>> Your current installations will continue to run fine, and you won't
>> need to change any code. You can still come to the newly designed
>> http://www.hudson-ci.org/ for all things Hudson. Later this week we
>> will announce a new release of Hudson. This release will primarily
>> de-couple the Hudson code from the old auto-update center back to the
>> official Hudson update center.  If you use auto-update with version
>> 1.395 or earlier, the auto-update will take you to a site that will ask
>> you to install jenkins which will remove your Hudson installation.  If
>> you want to continue to use Hudson, you should install Hudson v1.396 or
>> later when it becomes available later this week
>>
>> We have reverted to using the Hudson mailing lists on java.net<http://java.net> but are
>> open to discussion about creating a new google group.  In addition
>> java.net<http://java.net> provides a forum that can be used to discuss user problems,
>> ideas and other issues. There is a link to get to that at the top of
>> the hudson-ci.org<http://hudson-ci.org> website.  I would urge you to engage with other
>> users.
>>
>> Also as part of the fork, the Hudson github project has been taken
>> away. We have a current git repository on hudson.java.net<http://hudson.java.net> where people
>> can continue to check things in. We can also discuss moving this back
>> to github once we get things settled.  If you are interested in getting
>> involved, and are not already registered as a committer, please let us
>> know.  This is your opportunity to help shape the future of Hudson.
>>
>> Our primary goals over the next months will be to fix high-priority
>> bugs in the current edition of Hudson and formalize a development and
>> release process that will allow users of Hudson to have more insight
>> into what is being changed, why it is being changed, and when their
>> bugs will be fixed. We will also continue the discussion that Winston
>> started last month about what the next version of Hudson (v2) looks
>> like. I look forward to working closely with the community on where to
>> go from here.
>>
>> regards
>>
>> Susan
>>
>
>
> --
> Brian Bouterse
> ITng Services
>
>
>
> --
> Romain PELISSE,
> "The trouble with having an open mind, of course, is that people will insist on coming along and trying to put things in it" -- Terry Pratchett
> http://belaran.eu/wordpress/belaran
>

[Eirik Bjørsnøs]

unsubscribe

No, seriously: How do I get off this list?

The headers seem to indicate that an email to [hidden email]
with a subject of "unsubscribe-dev" should do the trick, but sympa
replies that it finds no command.

Is this Oracle's way of building a "community"? Creating email lists
that people can't unsubscribe from?

Eirik.


On Tue, Feb 1, 2011 at 7:20 PM,  <[hidden email]> wrote:

> All, Now that the fork has happened, we can start to put this saga
> behind us and get back to work.  At this point we want to reassure you
> that Hudson-ci continues and has our full commitment. We have a
> dedicated team that includes people from Oracle, as well as some of our
> partners and current Hudson community members who will continue to
> build and grow the Hudson project and community.
>
> Your current installations will continue to run fine, and you won't
> need to change any code. You can still come to the newly designed
> http://www.hudson-ci.org/ for all things Hudson. Later this week we
> will announce a new release of Hudson. This release will primarily
> de-couple the Hudson code from the old auto-update center back to the
> official Hudson update center.  If you use auto-update with version
> 1.395 or earlier, the auto-update will take you to a site that will ask
> you to install jenkins which will remove your Hudson installation.  If
> you want to continue to use Hudson, you should install Hudson v1.396 or
> later when it becomes available later this week
>
> We have reverted to using the Hudson mailing lists on java.net but are
> open to discussion about creating a new google group.  In addition
> java.net provides a forum that can be used to discuss user problems,
> ideas and other issues. There is a link to get to that at the top of
> the hudson-ci.org website.  I would urge you to engage with other
> users.
>
> Also as part of the fork, the Hudson github project has been taken
> away. We have a current git repository on hudson.java.net where people
> can continue to check things in. We can also discuss moving this back
> to github once we get things settled.  If you are interested in getting
> involved, and are not already registered as a committer, please let us
> know.  This is your opportunity to help shape the future of Hudson.
>
> Our primary goals over the next months will be to fix high-priority
> bugs in the current edition of Hudson and formalize a development and
> release process that will allow users of Hudson to have more insight
> into what is being changed, why it is being changed, and when their
> bugs will be fixed. We will also continue the discussion that Winston
> started last month about what the next version of Hudson (v2) looks
> like. I look forward to working closely with the community on where to
> go from here.
>
> regards
>
> Susan
>

[Renaud Lepage]

Send an email to [hidden email]

subject: "unsubscribe *", no quotes
no content.

and follow the instructions.


Sorry Susan!

-RL

2011/2/1 Eirik Bjørsnøs <[hidden email]>

unsubscribe

No, seriously: How do I get off this list?

The headers seem to indicate that an email to [hidden email]
with a subject of "unsubscribe-dev" should do the trick, but sympa
replies that it finds no command.

Is this Oracle's way of building a "community"? Creating email lists
that people can't unsubscribe from?

Eirik.

On Tue, Feb 1, 2011 at 7:20 PM,  <[hidden email]> wrote:
> All, Now that the fork has happened, we can start to put this saga
> behind us and get back to work.  At this point we want to reassure you
> that Hudson-ci continues and has our full commitment. We have a
> dedicated team that includes people from Oracle, as well as some of our
> partners and current Hudson community members who will continue to
> build and grow the Hudson project and community.
>
> Your current installations will continue to run fine, and you won't
> need to change any code. You can still come to the newly designed
> http://www.hudson-ci.org/ for all things Hudson. Later this week we
> will announce a new release of Hudson. This release will primarily
> de-couple the Hudson code from the old auto-update center back to the
> official Hudson update center.  If you use auto-update with version
> 1.395 or earlier, the auto-update will take you to a site that will ask
> you to install jenkins which will remove your Hudson installation.  If
> you want to continue to use Hudson, you should install Hudson v1.396 or
> later when it becomes available later this week
>
> We have reverted to using the Hudson mailing lists on java.net but are
> open to discussion about creating a new google group.  In addition
> java.net provides a forum that can be used to discuss user problems,
> ideas and other issues. There is a link to get to that at the top of
> the hudson-ci.org website.  I would urge you to engage with other
> users.
>
> Also as part of the fork, the Hudson github project has been taken
> away. We have a current git repository on hudson.java.net where people
> can continue to check things in. We can also discuss moving this back
> to github once we get things settled.  If you are interested in getting
> involved, and are not already registered as a committer, please let us
> know.  This is your opportunity to help shape the future of Hudson.
>
> Our primary goals over the next months will be to fix high-priority
> bugs in the current edition of Hudson and formalize a development and
> release process that will allow users of Hudson to have more insight
> into what is being changed, why it is being changed, and when their
> bugs will be fixed. We will also continue the discussion that Winston
> started last month about what the next version of Hudson (v2) looks
> like. I look forward to working closely with the community on where to
> go from here.
>
> regards
>
> Susan
>

[Trojan, Krzysztof]

What I am surprised is that Oracle was given ownership of the project. I have not paid attention to the list for some time now, but as far as I remember the latest approach on this by some Oracle employee had rather cold welcome.

For me it looks like a highjack, not a fork ;)
But it seems Kohsuke gave it his blessing, and I respect his opinion here.

Regards,
Chris

-----Original Message-----
From: Eirik Bjørsnøs [mailto:[hidden email]]
Sent: Tuesday, February 01, 2011 9:07 PM
To: [hidden email]
Cc: [hidden email]
Subject: [Hudson-Dev] Re: [] The Future of Hudson

unsubscribe

No, seriously: How do I get off this list?

The headers seem to indicate that an email to [hidden email]
with a subject of "unsubscribe-dev" should do the trick, but sympa
replies that it finds no command.

Is this Oracle's way of building a "community"? Creating email lists
that people can't unsubscribe from?

Eirik.


On Tue, Feb 1, 2011 at 7:20 PM,  <[hidden email]> wrote:

> All, Now that the fork has happened, we can start to put this saga
> behind us and get back to work.  At this point we want to reassure you
> that Hudson-ci continues and has our full commitment. We have a
> dedicated team that includes people from Oracle, as well as some of our
> partners and current Hudson community members who will continue to
> build and grow the Hudson project and community.
>
> Your current installations will continue to run fine, and you won't
> need to change any code. You can still come to the newly designed
> http://www.hudson-ci.org/ for all things Hudson. Later this week we
> will announce a new release of Hudson. This release will primarily
> de-couple the Hudson code from the old auto-update center back to the
> official Hudson update center.  If you use auto-update with version
> 1.395 or earlier, the auto-update will take you to a site that will ask
> you to install jenkins which will remove your Hudson installation.  If
> you want to continue to use Hudson, you should install Hudson v1.396 or
> later when it becomes available later this week
>
> We have reverted to using the Hudson mailing lists on java.net but are
> open to discussion about creating a new google group.  In addition
> java.net provides a forum that can be used to discuss user problems,
> ideas and other issues. There is a link to get to that at the top of
> the hudson-ci.org website.  I would urge you to engage with other
> users.
>
> Also as part of the fork, the Hudson github project has been taken
> away. We have a current git repository on hudson.java.net where people
> can continue to check things in. We can also discuss moving this back
> to github once we get things settled.  If you are interested in getting
> involved, and are not already registered as a committer, please let us
> know.  This is your opportunity to help shape the future of Hudson.
>
> Our primary goals over the next months will be to fix high-priority
> bugs in the current edition of Hudson and formalize a development and
> release process that will allow users of Hudson to have more insight
> into what is being changed, why it is being changed, and when their
> bugs will be fixed. We will also continue the discussion that Winston
> started last month about what the next version of Hudson (v2) looks
> like. I look forward to working closely with the community on where to
> go from here.
>
> regards
>
> Susan
>

_____________

The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.
_____________

[Krzysztof Baranski]

On 01.02.2011 21:07, Eirik Bjørsnøs wrote:

> unsubscribe
>
> No, seriously: How do I get off this list?
>
> The headers seem to indicate that an email to [hidden email]
> with a subject of "unsubscribe-dev" should do the trick, but sympa
> replies that it finds no command.
>
> Is this Oracle's way of building a "community"? Creating email lists
> that people can't unsubscribe from?
>
> Eirik.

According to
http://java.net/nonav/projects/hudson/sources/svn/content/trunk/www/mailing-lists.html?rev=38326 
you should send email to

[hidden email]
[hidden email]

Regards,
Krzysztof

[Eirik Bjørsnøs]

Turns out Oracle actually does provide a UI for unsubscribing from
java.net mailing lists. Please accept my sincere apologies for
indicating otherwise. Actually, with this UI, unsubscribing is
temptingly easy and actually a quite pleasant user experience:

o Go to: http://java.net/projects/hudson/lists
o Click "Login", enter your java.net credentials
o Select the "Subscriptions" tab
o Find the big fat button called "Unsubscribe" under the dev@hudson list.
o Click the button
o Give yourself a treat

Thanks, but no thanks.
Eirik.


2011/2/1 Eirik Bjørsnøs <[hidden email]>:

> unsubscribe
>
> No, seriously: How do I get off this list?
>
> The headers seem to indicate that an email to [hidden email]
> with a subject of "unsubscribe-dev" should do the trick, but sympa
> replies that it finds no command.
>
> Is this Oracle's way of building a "community"? Creating email lists
> that people can't unsubscribe from?
>
> Eirik.
>
>
> On Tue, Feb 1, 2011 at 7:20 PM,  <[hidden email]> wrote:
>> All, Now that the fork has happened, we can start to put this saga
>> behind us and get back to work.  At this point we want to reassure you
>> that Hudson-ci continues and has our full commitment. We have a
>> dedicated team that includes people from Oracle, as well as some of our
>> partners and current Hudson community members who will continue to
>> build and grow the Hudson project and community.
>>
>> Your current installations will continue to run fine, and you won't
>> need to change any code. You can still come to the newly designed
>> http://www.hudson-ci.org/ for all things Hudson. Later this week we
>> will announce a new release of Hudson. This release will primarily
>> de-couple the Hudson code from the old auto-update center back to the
>> official Hudson update center.  If you use auto-update with version
>> 1.395 or earlier, the auto-update will take you to a site that will ask
>> you to install jenkins which will remove your Hudson installation.  If
>> you want to continue to use Hudson, you should install Hudson v1.396 or
>> later when it becomes available later this week
>>
>> We have reverted to using the Hudson mailing lists on java.net but are
>> open to discussion about creating a new google group.  In addition
>> java.net provides a forum that can be used to discuss user problems,
>> ideas and other issues. There is a link to get to that at the top of
>> the hudson-ci.org website.  I would urge you to engage with other
>> users.
>>
>> Also as part of the fork, the Hudson github project has been taken
>> away. We have a current git repository on hudson.java.net where people
>> can continue to check things in. We can also discuss moving this back
>> to github once we get things settled.  If you are interested in getting
>> involved, and are not already registered as a committer, please let us
>> know.  This is your opportunity to help shape the future of Hudson.
>>
>> Our primary goals over the next months will be to fix high-priority
>> bugs in the current edition of Hudson and formalize a development and
>> release process that will allow users of Hudson to have more insight
>> into what is being changed, why it is being changed, and when their
>> bugs will be fixed. We will also continue the discussion that Winston
>> started last month about what the next version of Hudson (v2) looks
>> like. I look forward to working closely with the community on where to
>> go from here.
>>
>> regards
>>
>> Susan
>>
>

[Kohsuke Kawaguchi]

No, I didn't hand over the project to Oracle. They feel they are
entitled to it, and I was simply removed from the project.

2011/2/1 Trojan, Krzysztof <[hidden email]>:

> What I am surprised is that Oracle was given ownership of the project.
> I have not paid attention to the list for some time now, but as far as
> I remember the latest approach on this by some Oracle employee
> had rather cold welcome.
>
> For me it looks like a highjack, not a fork ;)
> But it seems Kohsuke gave it his blessing, and I respect his opinion here.
>
> Regards,
> Chris
>
> -----Original Message-----
> From: Eirik Bjørsnøs [mailto:[hidden email]]
> Sent: Tuesday, February 01, 2011 9:07 PM
> To: [hidden email]
> Cc: [hidden email]
> Subject: [Hudson-Dev] Re: [] The Future of Hudson
>
> unsubscribe
>
> No, seriously: How do I get off this list?
>
> The headers seem to indicate that an email to [hidden email]
> with a subject of "unsubscribe-dev" should do the trick, but sympa
> replies that it finds no command.
>
> Is this Oracle's way of building a "community"? Creating email lists
> that people can't unsubscribe from?
>
> Eirik.
>
>
> On Tue, Feb 1, 2011 at 7:20 PM,  <[hidden email]> wrote:
>> All, Now that the fork has happened, we can start to put this saga
>> behind us and get back to work.  At this point we want to reassure you
>> that Hudson-ci continues and has our full commitment. We have a
>> dedicated team that includes people from Oracle, as well as some of our
>> partners and current Hudson community members who will continue to
>> build and grow the Hudson project and community.
>>
>> Your current installations will continue to run fine, and you won't
>> need to change any code. You can still come to the newly designed
>> http://www.hudson-ci.org/ for all things Hudson. Later this week we
>> will announce a new release of Hudson. This release will primarily
>> de-couple the Hudson code from the old auto-update center back to the
>> official Hudson update center.  If you use auto-update with version
>> 1.395 or earlier, the auto-update will take you to a site that will ask
>> you to install jenkins which will remove your Hudson installation.  If
>> you want to continue to use Hudson, you should install Hudson v1.396 or
>> later when it becomes available later this week
>>
>> We have reverted to using the Hudson mailing lists on java.net but are
>> open to discussion about creating a new google group.  In addition
>> java.net provides a forum that can be used to discuss user problems,
>> ideas and other issues. There is a link to get to that at the top of
>> the hudson-ci.org website.  I would urge you to engage with other
>> users.
>>
>> Also as part of the fork, the Hudson github project has been taken
>> away. We have a current git repository on hudson.java.net where people
>> can continue to check things in. We can also discuss moving this back
>> to github once we get things settled.  If you are interested in getting
>> involved, and are not already registered as a committer, please let us
>> know.  This is your opportunity to help shape the future of Hudson.
>>
>> Our primary goals over the next months will be to fix high-priority
>> bugs in the current edition of Hudson and formalize a development and
>> release process that will allow users of Hudson to have more insight
>> into what is being changed, why it is being changed, and when their
>> bugs will be fixed. We will also continue the discussion that Winston
>> started last month about what the next version of Hudson (v2) looks
>> like. I look forward to working closely with the community on where to
>> go from here.
>>
>> regards
>>
>> Susan
>>
>
> _____________
>
> The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.
> _____________
>

--
Kohsuke Kawaguchi

[Trojan, Krzysztof]

Hi,

So additionally to highjacking the project they also claim (or "suggest") to have your consent:

On the new Hudson-ci.org one can read:
"Many of you may be aware that Andrew Bayer and Cloudbees (where Kohsuke Kawaguchi now works) have confirmed their intent to fork Hudson into a new community. We want the Hudson community to know that we have a dedicated team that includes people from Oracle, as well as some of our partners and current Hudson community members who will continue to build and grow the Hudson project and community. Your current installations will continue to run fine, and you won't need to change any code. You can still come to http://www.hudson-ci.org/ for all things Hudson."

Don't know if you work Cloudbees ... but it does not necessarily mean you gave the project away to them.

Let's see what will come out of this mess ... the Hudson was usable before Oracle overtook it, we can always think about a fork ;)

But still I don't think I understand how one, especially a person of your level of recognition, can be "removed" from any open source project.

Kind regards,
Chris

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Kohsuke Kawaguchi
Sent: Tuesday, February 01, 2011 9:38 PM
To: Trojan, Krzysztof
Cc: [hidden email]
Subject: Re: [Hudson-Dev] Re: [] The Future of Hudson

No, I didn't hand over the project to Oracle. They feel they are
entitled to it, and I was simply removed from the project.

2011/2/1 Trojan, Krzysztof <[hidden email]>:

> What I am surprised is that Oracle was given ownership of the project.
> I have not paid attention to the list for some time now, but as far as
> I remember the latest approach on this by some Oracle employee
> had rather cold welcome.
>
> For me it looks like a highjack, not a fork ;)
> But it seems Kohsuke gave it his blessing, and I respect his opinion here.
>
> Regards,
> Chris
>
> -----Original Message-----
> From: Eirik Bjørsnøs [mailto:[hidden email]]
> Sent: Tuesday, February 01, 2011 9:07 PM
> To: [hidden email]
> Cc: [hidden email]
> Subject: [Hudson-Dev] Re: [] The Future of Hudson
>
> unsubscribe
>
> No, seriously: How do I get off this list?
>
> The headers seem to indicate that an email to [hidden email]
> with a subject of "unsubscribe-dev" should do the trick, but sympa
> replies that it finds no command.
>
> Is this Oracle's way of building a "community"? Creating email lists
> that people can't unsubscribe from?
>
> Eirik.
>
>
> On Tue, Feb 1, 2011 at 7:20 PM,  <[hidden email]> wrote:
>> All, Now that the fork has happened, we can start to put this saga
>> behind us and get back to work.  At this point we want to reassure you
>> that Hudson-ci continues and has our full commitment. We have a
>> dedicated team that includes people from Oracle, as well as some of our
>> partners and current Hudson community members who will continue to
>> build and grow the Hudson project and community.
>>
>> Your current installations will continue to run fine, and you won't
>> need to change any code. You can still come to the newly designed
>> http://www.hudson-ci.org/ for all things Hudson. Later this week we
>> will announce a new release of Hudson. This release will primarily
>> de-couple the Hudson code from the old auto-update center back to the
>> official Hudson update center.  If you use auto-update with version
>> 1.395 or earlier, the auto-update will take you to a site that will ask
>> you to install jenkins which will remove your Hudson installation.  If
>> you want to continue to use Hudson, you should install Hudson v1.396 or
>> later when it becomes available later this week
>>
>> We have reverted to using the Hudson mailing lists on java.net but are
>> open to discussion about creating a new google group.  In addition
>> java.net provides a forum that can be used to discuss user problems,
>> ideas and other issues. There is a link to get to that at the top of
>> the hudson-ci.org website.  I would urge you to engage with other
>> users.
>>
>> Also as part of the fork, the Hudson github project has been taken
>> away. We have a current git repository on hudson.java.net where people
>> can continue to check things in. We can also discuss moving this back
>> to github once we get things settled.  If you are interested in getting
>> involved, and are not already registered as a committer, please let us
>> know.  This is your opportunity to help shape the future of Hudson.
>>
>> Our primary goals over the next months will be to fix high-priority
>> bugs in the current edition of Hudson and formalize a development and
>> release process that will allow users of Hudson to have more insight
>> into what is being changed, why it is being changed, and when their
>> bugs will be fixed. We will also continue the discussion that Winston
>> started last month about what the next version of Hudson (v2) looks
>> like. I look forward to working closely with the community on where to
>> go from here.
>>
>> regards
>>
>> Susan
>>
>
> _____________
>
> The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.
> _____________
>

--
Kohsuke Kawaguchi

_____________

The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.
_____________

[Jorg Heymans-4]

Unsubscribed, thanks for the pointer Renaud.

Good luck to Hudson, long live Jenkins :-)

Jorg

2011/2/1 Renaud Lepage <[hidden email]>

Send an email to [hidden email]

subject: "unsubscribe *", no quotes
no content.

and follow the instructions.


Sorry Susan!

-RL

2011/2/1 Eirik Bjørsnøs <[hidden email]>

unsubscribe

No, seriously: How do I get off this list?

The headers seem to indicate that an email to [hidden email]
with a subject of "unsubscribe-dev" should do the trick, but sympa
replies that it finds no command.

Is this Oracle's way of building a "community"? Creating email lists
that people can't unsubscribe from?

Eirik.

On Tue, Feb 1, 2011 at 7:20 PM,  <[hidden email]> wrote:
> All, Now that the fork has happened, we can start to put this saga
> behind us and get back to work.  At this point we want to reassure you
> that Hudson-ci continues and has our full commitment. We have a
> dedicated team that includes people from Oracle, as well as some of our
> partners and current Hudson community members who will continue to
> build and grow the Hudson project and community.
>
> Your current installations will continue to run fine, and you won't
> need to change any code. You can still come to the newly designed
> http://www.hudson-ci.org/ for all things Hudson. Later this week we
> will announce a new release of Hudson. This release will primarily
> de-couple the Hudson code from the old auto-update center back to the
> official Hudson update center.  If you use auto-update with version
> 1.395 or earlier, the auto-update will take you to a site that will ask
> you to install jenkins which will remove your Hudson installation.  If
> you want to continue to use Hudson, you should install Hudson v1.396 or
> later when it becomes available later this week
>
> We have reverted to using the Hudson mailing lists on java.net but are
> open to discussion about creating a new google group.  In addition
> java.net provides a forum that can be used to discuss user problems,
> ideas and other issues. There is a link to get to that at the top of
> the hudson-ci.org website.  I would urge you to engage with other
> users.
>
> Also as part of the fork, the Hudson github project has been taken
> away. We have a current git repository on hudson.java.net where people
> can continue to check things in. We can also discuss moving this back
> to github once we get things settled.  If you are interested in getting
> involved, and are not already registered as a committer, please let us
> know.  This is your opportunity to help shape the future of Hudson.
>
> Our primary goals over the next months will be to fix high-priority
> bugs in the current edition of Hudson and formalize a development and
> release process that will allow users of Hudson to have more insight
> into what is being changed, why it is being changed, and when their
> bugs will be fixed. We will also continue the discussion that Winston
> started last month about what the next version of Hudson (v2) looks
> like. I look forward to working closely with the community on where to
> go from here.
>
> regards
>
> Susan
>

[Harry G]

Hi,

I'm just a neutral Hudson user, but followed the discussion and got involved a bit.
So to be informed correctly, you should read both sides of the story and then decide yourself.

Oracles point of view is here:
http://www.hudson-ci.org/docs/news.html
and on this mailing list.

The communities point of view is that they decided 214:14 to rename to Jenkins - not to fork.
http://jenkins.361315.n4.nabble.com/Rename-Vote-Results-td3246526.html
According to this result, it seems that most _current_ developers will follow Jenkins.
We'll see where the users will go and if Oracle is able to get other developers for the Hudson remaining at www.hudson-ci.org.
You can also read more in the blogs: http://jenkins-ci.org/node

Regards,

  Harald

-----Ursprüngliche Nachricht-----
Von: Trojan, Krzysztof [mailto:[hidden email]]
Gesendet: Dienstag, 1. Februar 2011 22:04
An: Kohsuke Kawaguchi
Cc: [hidden email]
Betreff: [Hudson-Dev] Re: [] The Future of Hudson

Hi,

So additionally to highjacking the project they also claim (or "suggest") to have your consent:

On the new Hudson-ci.org one can read:
"Many of you may be aware that Andrew Bayer and Cloudbees (where Kohsuke Kawaguchi now works) have confirmed their intent to fork Hudson into a new community. We want the Hudson community to know that we have a dedicated team that includes people from Oracle, as well as some of our partners and current Hudson community members who will continue to build and grow the Hudson project and community. Your current installations will continue to run fine, and you won't need to change any code. You can still come to http://www.hudson-ci.org/ for all things Hudson."

Don't know if you work Cloudbees ... but it does not necessarily mean you gave the project away to them.

Let's see what will come out of this mess ... the Hudson was usable before Oracle overtook it, we can always think about a fork ;)

But still I don't think I understand how one, especially a person of your level of recognition, can be "removed" from any open source project.

Kind regards,
Chris

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Kohsuke Kawaguchi
Sent: Tuesday, February 01, 2011 9:38 PM
To: Trojan, Krzysztof
Cc: [hidden email]
Subject: Re: [Hudson-Dev] Re: [] The Future of Hudson

No, I didn't hand over the project to Oracle. They feel they are
entitled to it, and I was simply removed from the project.

2011/2/1 Trojan, Krzysztof <[hidden email]>:

> What I am surprised is that Oracle was given ownership of the project.
> I have not paid attention to the list for some time now, but as far as
> I remember the latest approach on this by some Oracle employee
> had rather cold welcome.
>
> For me it looks like a highjack, not a fork ;)
> But it seems Kohsuke gave it his blessing, and I respect his opinion here.
>
> Regards,
> Chris
>
> -----Original Message-----
> From: Eirik Bjørsnøs [mailto:[hidden email]]
> Sent: Tuesday, February 01, 2011 9:07 PM
> To: [hidden email]
> Cc: [hidden email]
> Subject: [Hudson-Dev] Re: [] The Future of Hudson
>
> unsubscribe
>
> No, seriously: How do I get off this list?
>
> The headers seem to indicate that an email to [hidden email]
> with a subject of "unsubscribe-dev" should do the trick, but sympa
> replies that it finds no command.
>
> Is this Oracle's way of building a "community"? Creating email lists
> that people can't unsubscribe from?
>
> Eirik.
>
>
> On Tue, Feb 1, 2011 at 7:20 PM,  <[hidden email]> wrote:
>> All, Now that the fork has happened, we can start to put this saga
>> behind us and get back to work.  At this point we want to reassure you
>> that Hudson-ci continues and has our full commitment. We have a
>> dedicated team that includes people from Oracle, as well as some of our
>> partners and current Hudson community members who will continue to
>> build and grow the Hudson project and community.
>>
>> Your current installations will continue to run fine, and you won't
>> need to change any code. You can still come to the newly designed
>> http://www.hudson-ci.org/ for all things Hudson. Later this week we
>> will announce a new release of Hudson. This release will primarily
>> de-couple the Hudson code from the old auto-update center back to the
>> official Hudson update center.  If you use auto-update with version
>> 1.395 or earlier, the auto-update will take you to a site that will ask
>> you to install jenkins which will remove your Hudson installation.  If
>> you want to continue to use Hudson, you should install Hudson v1.396 or
>> later when it becomes available later this week
>>
>> We have reverted to using the Hudson mailing lists on java.net but are
>> open to discussion about creating a new google group.  In addition
>> java.net provides a forum that can be used to discuss user problems,
>> ideas and other issues. There is a link to get to that at the top of
>> the hudson-ci.org website.  I would urge you to engage with other
>> users.
>>
>> Also as part of the fork, the Hudson github project has been taken
>> away. We have a current git repository on hudson.java.net where people
>> can continue to check things in. We can also discuss moving this back
>> to github once we get things settled.  If you are interested in getting
>> involved, and are not already registered as a committer, please let us
>> know.  This is your opportunity to help shape the future of Hudson.
>>
>> Our primary goals over the next months will be to fix high-priority
>> bugs in the current edition of Hudson and formalize a development and
>> release process that will allow users of Hudson to have more insight
>> into what is being changed, why it is being changed, and when their
>> bugs will be fixed. We will also continue the discussion that Winston
>> started last month about what the next version of Hudson (v2) looks
>> like. I look forward to working closely with the community on where to
>> go from here.
>>
>> regards
>>
>> Susan
>>
>
> _____________
>
> The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.
> _____________
>

--
Kohsuke Kawaguchi

_____________

The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.
_____________

[汪黎]

unsubscribe

2011/2/2 <[hidden email]>

All, Now that the fork has happened, we can start to put this saga
behind us and get back to work.  At this point we want to reassure you
that Hudson-ci continues and has our full commitment. We have a
dedicated team that includes people from Oracle, as well as some of our
partners and current Hudson community members who will continue to
build and grow the Hudson project and community.

Your current installations will continue to run fine, and you won't
need to change any code. You can still come to the newly designed
http://www.hudson-ci.org/ for all things Hudson. Later this week we
will announce a new release of Hudson. This release will primarily
de-couple the Hudson code from the old auto-update center back to the
official Hudson update center.  If you use auto-update with version
1.395 or earlier, the auto-update will take you to a site that will ask
you to install jenkins which will remove your Hudson installation.  If
you want to continue to use Hudson, you should install Hudson v1.396 or
later when it becomes available later this week

We have reverted to using the Hudson mailing lists on java.net but are
open to discussion about creating a new google group.  In addition
java.net provides a forum that can be used to discuss user problems,
ideas and other issues. There is a link to get to that at the top of
the hudson-ci.org website.  I would urge you to engage with other
users.

Also as part of the fork, the Hudson github project has been taken
away. We have a current git repository on hudson.java.net where people
can continue to check things in. We can also discuss moving this back
to github once we get things settled.  If you are interested in getting
involved, and are not already registered as a committer, please let us
know.  This is your opportunity to help shape the future of Hudson.

Our primary goals over the next months will be to fix high-priority
bugs in the current edition of Hudson and formalize a development and
release process that will allow users of Hudson to have more insight
into what is being changed, why it is being changed, and when their
bugs will be fixed. We will also continue the discussion that Winston
started last month about what the next version of Hudson (v2) looks
like. I look forward to working closely with the community on where to
go from here.

regards

Susan