On Sat, Mar 19, 2011 at 12:31 AM, Tom Hughes wrote:
> Sure - you can browse the master repository of what is deployed on the
> main web site here:
>
> http://git.openstreetmap.org/potlatch2.git/
>
> and you can see what (for example) Andy is working on here:
>
> http://github.com/gravitystorm/Po
On 18/03/11 12:55, Steve Bennett wrote:
> On Fri, Mar 18, 2011 at 8:56 PM, Tom Hughes wrote:
>> On 18/03/11 09:47, Steve Bennett wrote:
>>
>>> - how does one refer to changesets that feature a fix/enhancement (ie,
>>> r13245)?
>>
>> You can't at the moment - trac 0.11 only supports a single repos
On Fri, Mar 18, 2011 at 8:56 PM, Tom Hughes wrote:
> On 18/03/11 09:47, Steve Bennett wrote:
>
>> - how does one refer to changesets that feature a fix/enhancement (ie,
>> r13245)?
>
> You can't at the moment - trac 0.11 only supports a single repository.
Do I understand from that there are now
On 18/03/11 09:47, Steve Bennett wrote:
> - how does one refer to changesets that feature a fix/enhancement (ie,
> r13245)?
You can't at the moment - trac 0.11 only supports a single repository.
There is support in trac 0.12 for multiple repositories, but that
version isn't in the Ubuntu releas
On Wed, Mar 9, 2011 at 6:25 AM, Andy Allan wrote:
> Things have progressed today. Thanks to TomH we now have a conversion
> of svn to git, and I've written the promised introduction for p2
> committers at
Another question: what will happen to the integration between Trac and
Svn? In particular:
-
On Wed, Mar 9, 2011 at 6:25 AM, Andy Allan wrote:
> Happy to answer any questions, but remember things are neither set in
> stone nor necessarily fully thought-through!
Hi Andy,
First - thanks for taking the time to write up this documentation.
My question is about the paragraph beginning "Publ
On Tue, Mar 8, 2011 at 8:12 PM, Serge Wroclawski wrote:
> For potatch2, especially, I foresee developers customising it for
> various use cases (like I'm doing), and git is very useful here
> because it allows someone to customize their instance while keeping up
> to date with the core.
This is
On Mon, Feb 28, 2011 at 4:31 AM, Richard Fairhurst wrote:
> In the near future it looks likely that P2 will become the default editor on
> osm.org.Consequently we need to move from the 'rapid development' stage to
> the 'mature code' stage, and enforce a bit more rigour in the codebase -
> "with g
On Mon, Feb 28, 2011 at 9:31 AM, Richard Fairhurst wrote:
> In conjunction with this, we will be moving from svn to git (as used for the
> core Rails port). This will allow people to hack on their own improvements
> in parallel until they're ready for integration into the main codebase. Andy
> wi
Steve Bennett wrote:
Can you elaborate a bit on who "we" is, in this context? And what kind
of process of review and integration of new features do you envisage?
I guess I'm wondering how long we can expect to wait between
developing a new feature and seeing its deployment.
We're having a Lond
On Mon, Feb 28, 2011 at 8:31 PM, Richard Fairhurst wrote:
> r25368 should be the base for the functionality freeze. That's certainly not
> to say that we abandon the stuff that's been done since then, but we will
> separate it into the essentials (a and b above) and the enhancements (new
> functio
In the near future it looks likely that P2 will become the default
editor on osm.org.Consequently we need to move from the 'rapid
development' stage to the 'mature code' stage, and enforce a bit more
rigour in the codebase - "with great power comes great responsibility"
and all that. :)
In pa
12 matches
Mail list logo
