Sourcecode of beta versions

[Vincent Kessler]

Hi there,

it would be very nice to get the sourcecode of the beta versions as well.

Thank you and regards,

Vincent

[heinrichsweikamp]

Hello Vincent,

We do not upload the beta sources (right now) because they are outdated within a few days. We can email you the latest code package if you want.

regards,
Matthias

[Vincent Kessler]

So this means you change the beta hex files published on the version page?
I thought it would be no additional expense if you published the sourcecode corresponding to the respective beta binary file on the version pages.
What about a public readable CVS or SVN repository? That would make it easier for people who would like to track the development progress or do their own customizations.

Regards,

Vincent

[heinrichsweikamp]

Vincent Kessler Wrote:
-------------------------------------------------------
> So this means you change the beta hex files
> published on the version page?

No, of course not. But betas are some kind of snapshot and the code looks ugly. Usually, we continue to work on the code right after uploading the HEX file. Until today we cleaned the code for the betas only...

> What about a public readable CVS or SVN
> repository? That would make it easier for people

Good idea, can you suggest a reliable server for that? Our internal CVS can not be opened to the Internet due to security reasons.

regards,
Matthias

[Vincent Kessler]

heinrichsweikamp Wrote:
-------------------------------------------------------
> > What about a public readable CVS or SVN
> > repository? That would make it easier for
> people
>
> Good idea, can you suggest a reliable server for
> that? Our internal CVS can not be opened to the
> Internet due to security reasons.
>

I would suggest using http://code.google.com

Regards,

Vincent

[Paul S]

heinrichsweikamp Wrote:

> Good idea, can you suggest a reliable server for
> that? Our internal CVS can not be opened to the
> Internet due to security reasons.

Understandable.

It all comes down to what source control system you want to use.

If you really have to stay with CVS (shudder!) then I think Sourceforge could host it. I would seriously look at moving to something more modern though. It will make your life easier.

Subversion is a lot better than CVS (you can't get files out of sync with each other). Sourceforge also support subversion, as does Google

Google have also announced that they will be supporting Mercurial (Official Page) which is a DVCS (Distributed Version Control System). DVCS's are a little different, but it does make it easy for people to manage their own private branches. Something this project may benefit from. You can also host Mercurial projects on Bitbucket, and other DVCS's like git have similar places such as GitHub. Both Bitbucket and Github are companies which charge for hosting, but both companies offer free hosting to OpenSource projects.

My personal ideal situation would be a Mercurial repository on Google Code or Bitbucket.
I just like using Mercurial and on those sites we would get an issue tracker. I think it's already getting confusing seeing which issues have been solved in the forums, and an issue tracker would make that a lot easier.

[heinrichsweikamp]

Paul S Wrote:
> My personal ideal situation would be a Mercurial
> repository on Google Code or Bitbucket.

I've just downloaded Mercurial and will play around with it.

> I just like using Mercurial and on those sites we
> would get an issue tracker. I think it's already

Agree.

Cheers,
Matthias

[Paul S]

[quote=Matthias]
I've just downloaded Mercurial and will play around with it.
[/quote]

If you have any questions feel free to get in touch. It might be a bit different to what you're used to.

[heinrichsweikamp]

Paul S Wrote:
> If you have any questions feel free to get in
> touch. It might be a bit different to what you're
> used to.

Here's the first one

I've setup an account at Bitbucket and installed TortoiseHG and Mercurial. I change some files and select "HG Commit" from the Explorer (WinXP), so far so good.

When selecting "Synchronize" and clicking on Push I get:

[quote]pushing to h ttps://heinrichsweikamp@bitbucket.org/heinrichsweikamp/ostc_code/
searching for changes
1 changesets found
*** http authorization required[command interrupted][/quote]

I get no form to enter the password and I can't see where to enter it in the config... When using the command line "hg push" I have to enter the password and the upload seems to be fine.

[quote]J:\temp\OSTC>hg push
pushing to h ttps://heinrichsweikamp@bitbucket.org/heinrichsweikamp/ostc_code/
searching for changes
http authorization required
realm: Bitbucket.org HTTP
user: heinrichsweikamp
password:
bb/acl: heinrichsweikamp is allowed. accepted payload.
quota: 1.5 MB in use, 150.0 MB available (0.98% used)[/quote]

Any hint?

Thanks!

Matthias

[heinrichsweikamp]

Vincent Kessler Wrote:
-------------------------------------------------------
> Hi there,
> it would be very nice to get the sourcecode of the
> beta versions as well.

Here you go: OSTC Code Repository

Cheers,
Matthias

[Vincent Kessler]

heinrichsweikamp Wrote:
-------------------------------------------------------
> Vincent Kessler Wrote:
> --------------------------------------------------
> -----
> > Hi there,
> > it would be very nice to get the sourcecode of
> the
> > beta versions as well.
>
> Here you go: OSTC Code Repository
>

Very nice! I will go an checkout the latest code right now!

Regards,

Vincent