[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [dash-dev] How to (or not to) develop on the dashboard commits explorer
|
What about the process of developing locally, checking in changes to
CVS, and using http://dash.eclipse.org/deploy/ to update from cvs?
Nick
On Feb 4, 2008 9:45 PM, Bjorn Freeman-Benson
<bjorn.freeman-benson@xxxxxxxxxxx> wrote:
>
> Dash Team,
> Karl and I did a lot of work today to fix bug 212140 and in the process of
> doing this we cleaned up the dash.eclipse.org:~dashboard tree. In order to
> keep it clean, we need to make a new rule:
>
>
> Do _not_ develop in the ~dashboard directory Develop in your local directory
> or dev box and use "cvs update" in ~dashboard to bring down the latest code.
> Thanks.
>
> The reason for this new rule is that you cannot commit code from the
> ~dashboard directory. Thus if you write code in ~dashboard and then copy
> that code to another box to do the commit and then do a "cvs update" from
> ~dashboard, the files will be filled with merge comments even though the
> code is identical. And then the scripts will not run. And it makes a mess
> that someone then has to clean up.
>
> Thanks,
> Bjorn
>
> --
> [end of message]
> _______________________________________________
> dash-dev mailing list
> dash-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/dash-dev
>
>
