Hi,
2) If I understand correctly, a key question is who will have commit
rights to the master repo on github. It seems that an exception is
required to allow that access to more than one person. My sense is that
ideally we should have more than one person with that access, but far
fewer
Malte Dik malte@web.de writes:
Eric Firing wrote:
2) If I understand correctly, a key question is who will have commit
rights to the master repo on github. It seems that an exception is
required to allow that access to more than one person.
Multiple options (as far as I have
On Sun, May 30, 2010 at 5:18 AM, Jouni K. Seppänen j...@iki.fi wrote:
I agree that there should be a release before the transition.
I was initially reluctant to do a release before the transition
because of the get_sample_data issue. I was worried that some 1.x
releases would point to the sf
On 05/30/2010 05:54 AM, John Hunter wrote:
On Sun, May 30, 2010 at 5:18 AM, Jouni K. Seppänenj...@iki.fi wrote:
I agree that there should be a release before the transition.
I was initially reluctant to do a release before the transition
because of the get_sample_data issue. I was worried
On Sun, May 30, 2010 at 12:05 PM, Eric Firing efir...@hawaii.edu wrote:
Do you have in mind a dual release--maintenance branch and trunk--or is
v0_99_maint abandoned with no release? Another option would be to make
a 99 release ASAP and delay the 1.0.
I do want to put out one last maintenance
On 05/30/2010 05:54 AM, John Hunter wrote:
now. Everyone who has some free time should tackle outstanding bugs
on the tracker. I am aware of a compile problem on solaris with CXX6
Appeal to all developers, official or not: there are 95 open bugs listed
on the tracker at the moment.
I
Hi,
Multiple options (as far as I have understand github). You could use one
account with multiple ssh-keys or you can add contributors to the
repository
in the repositorys Admin-panel, which I haven't tried out, yet.
The github TOS allow only one person per account. I guess that's why