[os-infrastructure] Accepting (or rejecting) user contributions into piccolo ingres!main and or community branches

[Andrew Ross]

Hi Chris, All

On the server side, we created a patch file (svn diff) for each change
set. No branches were needed for them (at least so far) 

Chris Hane collected them and applied them to Emma's work area on the VM
on her laptop so she could demo the set. He's still got the master set
while those of us who sprinted have what we worked on.

Now that the dust has settled from the IUA, we'll be checking with the
sprinters to see if they're planning to complete them. I suspect many of
them need more work if for no other reason than proper testing and
process diligence. I expect that in most cases the sprinters will finish
things off. 

Some of them already have tickets in http://bugs.ingres.com. e.g.
http://bugs.ingres.com/ticket/170, http://bugs.ingres.com/ticket/143,
http://bugs.ingres.com/ticket/193

Andrew

-----Original Message-----
From: opensource-infrastructure-bounces at lists.ingres.com
[mailto:opensource-infrastructure-bounces at lists.ingres.com] On Behalf Of
Chris Clark
Sent: July 1, 2008 3:19 PM
To: Discussions about the infrastructure needed to support a true open
sourcecommunity; Open Source Engineering
Subject: [os-infrastructure] Accepting (or rejecting) user contributions
into piccolo ingres!main and or community branches

Something that came up whilst chatting off line with Ralph; the code
sprint in the UK should have a number of excellent real world (small
project) use cases to talk about. We have a number of Ingres projects
and OpenROAD ones to look at (ideally all of them).

Can anyone who is/was involved with the code sprints in the UK talk
about how that was(/is being)  handled? E.g. were branches made, or were
patches generated with "svn diff"? How are the changes going to get into
main (are they going to get into main or do we not want them).

Chris

_______________________________________________
opensource-infrastructure mailing list
opensource-infrastructure at lists.ingres.com
http://lists.ingres.com/mailman/listinfo/opensource-infrastructure