From: Erik Petrich <epetrich@iv...> - 2004-05-23 23:44:18
On Mon, 24 May 2004, Vangelis Rokas wrote:
> After the latest changes in the SourceForge's CVS access,
> is it ok to commit some changes I've made? Or should I wait?
I think the only objection earlier was breaking the build in the middle of
preparing for a new release.
Currently, we are in between releases. This is the ideal time to commit
changes and new code to CVS. Even if the daily snapshot build is broken by
a commit, as long as it is fixed within a few days, I don't think any of
the other developers will complain (and the users shouldn't complain since
the snapshot download page has a disclaimer). The key thing is that any
bugs or build incompatibilites introduced by our changes can be found and
fixed well before a new release, or worst case, listed as a known bug in
the bug tracker.
In short: go ahead and commit!
From: Vangelis Rokas <vrokas@ot...> - 2004-05-24 13:15:03
----- Original Message -----
From: "Erik Petrich" <epetrich@...>
Subject: Re: [sdcc-devel] committing changes
> > After the latest changes in the SourceForge's CVS access,
> > is it ok to commit some changes I've made? Or should I wait?
> I think the only objection earlier was breaking the build in the middle of
> preparing for a new release.
Oh, it has nothing to do with that. Sourceforge has changed BIND from
8 to version 9, and it requires a fresh checkout for the CVS access to work.
It took me some hours to synchornize my old version to the new checkout.
(one can't commit any changes using the old directories, so old changes
be tranfered by hand to the frash checkout...)
I wouldn't like others to have problems like this.
ANW, I'll commit the changes.
Get latest updates about Open Source Projects, Conferences and News.