[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: gEDA-user: test repo
DJ Delorie wrote:
>
>> If this happens too often, I may have to quit using and testing the
>> cutting edge version. After all, I still have to get my projects
>> done. I guess, other users feel the same.
>
> This has always been the case.
No reason not to change sub optimum habits.
> If you want a stable reliable tool, use a released version, or stick
If you want real world testing, provide an environment with proper
fall back options.
> with one checked-out version you know
> works, or maintain your own bugfix branch. Git head is where
> development happens, and when we're bringing in big changes, stuff
> breaks.
This is why other projects like KiCAD provide a dedicated testing repo.
Debian even has four stages (experimental, unstable, testing and stable).
By the way, stuff also breaks with small changes. See the first commits
of the new layer selector.
>> Add a branch "test" to git.
>
> We call this "remote repositories" like Peter's GL repo.
This is only comparable, if there is just one such remote repo and if
this repo is handled like Peter did. That is, frequent rebase to the
main tree and in general a slow and steady progress. If any of these
prerequisites is not met, the remote repository approach won't cut it.
> I see no
> need to have something else in the main repo that needs admin time
> when we already have a working model for it.
It is not working.
See the mil-to-nm conversion. IIRC, Andrew had a test repo set up.
Obviously, some quite severe issues had passed undetected.
---<)kaiamrtin(>---
--
Kai-Martin Knaak tel: +49-511-762-2895
Universität Hannover, Inst. für Quantenoptik fax: +49-511-762-2211
Welfengarten 1, 30167 Hannover http://www.iqo.uni-hannover.de
-----> not happy with moderation of geda-user mailinglist
_______________________________________________
geda-user mailing list
geda-user@xxxxxxxxxxxxxx
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user