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 well....we 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 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
> >
> > ---------------------------------------------------------------------
> > 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
