I agree with Joe.
thanks,
dims
On 11/13/2009 03:50 PM, Joe Schaefer wrote:
- Original Message
From: Greg Stein
To: general@incubator.apache.org
Sent: Fri, November 13, 2009 12:23:04 PM
Subject: Explanation of the extra pain (was: Two other issues to discuss for
Subversion
- Original Message
> From: Greg Stein
> To: general@incubator.apache.org
> Sent: Fri, November 13, 2009 12:23:04 PM
> Subject: Explanation of the extra pain (was: Two other issues to discuss for
> Subversion)
> Okay. I *think* that is pretty much the background
on all releases. Can we
tweak ViewVC to dynamically insert a header "This repository area is
part of an Apache Incubator podling". etc etc.
Cheers,
-g
-- Forwarded message --
From: Leo Simons
Date: Wed, Nov 11, 2009 at 19:17
Subject: Re: Two other issues to discuss for Sub
No objection from me for creating mailing lists and svn repo in the
expected final place.
It's a bit of a pain for podlings to face a double move of both their
repositories and mailing lists when arriving at Apache. The rationale
for doing it has many aspects that IMHO don't apply to the S
Same remark here than for the svn migration.
As this is unusual for the incubating project, it might be eductive for the
future poddling to describe why the incubator wants normaly to have
incubator mailing list and why this rational is not applicable to
subversion.
Gilles Scokart
2009/11/13 G
As this is unusual for the incubating project, it might be eductive for the
future poddling to describe why the incubator wants normaly to to have the
project under /incubator/ and why this rational is not applicable to
subversion.
Don't misunderstand me, I think it is good to have such exception
On Fri, Nov 13, 2009 at 12:59 AM, Greg Stein wrote:
> Joe Schaefer asked if he could set up the mailing lists this weekend.
> The discussion seemed to end, with no particular opposition, so I
> filed an Infrastructure ticket to track the creation of the mailing
> lists:
> https://issues.apache.or
Joe Schaefer asked if he could set up the mailing lists this weekend.
The discussion seemed to end, with no particular opposition, so I
filed an Infrastructure ticket to track the creation of the mailing
lists:
https://issues.apache.org/jira/browse/INFRA-2324
At this time, we're setting up just
Forgot to list the Infrastructure ticket, in case you would like to
follow the migration more closely:
https://issues.apache.org/jira/browse/INFRA-2321
On Thu, Nov 12, 2009 at 13:41, Greg Stein wrote:
> It looks like we might be moving the code repository over on
> Sunday(!). Thus, my query abo
Thanks, and yes: agreed on the rationale.
And have no fears. We aren't going to back out. And I'm not seeing
that the ASF would boot us. So that just means we need to work through
it :-)
On Wed, Nov 11, 2009 at 19:17, Leo Simons wrote:
> On Tue, Nov 10, 2009 at 7:27 PM, Greg Stein wrote:
>> The
It looks like we might be moving the code repository over on
Sunday(!). Thus, my query about source code placement has a finite
window for further discussion :-)
Over the past two days, it sounds like nobody has any particular
object to the svn code being loaded directly to /subversion. (yes, it
i
On Tue, Nov 10, 2009 at 7:27 PM, Greg Stein wrote:
> There are two other issues to discuss for the Subversion podling:
>
> * moving the mailing lists directly to @subversion.apache.org
> * placing the source code at /subversion/ rather than /incubator/subversion/
>
> We are hoping to minimize over
Easy: no, unless you have the same open source track
record and constitution of apache folks as subversion does.
- Original Message
> From: Gilles Scokart
> To: general@incubator.apache.org
> Sent: Wed, November 11, 2009 12:11:10 PM
> Subject: Re: Two other issues to
What will you say to the next incubating project asking the same thing?
Gilles Scokart
2009/11/10 Greg Stein
> There are two other issues to discuss for the Subversion podling:
>
> * moving the mailing lists directly to @subversion.apache.org
> * placing the source code at /subversion/ rather
Martijn Dashorst wrote:
> On Tue, Nov 10, 2009 at 8:43 PM, Greg Stein wrote:
>
>> LOL
>>
>> Well... the problem is that an "svn mv" from /incubator/subversion/ to
>> /subversion/ introduces an artificial breakage in the history. It is
>> actually quite disruptive for tracking history (which is
On Tue, Nov 10, 2009 at 8:43 PM, Greg Stein wrote:
> LOL
>
> Well... the problem is that an "svn mv" from /incubator/subversion/ to
> /subversion/ introduces an artificial breakage in the history. It is
> actually quite disruptive for tracking history (which is very
> important to us).
Sounds lik
On Tue, Nov 10, 2009 at 22:41, Ralph Goers wrote:
> On Nov 10, 2009, at 7:17 PM, Greg Stein wrote:
>
>> On Tue, Nov 10, 2009 at 21:09, Ralph Goers
>> wrote:
>>>
>>> On Nov 10, 2009, at 11:27 AM, Greg Stein wrote:
>>>
There are two other issues to discuss for the Subversion podling:
>>>
On Nov 10, 2009, at 7:17 PM, Greg Stein wrote:
> On Tue, Nov 10, 2009 at 21:09, Ralph Goers wrote:
>>
>> On Nov 10, 2009, at 11:27 AM, Greg Stein wrote:
>>
>>> There are two other issues to discuss for the Subversion podling:
>>>
>>> * moving the mailing lists directly to @subversion.apache.o
On Tue, Nov 10, 2009 at 22:17, Greg Stein wrote:
> On Tue, Nov 10, 2009 at 21:09, Ralph Goers wrote:
>...
>> I am fine with doing everything as if this was a TLP with the two exceptions
>> that 1) the main page should say it is still in incubation 2) it is still
>> under the umbrella of the IPM
On Tue, Nov 10, 2009 at 21:09, Ralph Goers wrote:
>
> On Nov 10, 2009, at 11:27 AM, Greg Stein wrote:
>
>> There are two other issues to discuss for the Subversion podling:
>>
>> * moving the mailing lists directly to @subversion.apache.org
>> * placing the source code at /subversion/ rather than
On Nov 10, 2009, at 11:27 AM, Greg Stein wrote:
> There are two other issues to discuss for the Subversion podling:
>
> * moving the mailing lists directly to @subversion.apache.org
> * placing the source code at /subversion/ rather than /incubator/subversion/
>
> We are hoping to minimize over
Now that you have explained :) +1 from me.
-- dims
On 11/10/2009 02:43 PM, Greg Stein wrote:
LOL
Well... the problem is that an "svn mv" from /incubator/subversion/ to
/subversion/ introduces an artificial breakage in the history. It is
actually quite disruptive for tracking history (which is
On Nov 10, 2009, at 2:27 PM, Greg Stein wrote:
There are two other issues to discuss for the Subversion podling:
* moving the mailing lists directly to @subversion.apache.org
* placing the source code at /subversion/ rather than /incubator/
subversion/
We are hoping to minimize overall disr
LOL
Well... the problem is that an "svn mv" from /incubator/subversion/ to
/subversion/ introduces an artificial breakage in the history. It is
actually quite disruptive for tracking history (which is very
important to us).
(and yes, because of that history issue, I personally have no problem
put
The project status will stay there and be maintained as long as we're
incubating. That's my initial draft to get it into the system. I need
to spend more time with it (but have spent time getting other
discussions/tasks "into the pipeline"). I'm just about out of that
stuff, so will go update that
Personally i am ok with #1, but i am not sure if "svn switch --relocate" too
much of a burden for you guys :)
On 11/10/2009 02:27 PM, Greg Stein wrote:
There are two other issues to discuss for the Subversion podling:
* moving the mailing lists directly to @subversion.apache.org
* placing the
How about the website ? (I can not find any information about the
project, mentors, committers etc.. )
http://incubator.apache.org/projects/subversion.html
-Deepal
> There are two other issues to discuss for the Subversion podling:
>
> * moving the mailing lists directly to @subversion.apache.org
There are two other issues to discuss for the Subversion podling:
* moving the mailing lists directly to @subversion.apache.org
* placing the source code at /subversion/ rather than /incubator/subversion/
We are hoping to minimize overall disruption to the community with a
move to incubator space
28 matches
Mail list logo
