Re: [IMPORTANT NOTICE] Jira migration from Codehaus to Apache on April 4th
Hi Herve, Can we please have a look at my account (Username:tibor17), especially the profile because the Groups is jira-users instead of maven-developers. Thx for answer. Tibor -- View this message in context: http://maven.40175.n5.nabble.com/IMPORTANT-NOTICE-Jira-migration-from-Codehaus-to-Apache-on-April-4th-tp5830262p5833095.html Sent from the Maven Developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [IMPORTANT NOTICE] Jira migration from Codehaus to Apache on April 4th
We need project components, project versions permissions from 2.) and issue management from 1.). -- View this message in context: http://maven.40175.n5.nabble.com/IMPORTANT-NOTICE-Jira-migration-from-Codehaus-to-Apache-on-April-4th-tp5830262p5832593.html Sent from the Maven Developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [IMPORTANT NOTICE] Jira migration from Codehaus to Apache on April 4th
Hervé, it looks much better now, as far as issues are concerned: I can assign issues and edit all parts of them (including title and descrition). That's great :). But I still can't manage the versions, e.g. add new ones, mark them released, or add descriptions to them. As that is part of the stuff that needs to be done when releasing something, I think that the Committers role should have the rights for that as well... Is that possible? Btw, I think that the work that you, Infra and Codehaus have put in for this is remarkable - a big thanks from me as well! 2015-04-11 1:38 GMT+02:00 Hervé BOUTEMY herve.bout...@free.fr: Hi, Dan and Andreas, you're in maven-developers groups = what is expected Then if you can't do anything useful, yes, there is some part missing in the config: we'll need to figure out which one :) Currently, the pattern applied to the Maven projects regarding roles is: - role Administrators = maven-administrators - role Developers = maven-developers which seems logical looking at Permissions, I see that most permissions are set on PMC and Committers roles, but absolutely no permission is set on Developers role: I thing it is the problem! To test another config on one project before doing it on every other, let's try on SUREFIRE: I just configured role PMC for maven-administrators and role Committers for maven-developers Can you check what actions this lets you do and if somthing is still missing, please? Regards Hervé Le vendredi 10 avril 2015 23:34:49 Andreas Gudian a écrit : Hi, I already am in the group maven-developers, but I don't seem to be able to do anything meaningfull, like managing versions or assigning issues to myself... I checked in SUREFIRE and in MECLIPSE. Is there some part missing in the config? Thanks, Andreas 2015-04-10 23:23 GMT+02:00 Dan Tran dant...@gmail.com: Hi Please add me as well Thanks -D On Fri, Apr 10, 2015 at 1:59 PM, Hervé BOUTEMY herve.bout...@free.fr wrote: I added you to the last request for maven-developers group https://issues.apache.org/jira/browse/INFRA-9422 Regards, Hervé Le vendredi 10 avril 2015 22:20:30 Mirko Friedenhagen a écrit : Hello, now I tried to assign https://issues.apache.org/jira/browse/MRELEASE-901 to myself and was unable to do so. However I was allowed to resolve the issue (and could close it as well). When going to my profile (https://issues.apache.org/jira/secure/ViewProfile.jspa) I see that I am only in the group jira-users and not in any other group (so is Robert Scholte btw, but he has assigned issues). Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ ( http://osrc.dfm.io/mfriedenhagen) https://bitbucket.org/mfriedenhagen/ On Tue, Apr 7, 2015 at 7:43 AM, Kristian Rosenvold kristian.rosenv...@gmail.com wrote: The user name mapping seems to be ok, but I seem to be missing permissions to do anything sensible at all ? (krosenvold) Kristian 2015-04-06 23:58 GMT+02:00 Mirko Friedenhagen mfriedenha...@gmail.com A big thank you from my side as well, I logged in to https://issues.apache.org/jira/ and was easily able to see all my reported issues and am allowed to edit the open ones. Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ ( http://osrc.dfm.io/mfriedenhagen ) https://bitbucket.org/mfriedenhagen/ On Mon, Apr 6, 2015 at 2:29 PM, Jason van Zyl ja...@takari.io wrote: The mapping did not work for my user as all issues that were assigned to jason on the Codehaus side are now mapping to Jason Lane. I also can no longer even log into issues.apache.org to comment on INFRA-9389. My codehaus user is jason, and my Apache user is jvanzyl. I lined up all my email addresses but only did so 3 hours before the migration so maybe that is the issue. But I've lost all access to the Apache JIRA instance all together and all my issues are assigned to someone else completely. On Apr 6, 2015, at 6:26 AM, Hervé BOUTEMY herve.bout...@free.fr wrote: there were a lot of manual tasks that took hours, really many hours (the night was shorter than expected), even more for Mark than for me: it's great to see that the result is positive = you can continue to work on the issues but everything didn't go as expected regarding accounts: please report any problem to INFRA-9389 [1] with precise info regarding usernames at Codehaus and at ASF Thank you Ben
Re: [IMPORTANT NOTICE] Jira migration from Codehaus to Apache on April 4th
ok, thanks for the feedback: we're in the right direction
I'll immediately change the configuration to every Jira project, since the
current SUREFIRE configuration lets committers work on daily basis, which is
important!
then I just had a look at Jira documentation [1]
and it seems managing versions is in Administer Projects permission, like
other abilities:
edit project role membership, project components, project versions and some
project details ('Project Name', 'URL', 'Project Lead', 'Project
Description')
This means we now have 2 choices:
1. either give this ability only to PMC members, like it is done at the
moment: committers have a lot of freedom on issues, but not on projects: if
they need a version or a component, they'll ask to PMC, like at the moment on
other activities related to release management
2. or give the project administrator role to committers
I like the second option, but the only associated ability that IMHO makes this
decision debatable is edit project role membership. I'll ask Mark if this
one can be configured independently from the other ones
If not, we'll have to make a choice.
IIUC, with current SUREFIRE configuration, that will be applied immediately to
every project, we're not in a hurry: this is only a point to decide in the
near future, isn't it?
Regards,
Hervé
[1] https://confluence.atlassian.com/display/JIRA/Managing+Project+Permissions
Le samedi 11 avril 2015 12:09:03 Andreas Gudian a écrit :
Hervé, it looks much better now, as far as issues are concerned: I can
assign issues and edit all parts of them (including title and descrition).
That's great :).
But I still can't manage the versions, e.g. add new ones, mark them
released, or add descriptions to them. As that is part of the stuff that
needs to be done when releasing something, I think that the Committers
role should have the rights for that as well... Is that possible?
Btw, I think that the work that you, Infra and Codehaus have put in for
this is remarkable - a big thanks from me as well!
2015-04-11 1:38 GMT+02:00 Hervé BOUTEMY herve.bout...@free.fr:
Hi,
Dan and Andreas, you're in maven-developers groups = what is expected
Then if you can't do anything useful, yes, there is some part missing in
the
config: we'll need to figure out which one :)
Currently, the pattern applied to the Maven projects regarding roles is:
- role Administrators = maven-administrators
- role Developers = maven-developers
which seems logical
looking at Permissions, I see that most permissions are set on PMC and
Committers roles, but absolutely no permission is set on Developers role:
I
thing it is the problem!
To test another config on one project before doing it on every other,
let's try
on SUREFIRE:
I just configured role PMC for maven-administrators and role Committers
for
maven-developers
Can you check what actions this lets you do and if somthing is still
missing,
please?
Regards
Hervé
Le vendredi 10 avril 2015 23:34:49 Andreas Gudian a écrit :
Hi,
I already am in the group maven-developers, but I don't seem to be
able
to do anything meaningfull, like managing versions or assigning issues
to
myself... I checked in SUREFIRE and in MECLIPSE.
Is there some part missing in the config?
Thanks,
Andreas
2015-04-10 23:23 GMT+02:00 Dan Tran dant...@gmail.com:
Hi
Please add me as well
Thanks
-D
On Fri, Apr 10, 2015 at 1:59 PM, Hervé BOUTEMY herve.bout...@free.fr
wrote:
I added you to the last request for maven-developers group
https://issues.apache.org/jira/browse/INFRA-9422
Regards,
Hervé
Le vendredi 10 avril 2015 22:20:30 Mirko Friedenhagen a écrit :
Hello,
now I tried to assign
https://issues.apache.org/jira/browse/MRELEASE-901 to myself and
was
unable to do so. However I was allowed to resolve the issue (and
could
close it as well).
When going to my profile
(https://issues.apache.org/jira/secure/ViewProfile.jspa) I see
that I
am only in the group jira-users and not in any other group (so is
Robert Scholte btw, but he has assigned issues).
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/ (
http://osrc.dfm.io/mfriedenhagen)
https://bitbucket.org/mfriedenhagen/
On Tue, Apr 7, 2015 at 7:43 AM, Kristian Rosenvold
kristian.rosenv...@gmail.com wrote:
The user name mapping seems to be ok, but I seem to be missing
permissions to do anything sensible at all ?
(krosenvold)
Kristian
2015-04-06 23:58 GMT+02:00 Mirko Friedenhagen
mfriedenha...@gmail.com
A big thank you from my side as well, I logged in to
Re: [IMPORTANT NOTICE] Jira migration from Codehaus to Apache on April 4th
On Saturday, April 11, 2015, Hervé BOUTEMY herve.bout...@free.fr wrote:
ok, thanks for the feedback: we're in the right direction
I'll immediately change the configuration to every Jira project, since the
current SUREFIRE configuration lets committers work on daily basis, which
is
important!
then I just had a look at Jira documentation [1]
and it seems managing versions is in Administer Projects permission, like
other abilities:
edit project role membership, project components, project versions and
some
project details ('Project Name', 'URL', 'Project Lead', 'Project
Description')
This means we now have 2 choices:
1. either give this ability only to PMC members, like it is done at the
moment: committers have a lot of freedom on issues, but not on projects: if
they need a version or a component, they'll ask to PMC, like at the moment
on
other activities related to release management
Given that Committers cannot release without the ok of three PMC members I
think we should try option 1 and if ends up being too much of a burden then
switch to 2. I am loath to remove permissions from commiters after granting
them.
That's my opinion anyways... It's not especially strongly held either...
More a preference if you like ;-)
2. or give the project administrator role to committers
I like the second option, but the only associated ability that IMHO makes
this
decision debatable is edit project role membership. I'll ask Mark if this
one can be configured independently from the other ones
If not, we'll have to make a choice.
IIUC, with current SUREFIRE configuration, that will be applied
immediately to
every project, we're not in a hurry: this is only a point to decide in the
near future, isn't it?
Regards,
Hervé
[1]
https://confluence.atlassian.com/display/JIRA/Managing+Project+Permissions
Le samedi 11 avril 2015 12:09:03 Andreas Gudian a écrit :
Hervé, it looks much better now, as far as issues are concerned: I can
assign issues and edit all parts of them (including title and
descrition).
That's great :).
But I still can't manage the versions, e.g. add new ones, mark them
released, or add descriptions to them. As that is part of the stuff that
needs to be done when releasing something, I think that the Committers
role should have the rights for that as well... Is that possible?
Btw, I think that the work that you, Infra and Codehaus have put in for
this is remarkable - a big thanks from me as well!
2015-04-11 1:38 GMT+02:00 Hervé BOUTEMY herve.bout...@free.fr
javascript:;:
Hi,
Dan and Andreas, you're in maven-developers groups = what is expected
Then if you can't do anything useful, yes, there is some part missing
in
the
config: we'll need to figure out which one :)
Currently, the pattern applied to the Maven projects regarding roles
is:
- role Administrators = maven-administrators
- role Developers = maven-developers
which seems logical
looking at Permissions, I see that most permissions are set on PMC and
Committers roles, but absolutely no permission is set on Developers
role:
I
thing it is the problem!
To test another config on one project before doing it on every other,
let's try
on SUREFIRE:
I just configured role PMC for maven-administrators and role Committers
for
maven-developers
Can you check what actions this lets you do and if somthing is still
missing,
please?
Regards
Hervé
Le vendredi 10 avril 2015 23:34:49 Andreas Gudian a écrit :
Hi,
I already am in the group maven-developers, but I don't seem to be
able
to do anything meaningfull, like managing versions or assigning
issues
to
myself... I checked in SUREFIRE and in MECLIPSE.
Is there some part missing in the config?
Thanks,
Andreas
2015-04-10 23:23 GMT+02:00 Dan Tran dant...@gmail.com
javascript:;:
Hi
Please add me as well
Thanks
-D
On Fri, Apr 10, 2015 at 1:59 PM, Hervé BOUTEMY
herve.bout...@free.fr javascript:;
wrote:
I added you to the last request for maven-developers group
https://issues.apache.org/jira/browse/INFRA-9422
Regards,
Hervé
Le vendredi 10 avril 2015 22:20:30 Mirko Friedenhagen a écrit :
Hello,
now I tried to assign
https://issues.apache.org/jira/browse/MRELEASE-901 to myself
and
was
unable to do so. However I was allowed to resolve the issue
(and
could
close it as well).
When going to my profile
(https://issues.apache.org/jira/secure/ViewProfile.jspa) I see
that I
am only in the group jira-users and not in any other group (so
is
Robert Scholte btw, but he has assigned issues).
Regards Mirko
--
http://illegalstateexception.blogspot.com/
Re: [IMPORTANT NOTICE] Jira migration from Codehaus to Apache on April 4th
Hi,
On 4/11/15 2:26 PM, Hervé BOUTEMY wrote:
ok, thanks for the feedback: we're in the right direction
I'll immediately change the configuration to every Jira project, since the
current SUREFIRE configuration lets committers work on daily basis, which is
important!
then I just had a look at Jira documentation [1]
and it seems managing versions is in Administer Projects permission, like
other abilities:
edit project role membership, project components, project versions and some
project details ('Project Name', 'URL', 'Project Lead', 'Project
Description')
This means we now have 2 choices:
1. either give this ability only to PMC members, like it is done at the
moment: committers have a lot of freedom on issues, but not on projects: if
they need a version or a component, they'll ask to PMC, like at the moment on
other activities related to release management
I would go with option 1 as wellwe can see if much is comming than
we might decide otherwise...
Kind regards
Karl Heinz Marbaise
2. or give the project administrator role to committers
I like the second option, but the only associated ability that IMHO makes this
decision debatable is edit project role membership. I'll ask Mark if this
one can be configured independently from the other ones
If not, we'll have to make a choice.
IIUC, with current SUREFIRE configuration, that will be applied immediately to
every project, we're not in a hurry: this is only a point to decide in the
near future, isn't it?
Regards,
Hervé
[1] https://confluence.atlassian.com/display/JIRA/Managing+Project+Permissions
Le samedi 11 avril 2015 12:09:03 Andreas Gudian a écrit :
Hervé, it looks much better now, as far as issues are concerned: I can
assign issues and edit all parts of them (including title and descrition).
That's great :).
But I still can't manage the versions, e.g. add new ones, mark them
released, or add descriptions to them. As that is part of the stuff that
needs to be done when releasing something, I think that the Committers
role should have the rights for that as well... Is that possible?
Btw, I think that the work that you, Infra and Codehaus have put in for
this is remarkable - a big thanks from me as well!
2015-04-11 1:38 GMT+02:00 Hervé BOUTEMY herve.bout...@free.fr:
Hi,
Dan and Andreas, you're in maven-developers groups = what is expected
Then if you can't do anything useful, yes, there is some part missing in
the
config: we'll need to figure out which one :)
Currently, the pattern applied to the Maven projects regarding roles is:
- role Administrators = maven-administrators
- role Developers = maven-developers
which seems logical
looking at Permissions, I see that most permissions are set on PMC and
Committers roles, but absolutely no permission is set on Developers role:
I
thing it is the problem!
To test another config on one project before doing it on every other,
let's try
on SUREFIRE:
I just configured role PMC for maven-administrators and role Committers
for
maven-developers
Can you check what actions this lets you do and if somthing is still
missing,
please?
Regards
Hervé
Le vendredi 10 avril 2015 23:34:49 Andreas Gudian a écrit :
Hi,
I already am in the group maven-developers, but I don't seem to be
able
to do anything meaningfull, like managing versions or assigning issues
to
myself... I checked in SUREFIRE and in MECLIPSE.
Is there some part missing in the config?
Thanks,
Andreas
2015-04-10 23:23 GMT+02:00 Dan Tran dant...@gmail.com:
Hi
Please add me as well
Thanks
-D
On Fri, Apr 10, 2015 at 1:59 PM, Hervé BOUTEMY herve.bout...@free.fr
wrote:
I added you to the last request for maven-developers group
https://issues.apache.org/jira/browse/INFRA-9422
Regards,
Hervé
Le vendredi 10 avril 2015 22:20:30 Mirko Friedenhagen a écrit :
Hello,
now I tried to assign
https://issues.apache.org/jira/browse/MRELEASE-901 to myself and
was
unable to do so. However I was allowed to resolve the issue (and
could
close it as well).
When going to my profile
(https://issues.apache.org/jira/secure/ViewProfile.jspa) I see
that I
am only in the group jira-users and not in any other group (so is
Robert Scholte btw, but he has assigned issues).
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/ (
http://osrc.dfm.io/mfriedenhagen)
https://bitbucket.org/mfriedenhagen/
On Tue, Apr 7, 2015 at 7:43 AM, Kristian Rosenvold
kristian.rosenv...@gmail.com wrote:
The user name mapping seems to be ok, but I seem to be missing
permissions to do anything sensible at all ?
(krosenvold)
Kristian
2015-04-06 23:58 GMT+02:00 Mirko Friedenhagen
mfriedenha...@gmail.com
A big thank you from my side as well, I logged in to
https://issues.apache.org/jira/ and was easily able to see all
my
reported issues and am allowed to edit the open ones.
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/ (
Re: [IMPORTANT NOTICE] Jira migration from Codehaus to Apache on April 4th
If committers cannot manage versions with option 1, I think we
should do option 2, since it would make the release process
increasingly complex for committers and increase the number of
interactions required.
Kristian
2015-04-11 15:10 GMT+02:00 Karl Heinz Marbaise khmarba...@gmx.de:
Hi,
On 4/11/15 2:26 PM, Hervé BOUTEMY wrote:
ok, thanks for the feedback: we're in the right direction
I'll immediately change the configuration to every Jira project, since the
current SUREFIRE configuration lets committers work on daily basis, which
is
important!
then I just had a look at Jira documentation [1]
and it seems managing versions is in Administer Projects permission,
like
other abilities:
edit project role membership, project components, project versions and
some
project details ('Project Name', 'URL', 'Project Lead', 'Project
Description')
This means we now have 2 choices:
1. either give this ability only to PMC members, like it is done at the
moment: committers have a lot of freedom on issues, but not on projects:
if
they need a version or a component, they'll ask to PMC, like at the moment
on
other activities related to release management
I would go with option 1 as wellwe can see if much is comming than we
might decide otherwise...
Kind regards
Karl Heinz Marbaise
2. or give the project administrator role to committers
I like the second option, but the only associated ability that IMHO makes
this
decision debatable is edit project role membership. I'll ask Mark if
this
one can be configured independently from the other ones
If not, we'll have to make a choice.
IIUC, with current SUREFIRE configuration, that will be applied
immediately to
every project, we're not in a hurry: this is only a point to decide in the
near future, isn't it?
Regards,
Hervé
[1]
https://confluence.atlassian.com/display/JIRA/Managing+Project+Permissions
Le samedi 11 avril 2015 12:09:03 Andreas Gudian a écrit :
Hervé, it looks much better now, as far as issues are concerned: I can
assign issues and edit all parts of them (including title and
descrition).
That's great :).
But I still can't manage the versions, e.g. add new ones, mark them
released, or add descriptions to them. As that is part of the stuff that
needs to be done when releasing something, I think that the Committers
role should have the rights for that as well... Is that possible?
Btw, I think that the work that you, Infra and Codehaus have put in for
this is remarkable - a big thanks from me as well!
2015-04-11 1:38 GMT+02:00 Hervé BOUTEMY herve.bout...@free.fr:
Hi,
Dan and Andreas, you're in maven-developers groups = what is expected
Then if you can't do anything useful, yes, there is some part missing in
the
config: we'll need to figure out which one :)
Currently, the pattern applied to the Maven projects regarding roles is:
- role Administrators = maven-administrators
- role Developers = maven-developers
which seems logical
looking at Permissions, I see that most permissions are set on PMC and
Committers roles, but absolutely no permission is set on Developers
role:
I
thing it is the problem!
To test another config on one project before doing it on every other,
let's try
on SUREFIRE:
I just configured role PMC for maven-administrators and role Committers
for
maven-developers
Can you check what actions this lets you do and if somthing is still
missing,
please?
Regards
Hervé
Le vendredi 10 avril 2015 23:34:49 Andreas Gudian a écrit :
Hi,
I already am in the group maven-developers, but I don't seem to be
able
to do anything meaningfull, like managing versions or assigning issues
to
myself... I checked in SUREFIRE and in MECLIPSE.
Is there some part missing in the config?
Thanks,
Andreas
2015-04-10 23:23 GMT+02:00 Dan Tran dant...@gmail.com:
Hi
Please add me as well
Thanks
-D
On Fri, Apr 10, 2015 at 1:59 PM, Hervé BOUTEMY herve.bout...@free.fr
wrote:
I added you to the last request for maven-developers group
https://issues.apache.org/jira/browse/INFRA-9422
Regards,
Hervé
Le vendredi 10 avril 2015 22:20:30 Mirko Friedenhagen a écrit :
Hello,
now I tried to assign
https://issues.apache.org/jira/browse/MRELEASE-901 to myself and
was
unable to do so. However I was allowed to resolve the issue (and
could
close it as well).
When going to my profile
(https://issues.apache.org/jira/secure/ViewProfile.jspa) I see
that I
am only in the group jira-users and not in any other group (so is
Robert Scholte btw, but he has assigned issues).
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/ (
http://osrc.dfm.io/mfriedenhagen)
https://bitbucket.org/mfriedenhagen/
On Tue, Apr 7, 2015 at 7:43 AM, Kristian Rosenvold
kristian.rosenv...@gmail.com wrote:
The user name mapping seems to be ok, but I seem to be missing
permissions to do anything sensible at all ?
Re: [IMPORTANT NOTICE] Jira migration from Codehaus to Apache on April 4th
Le samedi 11 avril 2015 12:09:03 Andreas Gudian a écrit : Btw, I think that the work that you, Infra and Codehaus have put in for this is remarkable - a big thanks from me as well! notice: this is nice to read :) - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [IMPORTANT NOTICE] Jira migration from Codehaus to Apache on April 4th
Le samedi 11 avril 2015 15:24:59 Kristian Rosenvold a écrit :
If committers cannot manage versions with option 1, I think we
should do option 2, since it would make the release process
increasingly complex for committers and increase the number of
interactions required.
you need to manage version exactly at the same time you need to contact the
PMC for publication of the release: I don't think the process is really more
complex, but the PMC will have more work than /dist + board report: now he
will have to mark the release on Jira and create next version
I think we can start with option 1 and see in a few weeks if there are
unexpected issues
Regards,
Hervé
Kristian
2015-04-11 15:10 GMT+02:00 Karl Heinz Marbaise khmarba...@gmx.de:
Hi,
On 4/11/15 2:26 PM, Hervé BOUTEMY wrote:
ok, thanks for the feedback: we're in the right direction
I'll immediately change the configuration to every Jira project, since
the
current SUREFIRE configuration lets committers work on daily basis, which
is
important!
then I just had a look at Jira documentation [1]
and it seems managing versions is in Administer Projects permission,
like
other abilities:
edit project role membership, project components, project versions and
some
project details ('Project Name', 'URL', 'Project Lead', 'Project
Description')
This means we now have 2 choices:
1. either give this ability only to PMC members, like it is done at the
moment: committers have a lot of freedom on issues, but not on projects:
if
they need a version or a component, they'll ask to PMC, like at the
moment
on
other activities related to release management
I would go with option 1 as wellwe can see if much is comming than we
might decide otherwise...
Kind regards
Karl Heinz Marbaise
2. or give the project administrator role to committers
I like the second option, but the only associated ability that IMHO makes
this
decision debatable is edit project role membership. I'll ask Mark if
this
one can be configured independently from the other ones
If not, we'll have to make a choice.
IIUC, with current SUREFIRE configuration, that will be applied
immediately to
every project, we're not in a hurry: this is only a point to decide in
the
near future, isn't it?
Regards,
Hervé
[1]
https://confluence.atlassian.com/display/JIRA/Managing+Project+Permission
s
Le samedi 11 avril 2015 12:09:03 Andreas Gudian a écrit :
Hervé, it looks much better now, as far as issues are concerned: I can
assign issues and edit all parts of them (including title and
descrition).
That's great :).
But I still can't manage the versions, e.g. add new ones, mark them
released, or add descriptions to them. As that is part of the stuff that
needs to be done when releasing something, I think that the Committers
role should have the rights for that as well... Is that possible?
Btw, I think that the work that you, Infra and Codehaus have put in for
this is remarkable - a big thanks from me as well!
2015-04-11 1:38 GMT+02:00 Hervé BOUTEMY herve.bout...@free.fr:
Hi,
Dan and Andreas, you're in maven-developers groups = what is expected
Then if you can't do anything useful, yes, there is some part missing
in
the
config: we'll need to figure out which one :)
Currently, the pattern applied to the Maven projects regarding roles
is:
- role Administrators = maven-administrators
- role Developers = maven-developers
which seems logical
looking at Permissions, I see that most permissions are set on PMC and
Committers roles, but absolutely no permission is set on Developers
role:
I
thing it is the problem!
To test another config on one project before doing it on every other,
let's try
on SUREFIRE:
I just configured role PMC for maven-administrators and role Committers
for
maven-developers
Can you check what actions this lets you do and if somthing is still
missing,
please?
Regards
Hervé
Le vendredi 10 avril 2015 23:34:49 Andreas Gudian a écrit :
Hi,
I already am in the group maven-developers, but I don't seem to be
able
to do anything meaningfull, like managing versions or assigning issues
to
myself... I checked in SUREFIRE and in MECLIPSE.
Is there some part missing in the config?
Thanks,
Andreas
2015-04-10 23:23 GMT+02:00 Dan Tran dant...@gmail.com:
Hi
Please add me as well
Thanks
-D
On Fri, Apr 10, 2015 at 1:59 PM, Hervé BOUTEMY
herve.bout...@free.fr
wrote:
I added you to the last request for maven-developers group
https://issues.apache.org/jira/browse/INFRA-9422
Regards,
Hervé
Le vendredi 10 avril 2015 22:20:30 Mirko Friedenhagen a écrit :
Hello,
now I tried to assign
https://issues.apache.org/jira/browse/MRELEASE-901 to myself and
was
unable to do so. However
Re: [IMPORTANT NOTICE] Jira migration from Codehaus to Apache on April 4th
Hello, now I tried to assign https://issues.apache.org/jira/browse/MRELEASE-901 to myself and was unable to do so. However I was allowed to resolve the issue (and could close it as well). When going to my profile (https://issues.apache.org/jira/secure/ViewProfile.jspa) I see that I am only in the group jira-users and not in any other group (so is Robert Scholte btw, but he has assigned issues). Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen) https://bitbucket.org/mfriedenhagen/ On Tue, Apr 7, 2015 at 7:43 AM, Kristian Rosenvold kristian.rosenv...@gmail.com wrote: The user name mapping seems to be ok, but I seem to be missing permissions to do anything sensible at all ? (krosenvold) Kristian 2015-04-06 23:58 GMT+02:00 Mirko Friedenhagen mfriedenha...@gmail.com: A big thank you from my side as well, I logged in to https://issues.apache.org/jira/ and was easily able to see all my reported issues and am allowed to edit the open ones. Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen) https://bitbucket.org/mfriedenhagen/ On Mon, Apr 6, 2015 at 2:29 PM, Jason van Zyl ja...@takari.io wrote: The mapping did not work for my user as all issues that were assigned to jason on the Codehaus side are now mapping to Jason Lane. I also can no longer even log into issues.apache.org to comment on INFRA-9389. My codehaus user is jason, and my Apache user is jvanzyl. I lined up all my email addresses but only did so 3 hours before the migration so maybe that is the issue. But I've lost all access to the Apache JIRA instance all together and all my issues are assigned to someone else completely. On Apr 6, 2015, at 6:26 AM, Hervé BOUTEMY herve.bout...@free.fr wrote: there were a lot of manual tasks that took hours, really many hours (the night was shorter than expected), even more for Mark than for me: it's great to see that the result is positive = you can continue to work on the issues but everything didn't go as expected regarding accounts: please report any problem to INFRA-9389 [1] with precise info regarding usernames at Codehaus and at ASF Thank you Ben for all the Codehaus support, and big big big thank you to Mark at ASF infra for the huge work on import. Regards, Hervé [1] https://issues.apache.org/jira/browse/INFRA-9389 Le lundi 6 avril 2015 11:55:01 Robert Scholte a écrit : I would like to take this chance to give huge kudo's to all involved parties. My first impression is that the migration went very well, since I can continue my work at https://issues.apache.org/jira as I was used to. The preparations already showed that it was more than a simple copy. It was a huge move and not everything could be automated (e.g. making all 60+ Jira projects read-only at Codehaus) but the end result is great. Thanks a lot Hervé, ASF Infra and Codehaus Support! Op Sat, 04 Apr 2015 23:10:55 +0200 schreef Hervé BOUTEMY herve.bout...@free.fr: Hi, Codehaus was put read-only during migration, when we started by doing a dump of the content. Import at ASF is not one yet: should be done tomorrow. You just have to way for 24 hours that the migration is done :) Regards, Hervé Le samedi 4 avril 2015 14:03:43 Tibor Digana a écrit : Hello guys, I am not able to find https://issues.apache.org/jira/browse/SUREFIRE I am not able to manage the issues at Codehaus either ASF. What can we do about that? Cheers Tibor -- View this message in context: http://maven.40175.n5.nabble.com/IMPORTANT-NOTICE-Jira-migration-from-Cod eh aus-to-Apache-on-April-4th-tp5830262p5831520.html Sent from the Maven Developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Takari and Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io - In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The
Re: [IMPORTANT NOTICE] Jira migration from Codehaus to Apache on April 4th
Jira has a different approach: you can only see shared groups. I am a member of multiple groups, but since you're not a member of any of these groups (exepct jira-users) you can't see them. Robert Op Fri, 10 Apr 2015 22:20:30 +0200 schreef Mirko Friedenhagen mfriedenha...@gmail.com: Hello, now I tried to assign https://issues.apache.org/jira/browse/MRELEASE-901 to myself and was unable to do so. However I was allowed to resolve the issue (and could close it as well). When going to my profile (https://issues.apache.org/jira/secure/ViewProfile.jspa) I see that I am only in the group jira-users and not in any other group (so is Robert Scholte btw, but he has assigned issues). Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen) https://bitbucket.org/mfriedenhagen/ On Tue, Apr 7, 2015 at 7:43 AM, Kristian Rosenvold kristian.rosenv...@gmail.com wrote: The user name mapping seems to be ok, but I seem to be missing permissions to do anything sensible at all ? (krosenvold) Kristian 2015-04-06 23:58 GMT+02:00 Mirko Friedenhagen mfriedenha...@gmail.com: A big thank you from my side as well, I logged in to https://issues.apache.org/jira/ and was easily able to see all my reported issues and am allowed to edit the open ones. Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen) https://bitbucket.org/mfriedenhagen/ On Mon, Apr 6, 2015 at 2:29 PM, Jason van Zyl ja...@takari.io wrote: The mapping did not work for my user as all issues that were assigned to jason on the Codehaus side are now mapping to Jason Lane. I also can no longer even log into issues.apache.org to comment on INFRA-9389. My codehaus user is jason, and my Apache user is jvanzyl. I lined up all my email addresses but only did so 3 hours before the migration so maybe that is the issue. But I've lost all access to the Apache JIRA instance all together and all my issues are assigned to someone else completely. On Apr 6, 2015, at 6:26 AM, Hervé BOUTEMY herve.bout...@free.fr wrote: there were a lot of manual tasks that took hours, really many hours (the night was shorter than expected), even more for Mark than for me: it's great to see that the result is positive = you can continue to work on the issues but everything didn't go as expected regarding accounts: please report any problem to INFRA-9389 [1] with precise info regarding usernames at Codehaus and at ASF Thank you Ben for all the Codehaus support, and big big big thank you to Mark at ASF infra for the huge work on import. Regards, Hervé [1] https://issues.apache.org/jira/browse/INFRA-9389 Le lundi 6 avril 2015 11:55:01 Robert Scholte a écrit : I would like to take this chance to give huge kudo's to all involved parties. My first impression is that the migration went very well, since I can continue my work at https://issues.apache.org/jira as I was used to. The preparations already showed that it was more than a simple copy. It was a huge move and not everything could be automated (e.g. making all 60+ Jira projects read-only at Codehaus) but the end result is great. Thanks a lot Hervé, ASF Infra and Codehaus Support! Op Sat, 04 Apr 2015 23:10:55 +0200 schreef Hervé BOUTEMY herve.bout...@free.fr: Hi, Codehaus was put read-only during migration, when we started by doing a dump of the content. Import at ASF is not one yet: should be done tomorrow. You just have to way for 24 hours that the migration is done :) Regards, Hervé Le samedi 4 avril 2015 14:03:43 Tibor Digana a écrit : Hello guys, I am not able to find https://issues.apache.org/jira/browse/SUREFIRE I am not able to manage the issues at Codehaus either ASF. What can we do about that? Cheers Tibor -- View this message in context: http://maven.40175.n5.nabble.com/IMPORTANT-NOTICE-Jira-migration-from-Cod eh aus-to-Apache-on-April-4th-tp5830262p5831520.html Sent from the Maven Developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Takari and Apache Maven
Re: [IMPORTANT NOTICE] Jira migration from Codehaus to Apache on April 4th
I added you to the last request for maven-developers group https://issues.apache.org/jira/browse/INFRA-9422 Regards, Hervé Le vendredi 10 avril 2015 22:20:30 Mirko Friedenhagen a écrit : Hello, now I tried to assign https://issues.apache.org/jira/browse/MRELEASE-901 to myself and was unable to do so. However I was allowed to resolve the issue (and could close it as well). When going to my profile (https://issues.apache.org/jira/secure/ViewProfile.jspa) I see that I am only in the group jira-users and not in any other group (so is Robert Scholte btw, but he has assigned issues). Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen) https://bitbucket.org/mfriedenhagen/ On Tue, Apr 7, 2015 at 7:43 AM, Kristian Rosenvold kristian.rosenv...@gmail.com wrote: The user name mapping seems to be ok, but I seem to be missing permissions to do anything sensible at all ? (krosenvold) Kristian 2015-04-06 23:58 GMT+02:00 Mirko Friedenhagen mfriedenha...@gmail.com: A big thank you from my side as well, I logged in to https://issues.apache.org/jira/ and was easily able to see all my reported issues and am allowed to edit the open ones. Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen) https://bitbucket.org/mfriedenhagen/ On Mon, Apr 6, 2015 at 2:29 PM, Jason van Zyl ja...@takari.io wrote: The mapping did not work for my user as all issues that were assigned to jason on the Codehaus side are now mapping to Jason Lane. I also can no longer even log into issues.apache.org to comment on INFRA-9389. My codehaus user is jason, and my Apache user is jvanzyl. I lined up all my email addresses but only did so 3 hours before the migration so maybe that is the issue. But I've lost all access to the Apache JIRA instance all together and all my issues are assigned to someone else completely. On Apr 6, 2015, at 6:26 AM, Hervé BOUTEMY herve.bout...@free.fr wrote: there were a lot of manual tasks that took hours, really many hours (the night was shorter than expected), even more for Mark than for me: it's great to see that the result is positive = you can continue to work on the issues but everything didn't go as expected regarding accounts: please report any problem to INFRA-9389 [1] with precise info regarding usernames at Codehaus and at ASF Thank you Ben for all the Codehaus support, and big big big thank you to Mark at ASF infra for the huge work on import. Regards, Hervé [1] https://issues.apache.org/jira/browse/INFRA-9389 Le lundi 6 avril 2015 11:55:01 Robert Scholte a écrit : I would like to take this chance to give huge kudo's to all involved parties. My first impression is that the migration went very well, since I can continue my work at https://issues.apache.org/jira as I was used to. The preparations already showed that it was more than a simple copy. It was a huge move and not everything could be automated (e.g. making all 60+ Jira projects read-only at Codehaus) but the end result is great. Thanks a lot Hervé, ASF Infra and Codehaus Support! Op Sat, 04 Apr 2015 23:10:55 +0200 schreef Hervé BOUTEMY herve.bout...@free.fr: Hi, Codehaus was put read-only during migration, when we started by doing a dump of the content. Import at ASF is not one yet: should be done tomorrow. You just have to way for 24 hours that the migration is done :) Regards, Hervé Le samedi 4 avril 2015 14:03:43 Tibor Digana a écrit : Hello guys, I am not able to find https://issues.apache.org/jira/browse/SUREFIRE I am not able to manage the issues at Codehaus either ASF. What can we do about that? Cheers Tibor -- View this message in context: http://maven.40175.n5.nabble.com/IMPORTANT-NOTICE-Jira-migration-fro m-Cod eh aus-to-Apache-on-April-4th-tp5830262p5831520.html Sent from the Maven Developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason
Re: [IMPORTANT NOTICE] Jira migration from Codehaus to Apache on April 4th
Hi Please add me as well Thanks -D On Fri, Apr 10, 2015 at 1:59 PM, Hervé BOUTEMY herve.bout...@free.fr wrote: I added you to the last request for maven-developers group https://issues.apache.org/jira/browse/INFRA-9422 Regards, Hervé Le vendredi 10 avril 2015 22:20:30 Mirko Friedenhagen a écrit : Hello, now I tried to assign https://issues.apache.org/jira/browse/MRELEASE-901 to myself and was unable to do so. However I was allowed to resolve the issue (and could close it as well). When going to my profile (https://issues.apache.org/jira/secure/ViewProfile.jspa) I see that I am only in the group jira-users and not in any other group (so is Robert Scholte btw, but he has assigned issues). Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen) https://bitbucket.org/mfriedenhagen/ On Tue, Apr 7, 2015 at 7:43 AM, Kristian Rosenvold kristian.rosenv...@gmail.com wrote: The user name mapping seems to be ok, but I seem to be missing permissions to do anything sensible at all ? (krosenvold) Kristian 2015-04-06 23:58 GMT+02:00 Mirko Friedenhagen mfriedenha...@gmail.com : A big thank you from my side as well, I logged in to https://issues.apache.org/jira/ and was easily able to see all my reported issues and am allowed to edit the open ones. Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen) https://bitbucket.org/mfriedenhagen/ On Mon, Apr 6, 2015 at 2:29 PM, Jason van Zyl ja...@takari.io wrote: The mapping did not work for my user as all issues that were assigned to jason on the Codehaus side are now mapping to Jason Lane. I also can no longer even log into issues.apache.org to comment on INFRA-9389. My codehaus user is jason, and my Apache user is jvanzyl. I lined up all my email addresses but only did so 3 hours before the migration so maybe that is the issue. But I've lost all access to the Apache JIRA instance all together and all my issues are assigned to someone else completely. On Apr 6, 2015, at 6:26 AM, Hervé BOUTEMY herve.bout...@free.fr wrote: there were a lot of manual tasks that took hours, really many hours (the night was shorter than expected), even more for Mark than for me: it's great to see that the result is positive = you can continue to work on the issues but everything didn't go as expected regarding accounts: please report any problem to INFRA-9389 [1] with precise info regarding usernames at Codehaus and at ASF Thank you Ben for all the Codehaus support, and big big big thank you to Mark at ASF infra for the huge work on import. Regards, Hervé [1] https://issues.apache.org/jira/browse/INFRA-9389 Le lundi 6 avril 2015 11:55:01 Robert Scholte a écrit : I would like to take this chance to give huge kudo's to all involved parties. My first impression is that the migration went very well, since I can continue my work at https://issues.apache.org/jira as I was used to. The preparations already showed that it was more than a simple copy. It was a huge move and not everything could be automated (e.g. making all 60+ Jira projects read-only at Codehaus) but the end result is great. Thanks a lot Hervé, ASF Infra and Codehaus Support! Op Sat, 04 Apr 2015 23:10:55 +0200 schreef Hervé BOUTEMY herve.bout...@free.fr: Hi, Codehaus was put read-only during migration, when we started by doing a dump of the content. Import at ASF is not one yet: should be done tomorrow. You just have to way for 24 hours that the migration is done :) Regards, Hervé Le samedi 4 avril 2015 14:03:43 Tibor Digana a écrit : Hello guys, I am not able to find https://issues.apache.org/jira/browse/SUREFIRE I am not able to manage the issues at Codehaus either ASF. What can we do about that? Cheers Tibor -- View this message in context: http://maven.40175.n5.nabble.com/IMPORTANT-NOTICE-Jira-migration-fro m-Cod eh aus-to-Apache-on-April-4th-tp5830262p5831520.html Sent from the Maven Developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [IMPORTANT NOTICE] Jira migration from Codehaus to Apache on April 4th
Hi, I already am in the group maven-developers, but I don't seem to be able to do anything meaningfull, like managing versions or assigning issues to myself... I checked in SUREFIRE and in MECLIPSE. Is there some part missing in the config? Thanks, Andreas 2015-04-10 23:23 GMT+02:00 Dan Tran dant...@gmail.com: Hi Please add me as well Thanks -D On Fri, Apr 10, 2015 at 1:59 PM, Hervé BOUTEMY herve.bout...@free.fr wrote: I added you to the last request for maven-developers group https://issues.apache.org/jira/browse/INFRA-9422 Regards, Hervé Le vendredi 10 avril 2015 22:20:30 Mirko Friedenhagen a écrit : Hello, now I tried to assign https://issues.apache.org/jira/browse/MRELEASE-901 to myself and was unable to do so. However I was allowed to resolve the issue (and could close it as well). When going to my profile (https://issues.apache.org/jira/secure/ViewProfile.jspa) I see that I am only in the group jira-users and not in any other group (so is Robert Scholte btw, but he has assigned issues). Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen) https://bitbucket.org/mfriedenhagen/ On Tue, Apr 7, 2015 at 7:43 AM, Kristian Rosenvold kristian.rosenv...@gmail.com wrote: The user name mapping seems to be ok, but I seem to be missing permissions to do anything sensible at all ? (krosenvold) Kristian 2015-04-06 23:58 GMT+02:00 Mirko Friedenhagen mfriedenha...@gmail.com : A big thank you from my side as well, I logged in to https://issues.apache.org/jira/ and was easily able to see all my reported issues and am allowed to edit the open ones. Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen ) https://bitbucket.org/mfriedenhagen/ On Mon, Apr 6, 2015 at 2:29 PM, Jason van Zyl ja...@takari.io wrote: The mapping did not work for my user as all issues that were assigned to jason on the Codehaus side are now mapping to Jason Lane. I also can no longer even log into issues.apache.org to comment on INFRA-9389. My codehaus user is jason, and my Apache user is jvanzyl. I lined up all my email addresses but only did so 3 hours before the migration so maybe that is the issue. But I've lost all access to the Apache JIRA instance all together and all my issues are assigned to someone else completely. On Apr 6, 2015, at 6:26 AM, Hervé BOUTEMY herve.bout...@free.fr wrote: there were a lot of manual tasks that took hours, really many hours (the night was shorter than expected), even more for Mark than for me: it's great to see that the result is positive = you can continue to work on the issues but everything didn't go as expected regarding accounts: please report any problem to INFRA-9389 [1] with precise info regarding usernames at Codehaus and at ASF Thank you Ben for all the Codehaus support, and big big big thank you to Mark at ASF infra for the huge work on import. Regards, Hervé [1] https://issues.apache.org/jira/browse/INFRA-9389 Le lundi 6 avril 2015 11:55:01 Robert Scholte a écrit : I would like to take this chance to give huge kudo's to all involved parties. My first impression is that the migration went very well, since I can continue my work at https://issues.apache.org/jira as I was used to. The preparations already showed that it was more than a simple copy. It was a huge move and not everything could be automated (e.g. making all 60+ Jira projects read-only at Codehaus) but the end result is great. Thanks a lot Hervé, ASF Infra and Codehaus Support! Op Sat, 04 Apr 2015 23:10:55 +0200 schreef Hervé BOUTEMY herve.bout...@free.fr: Hi, Codehaus was put read-only during migration, when we started by doing a dump of the content. Import at ASF is not one yet: should be done tomorrow. You just have to way for 24 hours that the migration is done :) Regards, Hervé Le samedi 4 avril 2015 14:03:43 Tibor Digana a écrit : Hello guys, I am not able to find https://issues.apache.org/jira/browse/SUREFIRE I am not able to manage the issues at Codehaus either ASF. What can we do about that? Cheers Tibor -- View this message in context: http://maven.40175.n5.nabble.com/IMPORTANT-NOTICE-Jira-migration-fro m-Cod eh aus-to-Apache-on-April-4th-tp5830262p5831520.html Sent from the Maven Developers mailing list archive at Nabble.com. - To unsubscribe, e-mail:
Re: [IMPORTANT NOTICE] Jira migration from Codehaus to Apache on April 4th
And please add me as well. id is jeffjensen Thank you. On Fri, Apr 10, 2015 at 4:23 PM, Dan Tran dant...@gmail.com wrote: Hi Please add me as well Thanks -D On Fri, Apr 10, 2015 at 1:59 PM, Hervé BOUTEMY herve.bout...@free.fr wrote: I added you to the last request for maven-developers group https://issues.apache.org/jira/browse/INFRA-9422 Regards, Hervé Le vendredi 10 avril 2015 22:20:30 Mirko Friedenhagen a écrit : Hello, now I tried to assign https://issues.apache.org/jira/browse/MRELEASE-901 to myself and was unable to do so. However I was allowed to resolve the issue (and could close it as well). When going to my profile (https://issues.apache.org/jira/secure/ViewProfile.jspa) I see that I am only in the group jira-users and not in any other group (so is Robert Scholte btw, but he has assigned issues). Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen) https://bitbucket.org/mfriedenhagen/ On Tue, Apr 7, 2015 at 7:43 AM, Kristian Rosenvold kristian.rosenv...@gmail.com wrote: The user name mapping seems to be ok, but I seem to be missing permissions to do anything sensible at all ? (krosenvold) Kristian 2015-04-06 23:58 GMT+02:00 Mirko Friedenhagen mfriedenha...@gmail.com : A big thank you from my side as well, I logged in to https://issues.apache.org/jira/ and was easily able to see all my reported issues and am allowed to edit the open ones. Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen ) https://bitbucket.org/mfriedenhagen/ On Mon, Apr 6, 2015 at 2:29 PM, Jason van Zyl ja...@takari.io wrote: The mapping did not work for my user as all issues that were assigned to jason on the Codehaus side are now mapping to Jason Lane. I also can no longer even log into issues.apache.org to comment on INFRA-9389. My codehaus user is jason, and my Apache user is jvanzyl. I lined up all my email addresses but only did so 3 hours before the migration so maybe that is the issue. But I've lost all access to the Apache JIRA instance all together and all my issues are assigned to someone else completely. On Apr 6, 2015, at 6:26 AM, Hervé BOUTEMY herve.bout...@free.fr wrote: there were a lot of manual tasks that took hours, really many hours (the night was shorter than expected), even more for Mark than for me: it's great to see that the result is positive = you can continue to work on the issues but everything didn't go as expected regarding accounts: please report any problem to INFRA-9389 [1] with precise info regarding usernames at Codehaus and at ASF Thank you Ben for all the Codehaus support, and big big big thank you to Mark at ASF infra for the huge work on import. Regards, Hervé [1] https://issues.apache.org/jira/browse/INFRA-9389 Le lundi 6 avril 2015 11:55:01 Robert Scholte a écrit : I would like to take this chance to give huge kudo's to all involved parties. My first impression is that the migration went very well, since I can continue my work at https://issues.apache.org/jira as I was used to. The preparations already showed that it was more than a simple copy. It was a huge move and not everything could be automated (e.g. making all 60+ Jira projects read-only at Codehaus) but the end result is great. Thanks a lot Hervé, ASF Infra and Codehaus Support! Op Sat, 04 Apr 2015 23:10:55 +0200 schreef Hervé BOUTEMY herve.bout...@free.fr: Hi, Codehaus was put read-only during migration, when we started by doing a dump of the content. Import at ASF is not one yet: should be done tomorrow. You just have to way for 24 hours that the migration is done :) Regards, Hervé Le samedi 4 avril 2015 14:03:43 Tibor Digana a écrit : Hello guys, I am not able to find https://issues.apache.org/jira/browse/SUREFIRE I am not able to manage the issues at Codehaus either ASF. What can we do about that? Cheers Tibor -- View this message in context: http://maven.40175.n5.nabble.com/IMPORTANT-NOTICE-Jira-migration-fro m-Cod eh aus-to-Apache-on-April-4th-tp5830262p5831520.html Sent from the Maven Developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail:
Re: [IMPORTANT NOTICE] Jira migration from Codehaus to Apache on April 4th
Hi, Dan and Andreas, you're in maven-developers groups = what is expected Then if you can't do anything useful, yes, there is some part missing in the config: we'll need to figure out which one :) Currently, the pattern applied to the Maven projects regarding roles is: - role Administrators = maven-administrators - role Developers = maven-developers which seems logical looking at Permissions, I see that most permissions are set on PMC and Committers roles, but absolutely no permission is set on Developers role: I thing it is the problem! To test another config on one project before doing it on every other, let's try on SUREFIRE: I just configured role PMC for maven-administrators and role Committers for maven-developers Can you check what actions this lets you do and if somthing is still missing, please? Regards Hervé Le vendredi 10 avril 2015 23:34:49 Andreas Gudian a écrit : Hi, I already am in the group maven-developers, but I don't seem to be able to do anything meaningfull, like managing versions or assigning issues to myself... I checked in SUREFIRE and in MECLIPSE. Is there some part missing in the config? Thanks, Andreas 2015-04-10 23:23 GMT+02:00 Dan Tran dant...@gmail.com: Hi Please add me as well Thanks -D On Fri, Apr 10, 2015 at 1:59 PM, Hervé BOUTEMY herve.bout...@free.fr wrote: I added you to the last request for maven-developers group https://issues.apache.org/jira/browse/INFRA-9422 Regards, Hervé Le vendredi 10 avril 2015 22:20:30 Mirko Friedenhagen a écrit : Hello, now I tried to assign https://issues.apache.org/jira/browse/MRELEASE-901 to myself and was unable to do so. However I was allowed to resolve the issue (and could close it as well). When going to my profile (https://issues.apache.org/jira/secure/ViewProfile.jspa) I see that I am only in the group jira-users and not in any other group (so is Robert Scholte btw, but he has assigned issues). Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen) https://bitbucket.org/mfriedenhagen/ On Tue, Apr 7, 2015 at 7:43 AM, Kristian Rosenvold kristian.rosenv...@gmail.com wrote: The user name mapping seems to be ok, but I seem to be missing permissions to do anything sensible at all ? (krosenvold) Kristian 2015-04-06 23:58 GMT+02:00 Mirko Friedenhagen mfriedenha...@gmail.com A big thank you from my side as well, I logged in to https://issues.apache.org/jira/ and was easily able to see all my reported issues and am allowed to edit the open ones. Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen ) https://bitbucket.org/mfriedenhagen/ On Mon, Apr 6, 2015 at 2:29 PM, Jason van Zyl ja...@takari.io wrote: The mapping did not work for my user as all issues that were assigned to jason on the Codehaus side are now mapping to Jason Lane. I also can no longer even log into issues.apache.org to comment on INFRA-9389. My codehaus user is jason, and my Apache user is jvanzyl. I lined up all my email addresses but only did so 3 hours before the migration so maybe that is the issue. But I've lost all access to the Apache JIRA instance all together and all my issues are assigned to someone else completely. On Apr 6, 2015, at 6:26 AM, Hervé BOUTEMY herve.bout...@free.fr wrote: there were a lot of manual tasks that took hours, really many hours (the night was shorter than expected), even more for Mark than for me: it's great to see that the result is positive = you can continue to work on the issues but everything didn't go as expected regarding accounts: please report any problem to INFRA-9389 [1] with precise info regarding usernames at Codehaus and at ASF Thank you Ben for all the Codehaus support, and big big big thank you to Mark at ASF infra for the huge work on import. Regards, Hervé [1] https://issues.apache.org/jira/browse/INFRA-9389 Le lundi 6 avril 2015 11:55:01 Robert Scholte a écrit : I would like to take this chance to give huge kudo's to all involved parties. My first impression is that the migration went very well, since I can continue my work at https://issues.apache.org/jira as I was used to. The preparations already showed that it was more than a simple copy. It was a huge move and not everything could be automated (e.g. making all
Re: [IMPORTANT NOTICE] Jira migration from Codehaus to Apache on April 4th
A big thank you from my side as well, I logged in to https://issues.apache.org/jira/ and was easily able to see all my reported issues and am allowed to edit the open ones. Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen) https://bitbucket.org/mfriedenhagen/ On Mon, Apr 6, 2015 at 2:29 PM, Jason van Zyl ja...@takari.io wrote: The mapping did not work for my user as all issues that were assigned to jason on the Codehaus side are now mapping to Jason Lane. I also can no longer even log into issues.apache.org to comment on INFRA-9389. My codehaus user is jason, and my Apache user is jvanzyl. I lined up all my email addresses but only did so 3 hours before the migration so maybe that is the issue. But I've lost all access to the Apache JIRA instance all together and all my issues are assigned to someone else completely. On Apr 6, 2015, at 6:26 AM, Hervé BOUTEMY herve.bout...@free.fr wrote: there were a lot of manual tasks that took hours, really many hours (the night was shorter than expected), even more for Mark than for me: it's great to see that the result is positive = you can continue to work on the issues but everything didn't go as expected regarding accounts: please report any problem to INFRA-9389 [1] with precise info regarding usernames at Codehaus and at ASF Thank you Ben for all the Codehaus support, and big big big thank you to Mark at ASF infra for the huge work on import. Regards, Hervé [1] https://issues.apache.org/jira/browse/INFRA-9389 Le lundi 6 avril 2015 11:55:01 Robert Scholte a écrit : I would like to take this chance to give huge kudo's to all involved parties. My first impression is that the migration went very well, since I can continue my work at https://issues.apache.org/jira as I was used to. The preparations already showed that it was more than a simple copy. It was a huge move and not everything could be automated (e.g. making all 60+ Jira projects read-only at Codehaus) but the end result is great. Thanks a lot Hervé, ASF Infra and Codehaus Support! Op Sat, 04 Apr 2015 23:10:55 +0200 schreef Hervé BOUTEMY herve.bout...@free.fr: Hi, Codehaus was put read-only during migration, when we started by doing a dump of the content. Import at ASF is not one yet: should be done tomorrow. You just have to way for 24 hours that the migration is done :) Regards, Hervé Le samedi 4 avril 2015 14:03:43 Tibor Digana a écrit : Hello guys, I am not able to find https://issues.apache.org/jira/browse/SUREFIRE I am not able to manage the issues at Codehaus either ASF. What can we do about that? Cheers Tibor -- View this message in context: http://maven.40175.n5.nabble.com/IMPORTANT-NOTICE-Jira-migration-from-Cod eh aus-to-Apache-on-April-4th-tp5830262p5831520.html Sent from the Maven Developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Takari and Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io - In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [IMPORTANT NOTICE] Jira migration from Codehaus to Apache on April 4th
The user name mapping seems to be ok, but I seem to be missing permissions to do anything sensible at all ? (krosenvold) Kristian 2015-04-06 23:58 GMT+02:00 Mirko Friedenhagen mfriedenha...@gmail.com: A big thank you from my side as well, I logged in to https://issues.apache.org/jira/ and was easily able to see all my reported issues and am allowed to edit the open ones. Regards Mirko -- http://illegalstateexception.blogspot.com/ https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen) https://bitbucket.org/mfriedenhagen/ On Mon, Apr 6, 2015 at 2:29 PM, Jason van Zyl ja...@takari.io wrote: The mapping did not work for my user as all issues that were assigned to jason on the Codehaus side are now mapping to Jason Lane. I also can no longer even log into issues.apache.org to comment on INFRA-9389. My codehaus user is jason, and my Apache user is jvanzyl. I lined up all my email addresses but only did so 3 hours before the migration so maybe that is the issue. But I've lost all access to the Apache JIRA instance all together and all my issues are assigned to someone else completely. On Apr 6, 2015, at 6:26 AM, Hervé BOUTEMY herve.bout...@free.fr wrote: there were a lot of manual tasks that took hours, really many hours (the night was shorter than expected), even more for Mark than for me: it's great to see that the result is positive = you can continue to work on the issues but everything didn't go as expected regarding accounts: please report any problem to INFRA-9389 [1] with precise info regarding usernames at Codehaus and at ASF Thank you Ben for all the Codehaus support, and big big big thank you to Mark at ASF infra for the huge work on import. Regards, Hervé [1] https://issues.apache.org/jira/browse/INFRA-9389 Le lundi 6 avril 2015 11:55:01 Robert Scholte a écrit : I would like to take this chance to give huge kudo's to all involved parties. My first impression is that the migration went very well, since I can continue my work at https://issues.apache.org/jira as I was used to. The preparations already showed that it was more than a simple copy. It was a huge move and not everything could be automated (e.g. making all 60+ Jira projects read-only at Codehaus) but the end result is great. Thanks a lot Hervé, ASF Infra and Codehaus Support! Op Sat, 04 Apr 2015 23:10:55 +0200 schreef Hervé BOUTEMY herve.bout...@free.fr: Hi, Codehaus was put read-only during migration, when we started by doing a dump of the content. Import at ASF is not one yet: should be done tomorrow. You just have to way for 24 hours that the migration is done :) Regards, Hervé Le samedi 4 avril 2015 14:03:43 Tibor Digana a écrit : Hello guys, I am not able to find https://issues.apache.org/jira/browse/SUREFIRE I am not able to manage the issues at Codehaus either ASF. What can we do about that? Cheers Tibor -- View this message in context: http://maven.40175.n5.nabble.com/IMPORTANT-NOTICE-Jira-migration-from-Cod eh aus-to-Apache-on-April-4th-tp5830262p5831520.html Sent from the Maven Developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Takari and Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io - In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [IMPORTANT NOTICE] Jira migration from Codehaus to Apache on April 4th
Thx for moving SUREFIRE in https://issues.apache.org/jira. I can login as tibor17, but I do not have rights to modify the issue milestones as it seems. The Apache login does not work for me. Is the migration in progress, or should I create a new login? -- View this message in context: http://maven.40175.n5.nabble.com/IMPORTANT-NOTICE-Jira-migration-from-Codehaus-to-Apache-on-April-4th-tp5830262p5831775.html Sent from the Maven Developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [IMPORTANT NOTICE] Jira migration from Codehaus to Apache on April 4th
I would like to take this chance to give huge kudo's to all involved parties. My first impression is that the migration went very well, since I can continue my work at https://issues.apache.org/jira as I was used to. The preparations already showed that it was more than a simple copy. It was a huge move and not everything could be automated (e.g. making all 60+ Jira projects read-only at Codehaus) but the end result is great. Thanks a lot Hervé, ASF Infra and Codehaus Support! Op Sat, 04 Apr 2015 23:10:55 +0200 schreef Hervé BOUTEMY herve.bout...@free.fr: Hi, Codehaus was put read-only during migration, when we started by doing a dump of the content. Import at ASF is not one yet: should be done tomorrow. You just have to way for 24 hours that the migration is done :) Regards, Hervé Le samedi 4 avril 2015 14:03:43 Tibor Digana a écrit : Hello guys, I am not able to find https://issues.apache.org/jira/browse/SUREFIRE I am not able to manage the issues at Codehaus either ASF. What can we do about that? Cheers Tibor -- View this message in context: http://maven.40175.n5.nabble.com/IMPORTANT-NOTICE-Jira-migration-from-Codeh aus-to-Apache-on-April-4th-tp5830262p5831520.html Sent from the Maven Developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [IMPORTANT NOTICE] Jira migration from Codehaus to Apache on April 4th
Hi, I would like to take this chance to give huge kudo's to all involved parties. My first impression is that the migration went very well, since I can continue my work at https://issues.apache.org/jira as I was used to. The preparations already showed that it was more than a simple copy. It was a huge move and not everything could be automated (e.g. making all 60+ Jira projects read-only at Codehaus) but the end result is great. Thanks a lot Hervé, ASF Infra and Codehaus Support! Big applaus für ASF Infra, Hervé and Codehaus Support... https://twitter.com/khmarbaise/status/584992997739200512 from me as well... Many thanks Kind regards Karl Heinz Marbaise Op Sat, 04 Apr 2015 23:10:55 +0200 schreef Hervé BOUTEMY herve.bout...@free.fr: Hi, Codehaus was put read-only during migration, when we started by doing a dump of the content. Import at ASF is not one yet: should be done tomorrow. You just have to way for 24 hours that the migration is done :) Regards, Hervé Le samedi 4 avril 2015 14:03:43 Tibor Digana a écrit : Hello guys, I am not able to find https://issues.apache.org/jira/browse/SUREFIRE I am not able to manage the issues at Codehaus either ASF. What can we do about that? Cheers Tibor - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [IMPORTANT NOTICE] Jira migration from Codehaus to Apache on April 4th
there were a lot of manual tasks that took hours, really many hours (the night was shorter than expected), even more for Mark than for me: it's great to see that the result is positive = you can continue to work on the issues but everything didn't go as expected regarding accounts: please report any problem to INFRA-9389 [1] with precise info regarding usernames at Codehaus and at ASF Thank you Ben for all the Codehaus support, and big big big thank you to Mark at ASF infra for the huge work on import. Regards, Hervé [1] https://issues.apache.org/jira/browse/INFRA-9389 Le lundi 6 avril 2015 11:55:01 Robert Scholte a écrit : I would like to take this chance to give huge kudo's to all involved parties. My first impression is that the migration went very well, since I can continue my work at https://issues.apache.org/jira as I was used to. The preparations already showed that it was more than a simple copy. It was a huge move and not everything could be automated (e.g. making all 60+ Jira projects read-only at Codehaus) but the end result is great. Thanks a lot Hervé, ASF Infra and Codehaus Support! Op Sat, 04 Apr 2015 23:10:55 +0200 schreef Hervé BOUTEMY herve.bout...@free.fr: Hi, Codehaus was put read-only during migration, when we started by doing a dump of the content. Import at ASF is not one yet: should be done tomorrow. You just have to way for 24 hours that the migration is done :) Regards, Hervé Le samedi 4 avril 2015 14:03:43 Tibor Digana a écrit : Hello guys, I am not able to find https://issues.apache.org/jira/browse/SUREFIRE I am not able to manage the issues at Codehaus either ASF. What can we do about that? Cheers Tibor -- View this message in context: http://maven.40175.n5.nabble.com/IMPORTANT-NOTICE-Jira-migration-from-Cod eh aus-to-Apache-on-April-4th-tp5830262p5831520.html Sent from the Maven Developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [IMPORTANT NOTICE] Jira migration from Codehaus to Apache on April 4th
The mapping did not work for my user as all issues that were assigned to jason on the Codehaus side are now mapping to Jason Lane. I also can no longer even log into issues.apache.org to comment on INFRA-9389. My codehaus user is jason, and my Apache user is jvanzyl. I lined up all my email addresses but only did so 3 hours before the migration so maybe that is the issue. But I've lost all access to the Apache JIRA instance all together and all my issues are assigned to someone else completely. On Apr 6, 2015, at 6:26 AM, Hervé BOUTEMY herve.bout...@free.fr wrote: there were a lot of manual tasks that took hours, really many hours (the night was shorter than expected), even more for Mark than for me: it's great to see that the result is positive = you can continue to work on the issues but everything didn't go as expected regarding accounts: please report any problem to INFRA-9389 [1] with precise info regarding usernames at Codehaus and at ASF Thank you Ben for all the Codehaus support, and big big big thank you to Mark at ASF infra for the huge work on import. Regards, Hervé [1] https://issues.apache.org/jira/browse/INFRA-9389 Le lundi 6 avril 2015 11:55:01 Robert Scholte a écrit : I would like to take this chance to give huge kudo's to all involved parties. My first impression is that the migration went very well, since I can continue my work at https://issues.apache.org/jira as I was used to. The preparations already showed that it was more than a simple copy. It was a huge move and not everything could be automated (e.g. making all 60+ Jira projects read-only at Codehaus) but the end result is great. Thanks a lot Hervé, ASF Infra and Codehaus Support! Op Sat, 04 Apr 2015 23:10:55 +0200 schreef Hervé BOUTEMY herve.bout...@free.fr: Hi, Codehaus was put read-only during migration, when we started by doing a dump of the content. Import at ASF is not one yet: should be done tomorrow. You just have to way for 24 hours that the migration is done :) Regards, Hervé Le samedi 4 avril 2015 14:03:43 Tibor Digana a écrit : Hello guys, I am not able to find https://issues.apache.org/jira/browse/SUREFIRE I am not able to manage the issues at Codehaus either ASF. What can we do about that? Cheers Tibor -- View this message in context: http://maven.40175.n5.nabble.com/IMPORTANT-NOTICE-Jira-migration-from-Cod eh aus-to-Apache-on-April-4th-tp5830262p5831520.html Sent from the Maven Developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Takari and Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io - In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [IMPORTANT NOTICE] Jira migration from Codehaus to Apache on April 4th
Hi, Codehaus was put read-only during migration, when we started by doing a dump of the content. Import at ASF is not one yet: should be done tomorrow. You just have to way for 24 hours that the migration is done :) Regards, Hervé Le samedi 4 avril 2015 14:03:43 Tibor Digana a écrit : Hello guys, I am not able to find https://issues.apache.org/jira/browse/SUREFIRE I am not able to manage the issues at Codehaus either ASF. What can we do about that? Cheers Tibor -- View this message in context: http://maven.40175.n5.nabble.com/IMPORTANT-NOTICE-Jira-migration-from-Codeh aus-to-Apache-on-April-4th-tp5830262p5831520.html Sent from the Maven Developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [IMPORTANT NOTICE] Jira migration from Codehaus to Apache on April 4th
Thank you Herve. I am glad to hear that migration is in the right hands :) Cheers Tibor -- View this message in context: http://maven.40175.n5.nabble.com/IMPORTANT-NOTICE-Jira-migration-from-Codehaus-to-Apache-on-April-4th-tp5830262p5831532.html Sent from the Maven Developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [IMPORTANT NOTICE] Jira migration from Codehaus to Apache on April 4th
Hello guys, I am not able to find https://issues.apache.org/jira/browse/SUREFIRE I am not able to manage the issues at Codehaus either ASF. What can we do about that? Cheers Tibor -- View this message in context: http://maven.40175.n5.nabble.com/IMPORTANT-NOTICE-Jira-migration-from-Codehaus-to-Apache-on-April-4th-tp5830262p5831520.html Sent from the Maven Developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [IMPORTANT NOTICE] Jira migration from Codehaus to Apache on April 4th
Hi Hervé should the same process be done for archiva continuum and groovy ? Regards Eric Le Vendredi 3 Avril 2015 08:37 CEST, Hervé BOUTEMY herve.bout...@free.fr a écrit: Hi Maven devs, After Jira migration to ASF, we'll need to create groups to give required privileged access to issues to the team. We need to know the Jira username of everybody, which unfortunately is not required to be the same as your Apache id. I started the list in http://svn.apache.org/r1670998 Please update your Jira username. Thank you Hervé Le vendredi 3 avril 2015 08:17:37 Hervé Boutemy a écrit : The migration will start in 12h: every Jira project at Codehaus to be migrated to ASF will be marked read-only Remember to check your Jira account email settings both at Codehaus and ASF if you want to be sure of the result at ASF. And everything is tracked at https://issues.apache.org/jira/browse/INFRA-9116 -The Apache Maven team Le mardi 31 mars 2015 23:24:21 Hervé BOUTEMY a écrit : Hi, Schedule confirmed: 20150403-2000 UTC = projects freeze in Codehaus 20150405 = projects available in ASF Don't forget to check account emails if you already have an account at ASF -The Apache Maven team Le mercredi 25 mars 2015 03:44:07 Hervé Boutemy a écrit : Hi, As announced in our quarterly report from january, we were studying Jira migration from Codehaus to Apache: the migration will happen during the week- end of April 4th. We'll create the exact same Jira projects at ASF than what we have at Codehaus, copy the whole content and mark Codehaus read-only. See https://issues.apache.org/jira/browse/INFRA-9116 for exact list. For example, it was done a few years ago with (near empty) MPOM, which was moved from http://jira.codehaus.org/browse/MPOM to https://issues.apache.org/jira/browse/MPOM How will username migration from Codehaus to ASF happen? When migrating existing content, user accounts will be migrated too (that's the way Jira works). To avoid creating accounts that already exist at Apache, matching will be done on account's e-mail address. The mapping will look something like: for each e-mail/username pair in the Codehaus content if the email is associated with a user in the ASF Jira instance, reuse: update the username from imported content to the ASF username else we'll create a new account in the ASF Jira instance: if the username already exists in the ASF Jira instance (another email) update the imported username to append -[SUFFIX] to the end else use the imported username/email as is The exact [SUFFIX] still needs to be defined. If you want to be sure of your username at Apache Jira, please take a look at your e-mail at Codehaus and check that it matches the e-mail at your Apache Jira account. If you have any question, don't hesitate to ask. We'll keep you informed as the operation is planned more in details. -The Apache Maven team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [IMPORTANT NOTICE] Jira migration from Codehaus to Apache on April 4th
The migration will start in 12h: every Jira project at Codehaus to be migrated to ASF will be marked read-only Remember to check your Jira account email settings both at Codehaus and ASF if you want to be sure of the result at ASF. And everything is tracked at https://issues.apache.org/jira/browse/INFRA-9116 -The Apache Maven team Le mardi 31 mars 2015 23:24:21 Hervé BOUTEMY a écrit : Hi, Schedule confirmed: 20150403-2000 UTC = projects freeze in Codehaus 20150405 = projects available in ASF Don't forget to check account emails if you already have an account at ASF -The Apache Maven team Le mercredi 25 mars 2015 03:44:07 Hervé Boutemy a écrit : Hi, As announced in our quarterly report from january, we were studying Jira migration from Codehaus to Apache: the migration will happen during the week- end of April 4th. We'll create the exact same Jira projects at ASF than what we have at Codehaus, copy the whole content and mark Codehaus read-only. See https://issues.apache.org/jira/browse/INFRA-9116 for exact list. For example, it was done a few years ago with (near empty) MPOM, which was moved from http://jira.codehaus.org/browse/MPOM to https://issues.apache.org/jira/browse/MPOM How will username migration from Codehaus to ASF happen? When migrating existing content, user accounts will be migrated too (that's the way Jira works). To avoid creating accounts that already exist at Apache, matching will be done on account's e-mail address. The mapping will look something like: for each e-mail/username pair in the Codehaus content if the email is associated with a user in the ASF Jira instance, reuse: update the username from imported content to the ASF username else we'll create a new account in the ASF Jira instance: if the username already exists in the ASF Jira instance (another email) update the imported username to append -[SUFFIX] to the end else use the imported username/email as is The exact [SUFFIX] still needs to be defined. If you want to be sure of your username at Apache Jira, please take a look at your e-mail at Codehaus and check that it matches the e-mail at your Apache Jira account. If you have any question, don't hesitate to ask. We'll keep you informed as the operation is planned more in details. -The Apache Maven team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [IMPORTANT NOTICE] Jira migration from Codehaus to Apache on April 4th
@Eric, The Archiva import is more simple as it's only one project compared to all Maven projects. But good to know what is your asf jira id. (very simple if it's the same) On 3 April 2015 at 18:42, Eric Barboni eric.barb...@irit.fr wrote: Hi Hervé should the same process be done for archiva continuum and groovy ? Regards Eric Le Vendredi 3 Avril 2015 08:37 CEST, Hervé BOUTEMY herve.bout...@free.fr a écrit: Hi Maven devs, After Jira migration to ASF, we'll need to create groups to give required privileged access to issues to the team. We need to know the Jira username of everybody, which unfortunately is not required to be the same as your Apache id. I started the list in http://svn.apache.org/r1670998 Please update your Jira username. Thank you Hervé Le vendredi 3 avril 2015 08:17:37 Hervé Boutemy a écrit : The migration will start in 12h: every Jira project at Codehaus to be migrated to ASF will be marked read-only Remember to check your Jira account email settings both at Codehaus and ASF if you want to be sure of the result at ASF. And everything is tracked at https://issues.apache.org/jira/browse/INFRA-9116 -The Apache Maven team Le mardi 31 mars 2015 23:24:21 Hervé BOUTEMY a écrit : Hi, Schedule confirmed: 20150403-2000 UTC = projects freeze in Codehaus 20150405 = projects available in ASF Don't forget to check account emails if you already have an account at ASF -The Apache Maven team Le mercredi 25 mars 2015 03:44:07 Hervé Boutemy a écrit : Hi, As announced in our quarterly report from january, we were studying Jira migration from Codehaus to Apache: the migration will happen during the week- end of April 4th. We'll create the exact same Jira projects at ASF than what we have at Codehaus, copy the whole content and mark Codehaus read-only. See https://issues.apache.org/jira/browse/INFRA-9116 for exact list. For example, it was done a few years ago with (near empty) MPOM, which was moved from http://jira.codehaus.org/browse/MPOM to https://issues.apache.org/jira/browse/MPOM How will username migration from Codehaus to ASF happen? When migrating existing content, user accounts will be migrated too (that's the way Jira works). To avoid creating accounts that already exist at Apache, matching will be done on account's e-mail address. The mapping will look something like: for each e-mail/username pair in the Codehaus content if the email is associated with a user in the ASF Jira instance, reuse: update the username from imported content to the ASF username else we'll create a new account in the ASF Jira instance: if the username already exists in the ASF Jira instance (another email) update the imported username to append -[SUFFIX] to the end else use the imported username/email as is The exact [SUFFIX] still needs to be defined. If you want to be sure of your username at Apache Jira, please take a look at your e-mail at Codehaus and check that it matches the e-mail at your Apache Jira account. If you have any question, don't hesitate to ask. We'll keep you informed as the operation is planned more in details. -The Apache Maven team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: [IMPORTANT NOTICE] Jira migration from Codehaus to Apache on April 4th
Hi Maven devs, After Jira migration to ASF, we'll need to create groups to give required privileged access to issues to the team. We need to know the Jira username of everybody, which unfortunately is not required to be the same as your Apache id. I started the list in http://svn.apache.org/r1670998 Please update your Jira username. Thank you Hervé Le vendredi 3 avril 2015 08:17:37 Hervé Boutemy a écrit : The migration will start in 12h: every Jira project at Codehaus to be migrated to ASF will be marked read-only Remember to check your Jira account email settings both at Codehaus and ASF if you want to be sure of the result at ASF. And everything is tracked at https://issues.apache.org/jira/browse/INFRA-9116 -The Apache Maven team Le mardi 31 mars 2015 23:24:21 Hervé BOUTEMY a écrit : Hi, Schedule confirmed: 20150403-2000 UTC = projects freeze in Codehaus 20150405 = projects available in ASF Don't forget to check account emails if you already have an account at ASF -The Apache Maven team Le mercredi 25 mars 2015 03:44:07 Hervé Boutemy a écrit : Hi, As announced in our quarterly report from january, we were studying Jira migration from Codehaus to Apache: the migration will happen during the week- end of April 4th. We'll create the exact same Jira projects at ASF than what we have at Codehaus, copy the whole content and mark Codehaus read-only. See https://issues.apache.org/jira/browse/INFRA-9116 for exact list. For example, it was done a few years ago with (near empty) MPOM, which was moved from http://jira.codehaus.org/browse/MPOM to https://issues.apache.org/jira/browse/MPOM How will username migration from Codehaus to ASF happen? When migrating existing content, user accounts will be migrated too (that's the way Jira works). To avoid creating accounts that already exist at Apache, matching will be done on account's e-mail address. The mapping will look something like: for each e-mail/username pair in the Codehaus content if the email is associated with a user in the ASF Jira instance, reuse: update the username from imported content to the ASF username else we'll create a new account in the ASF Jira instance: if the username already exists in the ASF Jira instance (another email) update the imported username to append -[SUFFIX] to the end else use the imported username/email as is The exact [SUFFIX] still needs to be defined. If you want to be sure of your username at Apache Jira, please take a look at your e-mail at Codehaus and check that it matches the e-mail at your Apache Jira account. If you have any question, don't hesitate to ask. We'll keep you informed as the operation is planned more in details. -The Apache Maven team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [IMPORTANT NOTICE] Jira migration from Codehaus to Apache on April 4th
@Eric, Codehaus is shutting down: read https://codehaus.org/. So the answer is yes. And there's not much time left. Cheers 2015-04-03 9:42 GMT+02:00 Eric Barboni eric.barb...@irit.fr: Hi Hervé should the same process be done for archiva continuum and groovy ? Regards Eric Le Vendredi 3 Avril 2015 08:37 CEST, Hervé BOUTEMY herve.bout...@free.fr a écrit: Hi Maven devs, After Jira migration to ASF, we'll need to create groups to give required privileged access to issues to the team. We need to know the Jira username of everybody, which unfortunately is not required to be the same as your Apache id. I started the list in http://svn.apache.org/r1670998 Please update your Jira username. Thank you Hervé Le vendredi 3 avril 2015 08:17:37 Hervé Boutemy a écrit : The migration will start in 12h: every Jira project at Codehaus to be migrated to ASF will be marked read-only Remember to check your Jira account email settings both at Codehaus and ASF if you want to be sure of the result at ASF. And everything is tracked at https://issues.apache.org/jira/browse/INFRA-9116 -The Apache Maven team Le mardi 31 mars 2015 23:24:21 Hervé BOUTEMY a écrit : Hi, Schedule confirmed: 20150403-2000 UTC = projects freeze in Codehaus 20150405 = projects available in ASF Don't forget to check account emails if you already have an account at ASF -The Apache Maven team Le mercredi 25 mars 2015 03:44:07 Hervé Boutemy a écrit : Hi, As announced in our quarterly report from january, we were studying Jira migration from Codehaus to Apache: the migration will happen during the week- end of April 4th. We'll create the exact same Jira projects at ASF than what we have at Codehaus, copy the whole content and mark Codehaus read-only. See https://issues.apache.org/jira/browse/INFRA-9116 for exact list. For example, it was done a few years ago with (near empty) MPOM, which was moved from http://jira.codehaus.org/browse/MPOM to https://issues.apache.org/jira/browse/MPOM How will username migration from Codehaus to ASF happen? When migrating existing content, user accounts will be migrated too (that's the way Jira works). To avoid creating accounts that already exist at Apache, matching will be done on account's e-mail address. The mapping will look something like: for each e-mail/username pair in the Codehaus content if the email is associated with a user in the ASF Jira instance, reuse: update the username from imported content to the ASF username else we'll create a new account in the ASF Jira instance: if the username already exists in the ASF Jira instance (another email) update the imported username to append -[SUFFIX] to the end else use the imported username/email as is The exact [SUFFIX] still needs to be defined. If you want to be sure of your username at Apache Jira, please take a look at your e-mail at Codehaus and check that it matches the e-mail at your Apache Jira account. If you have any question, don't hesitate to ask. We'll keep you informed as the operation is planned more in details. -The Apache Maven team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
Re: [IMPORTANT NOTICE] Jira migration from Codehaus to Apache on April 4th
Archiva, Continuum and Groovy have only 1 Jira project each: creating groups is not useful, since adding someone to the group is equivalent to adding to the project role. Since adding someone to Jira project role can be done by project members, but adding someone to a Jira group will require INFRA to do it, it's advised not to create groups for Archive, Continuum nor Groovy. (for Maven, with 60 Jira projects, we can't avoid it) Regards, Hervé - Mail original - De: Eric Barboni eric.barb...@irit.fr À: Maven Developers List dev@maven.apache.org Envoyé: Vendredi 3 Avril 2015 09:42:54 Objet: Re: [IMPORTANT NOTICE] Jira migration from Codehaus to Apache on April 4th Hi Hervé should the same process be done for archiva continuum and groovy ? Regards Eric Le Vendredi 3 Avril 2015 08:37 CEST, Hervé BOUTEMY herve.bout...@free.fr a écrit: Hi Maven devs, After Jira migration to ASF, we'll need to create groups to give required privileged access to issues to the team. We need to know the Jira username of everybody, which unfortunately is not required to be the same as your Apache id. I started the list in http://svn.apache.org/r1670998 Please update your Jira username. Thank you Hervé Le vendredi 3 avril 2015 08:17:37 Hervé Boutemy a écrit : The migration will start in 12h: every Jira project at Codehaus to be migrated to ASF will be marked read-only Remember to check your Jira account email settings both at Codehaus and ASF if you want to be sure of the result at ASF. And everything is tracked at https://issues.apache.org/jira/browse/INFRA-9116 -The Apache Maven team Le mardi 31 mars 2015 23:24:21 Hervé BOUTEMY a écrit : Hi, Schedule confirmed: 20150403-2000 UTC = projects freeze in Codehaus 20150405 = projects available in ASF Don't forget to check account emails if you already have an account at ASF -The Apache Maven team Le mercredi 25 mars 2015 03:44:07 Hervé Boutemy a écrit : Hi, As announced in our quarterly report from january, we were studying Jira migration from Codehaus to Apache: the migration will happen during the week- end of April 4th. We'll create the exact same Jira projects at ASF than what we have at Codehaus, copy the whole content and mark Codehaus read-only. See https://issues.apache.org/jira/browse/INFRA-9116 for exact list. For example, it was done a few years ago with (near empty) MPOM, which was moved from http://jira.codehaus.org/browse/MPOM to https://issues.apache.org/jira/browse/MPOM How will username migration from Codehaus to ASF happen? When migrating existing content, user accounts will be migrated too (that's the way Jira works). To avoid creating accounts that already exist at Apache, matching will be done on account's e-mail address. The mapping will look something like: for each e-mail/username pair in the Codehaus content if the email is associated with a user in the ASF Jira instance, reuse: update the username from imported content to the ASF username else we'll create a new account in the ASF Jira instance: if the username already exists in the ASF Jira instance (another email) update the imported username to append -[SUFFIX] to the end else use the imported username/email as is The exact [SUFFIX] still needs to be defined. If you want to be sure of your username at Apache Jira, please take a look at your e-mail at Codehaus and check that it matches the e-mail at your Apache Jira account. If you have any question, don't hesitate to ask. We'll keep you informed as the operation is planned more in details. -The Apache Maven team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e
RE: [IMPORTANT NOTICE] Jira migration from Codehaus to Apache on April 4th
Hi, Thanks for precision. Sorry for my previous short message, I thought it was a private reply to Hervé just in case we need for archiva. Wish you all the best during migration!! Fingers crossed Regards, Eric -Message d'origine- De : herve.bout...@free.fr [mailto:herve.bout...@free.fr] Envoyé : vendredi 3 avril 2015 14:07 À : Maven Developers List Objet : Re: [IMPORTANT NOTICE] Jira migration from Codehaus to Apache on April 4th Archiva, Continuum and Groovy have only 1 Jira project each: creating groups is not useful, since adding someone to the group is equivalent to adding to the project role. Since adding someone to Jira project role can be done by project members, but adding someone to a Jira group will require INFRA to do it, it's advised not to create groups for Archive, Continuum nor Groovy. (for Maven, with 60 Jira projects, we can't avoid it) Regards, Hervé - Mail original - De: Eric Barboni eric.barb...@irit.fr À: Maven Developers List dev@maven.apache.org Envoyé: Vendredi 3 Avril 2015 09:42:54 Objet: Re: [IMPORTANT NOTICE] Jira migration from Codehaus to Apache on April 4th Hi Hervé should the same process be done for archiva continuum and groovy ? Regards Eric Le Vendredi 3 Avril 2015 08:37 CEST, Hervé BOUTEMY herve.bout...@free.fr a écrit: Hi Maven devs, After Jira migration to ASF, we'll need to create groups to give required privileged access to issues to the team. We need to know the Jira username of everybody, which unfortunately is not required to be the same as your Apache id. I started the list in http://svn.apache.org/r1670998 Please update your Jira username. Thank you Hervé Le vendredi 3 avril 2015 08:17:37 Hervé Boutemy a écrit : The migration will start in 12h: every Jira project at Codehaus to be migrated to ASF will be marked read-only Remember to check your Jira account email settings both at Codehaus and ASF if you want to be sure of the result at ASF. And everything is tracked at https://issues.apache.org/jira/browse/INFRA-9116 -The Apache Maven team Le mardi 31 mars 2015 23:24:21 Hervé BOUTEMY a écrit : Hi, Schedule confirmed: 20150403-2000 UTC = projects freeze in Codehaus 20150405 = projects available in ASF Don't forget to check account emails if you already have an account at ASF -The Apache Maven team Le mercredi 25 mars 2015 03:44:07 Hervé Boutemy a écrit : Hi, As announced in our quarterly report from january, we were studying Jira migration from Codehaus to Apache: the migration will happen during the week- end of April 4th. We'll create the exact same Jira projects at ASF than what we have at Codehaus, copy the whole content and mark Codehaus read-only. See https://issues.apache.org/jira/browse/INFRA-9116 for exact list. For example, it was done a few years ago with (near empty) MPOM, which was moved from http://jira.codehaus.org/browse/MPOM to https://issues.apache.org/jira/browse/MPOM How will username migration from Codehaus to ASF happen? When migrating existing content, user accounts will be migrated too (that's the way Jira works). To avoid creating accounts that already exist at Apache, matching will be done on account's e-mail address. The mapping will look something like: for each e-mail/username pair in the Codehaus content if the email is associated with a user in the ASF Jira instance, reuse: update the username from imported content to the ASF username else we'll create a new account in the ASF Jira instance: if the username already exists in the ASF Jira instance (another email) update the imported username to append -[SUFFIX] to the end else use the imported username/email as is The exact [SUFFIX] still needs to be defined. If you want to be sure of your username at Apache Jira, please take a look at your e-mail at Codehaus and check that it matches the e-mail at your Apache Jira account. If you have any question, don't hesitate to ask. We'll keep you informed as the operation is planned more in details. -The Apache Maven team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- --- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [IMPORTANT NOTICE] Jira migration from Codehaus to Apache on April 4th
I think you have to ensure that your xircles primary email address is your @ apache.org email address... And before 20:00 UTC today too! On Friday, April 3, 2015, Jason van Zyl ja...@takari.io wrote: So in that file how is the mapping done from a different Codehaus username? There's the unix login @ Apache, and Apache JIRA username, but how is the mapping going to be done from a different username in the Codehaus JIRA instance? On Apr 3, 2015, at 2:37 AM, Hervé BOUTEMY herve.bout...@free.fr javascript:; wrote: Hi Maven devs, After Jira migration to ASF, we'll need to create groups to give required privileged access to issues to the team. We need to know the Jira username of everybody, which unfortunately is not required to be the same as your Apache id. I started the list in http://svn.apache.org/r1670998 Please update your Jira username. Thank you Hervé Le vendredi 3 avril 2015 08:17:37 Hervé Boutemy a écrit : The migration will start in 12h: every Jira project at Codehaus to be migrated to ASF will be marked read-only Remember to check your Jira account email settings both at Codehaus and ASF if you want to be sure of the result at ASF. And everything is tracked at https://issues.apache.org/jira/browse/INFRA-9116 -The Apache Maven team Le mardi 31 mars 2015 23:24:21 Hervé BOUTEMY a écrit : Hi, Schedule confirmed: 20150403-2000 UTC = projects freeze in Codehaus 20150405 = projects available in ASF Don't forget to check account emails if you already have an account at ASF -The Apache Maven team Le mercredi 25 mars 2015 03:44:07 Hervé Boutemy a écrit : Hi, As announced in our quarterly report from january, we were studying Jira migration from Codehaus to Apache: the migration will happen during the week- end of April 4th. We'll create the exact same Jira projects at ASF than what we have at Codehaus, copy the whole content and mark Codehaus read-only. See https://issues.apache.org/jira/browse/INFRA-9116 for exact list. For example, it was done a few years ago with (near empty) MPOM, which was moved from http://jira.codehaus.org/browse/MPOM to https://issues.apache.org/jira/browse/MPOM How will username migration from Codehaus to ASF happen? When migrating existing content, user accounts will be migrated too (that's the way Jira works). To avoid creating accounts that already exist at Apache, matching will be done on account's e-mail address. The mapping will look something like: for each e-mail/username pair in the Codehaus content if the email is associated with a user in the ASF Jira instance, reuse: update the username from imported content to the ASF username else we'll create a new account in the ASF Jira instance: if the username already exists in the ASF Jira instance (another email) update the imported username to append -[SUFFIX] to the end else use the imported username/email as is The exact [SUFFIX] still needs to be defined. If you want to be sure of your username at Apache Jira, please take a look at your e-mail at Codehaus and check that it matches the e-mail at your Apache Jira account. If you have any question, don't hesitate to ask. We'll keep you informed as the operation is planned more in details. -The Apache Maven team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org javascript:; For additional commands, e-mail: dev-h...@maven.apache.org javascript:; - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org javascript:; For additional commands, e-mail: dev-h...@maven.apache.org javascript:; - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org javascript:; For additional commands, e-mail: dev-h...@maven.apache.org javascript:; - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org javascript:; For additional commands, e-mail: dev-h...@maven.apache.org javascript:; Thanks, Jason -- Jason van Zyl Founder, Takari and Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io - What matters is not ideas, but the people who have them. Good people can fix bad ideas, but good ideas can't save bad people. -- Paul Graham - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org javascript:; For additional commands, e-mail: dev-h...@maven.apache.org javascript:; -- Sent from my phone
Re: [IMPORTANT NOTICE] Jira migration from Codehaus to Apache on April 4th
So in that file how is the mapping done from a different Codehaus username? There's the unix login @ Apache, and Apache JIRA username, but how is the mapping going to be done from a different username in the Codehaus JIRA instance? On Apr 3, 2015, at 2:37 AM, Hervé BOUTEMY herve.bout...@free.fr wrote: Hi Maven devs, After Jira migration to ASF, we'll need to create groups to give required privileged access to issues to the team. We need to know the Jira username of everybody, which unfortunately is not required to be the same as your Apache id. I started the list in http://svn.apache.org/r1670998 Please update your Jira username. Thank you Hervé Le vendredi 3 avril 2015 08:17:37 Hervé Boutemy a écrit : The migration will start in 12h: every Jira project at Codehaus to be migrated to ASF will be marked read-only Remember to check your Jira account email settings both at Codehaus and ASF if you want to be sure of the result at ASF. And everything is tracked at https://issues.apache.org/jira/browse/INFRA-9116 -The Apache Maven team Le mardi 31 mars 2015 23:24:21 Hervé BOUTEMY a écrit : Hi, Schedule confirmed: 20150403-2000 UTC = projects freeze in Codehaus 20150405 = projects available in ASF Don't forget to check account emails if you already have an account at ASF -The Apache Maven team Le mercredi 25 mars 2015 03:44:07 Hervé Boutemy a écrit : Hi, As announced in our quarterly report from january, we were studying Jira migration from Codehaus to Apache: the migration will happen during the week- end of April 4th. We'll create the exact same Jira projects at ASF than what we have at Codehaus, copy the whole content and mark Codehaus read-only. See https://issues.apache.org/jira/browse/INFRA-9116 for exact list. For example, it was done a few years ago with (near empty) MPOM, which was moved from http://jira.codehaus.org/browse/MPOM to https://issues.apache.org/jira/browse/MPOM How will username migration from Codehaus to ASF happen? When migrating existing content, user accounts will be migrated too (that's the way Jira works). To avoid creating accounts that already exist at Apache, matching will be done on account's e-mail address. The mapping will look something like: for each e-mail/username pair in the Codehaus content if the email is associated with a user in the ASF Jira instance, reuse: update the username from imported content to the ASF username else we'll create a new account in the ASF Jira instance: if the username already exists in the ASF Jira instance (another email) update the imported username to append -[SUFFIX] to the end else use the imported username/email as is The exact [SUFFIX] still needs to be defined. If you want to be sure of your username at Apache Jira, please take a look at your e-mail at Codehaus and check that it matches the e-mail at your Apache Jira account. If you have any question, don't hesitate to ask. We'll keep you informed as the operation is planned more in details. -The Apache Maven team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Takari and Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io - What matters is not ideas, but the people who have them. Good people can fix bad ideas, but good ideas can't save bad people. -- Paul Graham - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [IMPORTANT NOTICE] Jira migration from Codehaus to Apache on April 4th
details are in the fisrt email http://mail-archives.apache.org/mod_mbox/maven-users/201503.mbox/%3C1434116.J59z6P8pCf%40herve-desktop%3E Regards, Hervé Le vendredi 3 avril 2015 12:06:01 Jason van Zyl a écrit : So in that file how is the mapping done from a different Codehaus username? There's the unix login @ Apache, and Apache JIRA username, but how is the mapping going to be done from a different username in the Codehaus JIRA instance? On Apr 3, 2015, at 2:37 AM, Hervé BOUTEMY herve.bout...@free.fr wrote: Hi Maven devs, After Jira migration to ASF, we'll need to create groups to give required privileged access to issues to the team. We need to know the Jira username of everybody, which unfortunately is not required to be the same as your Apache id. I started the list in http://svn.apache.org/r1670998 Please update your Jira username. Thank you Hervé Le vendredi 3 avril 2015 08:17:37 Hervé Boutemy a écrit : The migration will start in 12h: every Jira project at Codehaus to be migrated to ASF will be marked read-only Remember to check your Jira account email settings both at Codehaus and ASF if you want to be sure of the result at ASF. And everything is tracked at https://issues.apache.org/jira/browse/INFRA-9116 -The Apache Maven team Le mardi 31 mars 2015 23:24:21 Hervé BOUTEMY a écrit : Hi, Schedule confirmed: 20150403-2000 UTC = projects freeze in Codehaus 20150405 = projects available in ASF Don't forget to check account emails if you already have an account at ASF -The Apache Maven team Le mercredi 25 mars 2015 03:44:07 Hervé Boutemy a écrit : Hi, As announced in our quarterly report from january, we were studying Jira migration from Codehaus to Apache: the migration will happen during the week- end of April 4th. We'll create the exact same Jira projects at ASF than what we have at Codehaus, copy the whole content and mark Codehaus read-only. See https://issues.apache.org/jira/browse/INFRA-9116 for exact list. For example, it was done a few years ago with (near empty) MPOM, which was moved from http://jira.codehaus.org/browse/MPOM to https://issues.apache.org/jira/browse/MPOM How will username migration from Codehaus to ASF happen? When migrating existing content, user accounts will be migrated too (that's the way Jira works). To avoid creating accounts that already exist at Apache, matching will be done on account's e-mail address. The mapping will look something like: for each e-mail/username pair in the Codehaus content if the email is associated with a user in the ASF Jira instance, reuse: update the username from imported content to the ASF username else we'll create a new account in the ASF Jira instance: if the username already exists in the ASF Jira instance (another email) update the imported username to append -[SUFFIX] to the end else use the imported username/email as is The exact [SUFFIX] still needs to be defined. If you want to be sure of your username at Apache Jira, please take a look at your e-mail at Codehaus and check that it matches the e-mail at your Apache Jira account. If you have any question, don't hesitate to ask. We'll keep you informed as the operation is planned more in details. -The Apache Maven team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Takari and Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io - What matters is not ideas, but the people who have them. Good people can fix bad ideas, but good ideas can't save bad people. -- Paul Graham - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For
Re: [IMPORTANT NOTICE] Jira migration from Codehaus to Apache on April 4th
Hi, Schedule confirmed: 20150403-2000 UTC = projects freeze in Codehaus 20150405 = projects available in ASF Don't forget to check account emails if you already have an account at ASF -The Apache Maven team Le mercredi 25 mars 2015 03:44:07 Hervé Boutemy a écrit : Hi, As announced in our quarterly report from january, we were studying Jira migration from Codehaus to Apache: the migration will happen during the week- end of April 4th. We'll create the exact same Jira projects at ASF than what we have at Codehaus, copy the whole content and mark Codehaus read-only. See https://issues.apache.org/jira/browse/INFRA-9116 for exact list. For example, it was done a few years ago with (near empty) MPOM, which was moved from http://jira.codehaus.org/browse/MPOM to https://issues.apache.org/jira/browse/MPOM How will username migration from Codehaus to ASF happen? When migrating existing content, user accounts will be migrated too (that's the way Jira works). To avoid creating accounts that already exist at Apache, matching will be done on account's e-mail address. The mapping will look something like: for each e-mail/username pair in the Codehaus content if the email is associated with a user in the ASF Jira instance, reuse: update the username from imported content to the ASF username else we'll create a new account in the ASF Jira instance: if the username already exists in the ASF Jira instance (another email) update the imported username to append -[SUFFIX] to the end else use the imported username/email as is The exact [SUFFIX] still needs to be defined. If you want to be sure of your username at Apache Jira, please take a look at your e-mail at Codehaus and check that it matches the e-mail at your Apache Jira account. If you have any question, don't hesitate to ask. We'll keep you informed as the operation is planned more in details. -The Apache Maven team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
