Was simpler to just do it myself than to figure out exactly which perms
Roger might need to set it up himself (being 'admin' for the NHE project is
apparently insufficient ???)

In any case, all done now -- advise any troubles~!

Steve Bohlen
[email protected]
http://blog.unhandled-exceptions.com
http://twitter.com/sbohlen


On Mon, Aug 1, 2011 at 9:03 AM, Stephen Bohlen <[email protected]> wrote:

> Sure, I'll take care of it now....
>
> Steve Bohlen
> [email protected]
> http://blog.unhandled-exceptions.com
> http://twitter.com/sbohlen
>
>
> On Mon, Aug 1, 2011 at 9:07 AM, Fabio Maulo <[email protected]> wrote:
>
>> Steve,
>> Roger Kratz, NH.Envers lead, needs permissions to configure the JIRA for
>> bitbucket (Envers is already on bitbucket) can you provide him the needed
>> permissions?
>> Thanks.
>>
>> --
>> Fabio Maulo
>>
>>
>> El 01/08/2011, a las 09:26, Stephen Bohlen < <[email protected]>
>> [email protected]> escribió:
>>
>> Excellent -- I knew about both of these being available for JIRA, but was
>> uncertain whether they were installed on the new hosted instance.  If plugin
>> availability isn't a blocker, then we're free and clear to make the decision
>> based on the other (more important) factors.
>>
>> Steve Bohlen
>> <[email protected]> <[email protected]>[email protected]
>> <http://blog.unhandled-exceptions.com><http://blog.unhandled-exceptions.com>
>> http://blog.unhandled-exceptions.com
>>  <http://twitter.com/sbohlen> <http://twitter.com/sbohlen>
>> http://twitter.com/sbohlen
>>
>>
>> On Mon, Aug 1, 2011 at 7:51 AM, Fabio Maulo < 
>> <[email protected]><[email protected]>
>> [email protected]> wrote:
>>
>>> AFAIK There are already two plugin installed: Git integration and
>>> Bitbucket
>>>
>>> --
>>> Fabio Maulo
>>>
>>>
>>> El 01/08/2011, a las 08:39, Stephen Bohlen < 
>>> <[email protected]><[email protected]>
>>> [email protected]> escribió:
>>>
>>> Drawing an arbitrary line in the sand for the sake of forcing a decision
>>> on this issue, I propose that we use 8/15 (2 weeks from today) as the
>>> planned target date for us to go-live officially within *some* DVCS (to be
>>> determined in the next two weeks).  This will permit us to lock-down the
>>> repo for any commits over the weekend of 8/13-8/14 to make this change.
>>>
>>> My present leaning on this issue is toward the following approach:
>>>
>>>    - move to github for source code management
>>>    - retain the present hosted JIRA instance with Atlassian for issue
>>>    management
>>>    - investigate the available options for JIRA <--> Git integration
>>>    under the present hosted JIRA (e.g., will Atlassian support one of the
>>>    several git plugins for JIRA under the hosted infrastructure?)
>>>
>>> While there are some obvious benefits to potentially moving to github for
>>> integrated issue management as well, IMO there is too much value (historical
>>> and otherwise) in the existing JIRA content (both resolved issues and
>>> pending) to simply jettison JIRA as an issue-tracker after some arbitrary
>>> date and move the issue management responsibility to github as well (though
>>> I would be very interested in other committers' opinion on this matter as
>>> well -- perhaps I'm overvaluing the existing JIRA content?).
>>>
>>> Other thoughts --?
>>>
>>> PS: I do concur that the slight pause that we will have in activity
>>> following the 3.2GA release makes this the best time to consider this move
>>> for the project.
>>>
>>> Steve Bohlen
>>>  <[email protected]> <[email protected]> <[email protected]>
>>> [email protected]
>>> <http://blog.unhandled-exceptions.com><http://blog.unhandled-exceptions.com><http://blog.unhandled-exceptions.com>
>>> http://blog.unhandled-exceptions.com
>>>  <http://twitter.com/sbohlen> 
>>> <http://twitter.com/sbohlen><http://twitter.com/sbohlen>
>>> http://twitter.com/sbohlen
>>>
>>>
>>> On Mon, Aug 1, 2011 at 6:56 AM, Julian Maughan 
>>> <<[email protected]><[email protected]><[email protected]>
>>> [email protected]> wrote:
>>>
>>>> The core committers will make a decision on this in due course: taking
>>>> into account all of the discussions that have been had on the subject (of
>>>> which there have been many!), as well as the more practical considerations
>>>> around what it will take to make such a transition.
>>>>
>>>> In my opinion, if we are going to make the move, now is a good time to
>>>> do it.
>>>>
>>>>
>>>> On 1 August 2011 15:29, Ramon Smits < 
>>>> <[email protected]><[email protected]><[email protected]>
>>>> [email protected]> wrote:
>>>>
>>>>>
>>>>>
>>>>> Hi all,
>>>>>
>>>>> I thought I read somewhere that when 3.2.0 would be released that there
>>>>> would be a switch to DCVS of which I thought git/github was pretty 
>>>>> popular.
>>>>>
>>>>> Is this still the case?
>>>>>
>>>>> --
>>>>> Ramon
>>>>>
>>>>>
>>>>
>>>
>>
>

Reply via email to