pre-release development trunk

4 views
Skip to first unread message

Daniel Saez

unread,
Jan 31, 2011, 2:51:19 AM1/31/11
to ardup...@googlegroups.com
Hi Pirates,

Now that we have an online tool, everytime anyone modifies some paramenter in the ardupirate.h  chances are high that the tool will get outdated, and people will start getting compile errors (as it is happening now).

Right now the tool is hosted on KK server so I don't have direct access to it (yet), so somentimes it can take a while to get it up to date.

I've talked with Hein, and we agreed to have a development pre-trunk. That is, we make a new "dev_trunk", where we can make modifications without altering the stable link between the trunk source code and the online tool.

So when both, source and tool are even, pre-tested and compiled, we can then move them to the trunk for everyone to download.

Bear in mind that a new configurator is comming, plus a ground station, so many modifications are on it's way and we need to keep a stable version, until we can safely add modifications.

Hein promissed to create this dev_trunk this afternoon ;-)

So once we have that pre-trunk, NO ONE should be modifying the trunk, unless we agree to do so or it has no impact on the config side; as a team of developers, we need COORDINATION  ;-)
 

happy coding,

Dani

Frank.T

unread,
Jan 31, 2011, 2:56:40 AM1/31/11
to ArduPirates
Great initiative!

//Frank

Emile Castelnuovo

unread,
Jan 31, 2011, 3:57:02 AM1/31/11
to ardup...@googlegroups.com
I agree, well done.

Emile

2011/1/31 Frank.T <frank.to...@gmail.com>

Paul Jones

unread,
Jan 31, 2011, 5:21:25 AM1/31/11
to ardup...@googlegroups.com

Should people really be downloading straight from the trunk anyway? I thought that the release versions were zipped and placed in the downloads section.

 

But yes I agree - coordination is good!

 

 

Paul.

Daniel Saez

unread,
Jan 31, 2011, 5:23:22 AM1/31/11
to ardup...@googlegroups.com
That's also a good point to take into account....

2011/1/31 Paul Jones <pa...@pauljones.id.au>

Norbert Machinek

unread,
Jan 31, 2011, 5:46:13 AM1/31/11
to ardup...@googlegroups.com
We should keep the public trunk - but seperated from the development as
suggested.
Should be made sure that only tested and approven code goes into public.
The Zips are only for guys who can't handle svn. ;)

I handed Dani the keys for the FTP server so no delay will occur if changes
are needed for the Online Tool.

Changes in the public trunk should be announced throughout the group and in
the blog so everyone knows...

Norbert

--------------------------------------------------
From: "Daniel Saez" <gdani...@gmail.com>
Sent: Monday, January 31, 2011 11:23 AM
To: <ardup...@googlegroups.com>
Subject: Re: pre-release development trunk

> That's also a good point to take into account....
>
> 2011/1/31 Paul Jones <pa...@pauljones.id.au>
>
>> Should people really be downloading straight from the trunk anyway? I
>> thought that the release versions were zipped and placed in the downloads
>> section.
>>
>>
>>
>> But yes I agree - coordination is good!
>>
>>
>>
>>
>>
>> Paul.
>>
>>
>>

>> *From:* ardup...@googlegroups.com
>> [mailto:ardup...@googlegroups.com]
>> *On Behalf Of *Daniel Saez
>> *Sent:* Monday, 31 January 2011 6:51 PM
>> *To:* ardup...@googlegroups.com
>> *Subject:* pre-release development trunk

Frank Toorenburg

unread,
Jan 31, 2011, 7:52:43 AM1/31/11
to ardup...@googlegroups.com
I fully backed this statement!
 
//Frank


 
2011/1/31 Norbert Machinek <kinde...@googlemail.com>
Reply all
Reply to author
Forward
0 new messages