Re: D tool development workflow

Bill Deegan <bill-cJFiu+DHMVC5azolltMz9laTQe2KTcn/@public.gmane.org>
Newsgroups gmane.comp.programming.tools.scons.devel
Message-ID <CAEyG4CFEMPqBf+maxCFf-VAV_6a9YF6c2EuiGnuTYwwqzceBSg@mail.gmail.com>
I appreciate your point of view.
But for many years now it has been separate.
We will migrate at some point.

For the time being, it's really not such a huge burden to login to tigris
to file a bug.
-Bill

On Tue, Apr 18, 2017 at 10:33 PM, Russel Winder <[email protected]>
wrote:

> On Tue, 2017-04-18 at 09:23 -0700, Bill Deegan wrote:
> > I think reporting bugs for one part of SCons in a different
> > repository is
> > not a good idea.
>
> I do not disagree. But having the codebase on BitBucket and the issue
> handler on Tigris is a dreadful set up in my view. If the issue handler
> was on BitBucket life would be a lot easier. However, every time this
> topic comes up we end up at "someone insists that the project cannot
> survive without the entire history, and no-one can be bothered to dothe
> transfer" so nothing happens.
>
> Of course Tigris looks like it is going away by the look of the sign
> saying "no more projects". If that happens and nothing is done, history
> gets lost anyway.
>
> I'd suggest opening up the issue tracker on the SCons repository on
> BitBucket sooner rather than later.
>
> --
> Russel.
> ============================================================
> =================
> Dr Russel Winder      t: +44 20 7585 2200   voip:
> sip:[email protected]
> 41 Buckmaster Road    m: +44 7770 465 077   xmpp: [email protected]
> London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder
>
> _______________________________________________
> Scons-dev mailing list
> [email protected]
> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>
>

_______________________________________________
Scons-dev mailing list
[email protected]
https://pairlist2.pair.net/mailman/listinfo/scons-dev
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.