Mailing-List: contact user-help@bloodhound.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@bloodhound.apache.org
Subject: Re: Product / Version strategies
References: <63F06E9E-1FB4-4B16-B802-903C4E2E4512@monivent.se>
 <CAGMZAuP1KhzwYhrOb-wJRuPFfAWaX37jTUCjPPmWfi8xvu7rYQ@mail.gmail.com>
From: Oscar Edvardsson <oscar@monivent.se>
Content-Type: text/plain;
	charset=utf-8
In-Reply-To: 
 <CAGMZAuP1KhzwYhrOb-wJRuPFfAWaX37jTUCjPPmWfi8xvu7rYQ@mail.gmail.com>
Message-Id: <275C5327-E83C-471C-BB40-98FCC48132B5@monivent.se>
Date: Wed, 26 Aug 2015 23:52:09 +0200
To: "user@bloodhound.apache.org" <user@bloodhound.apache.org>
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)

Thank you both for yor kind answers!

I would like to tinker as little as possible to avoid disaster (often happen=
s when I tinker) and help maintenance.

I can now really appreciate the idea of separating by discipline. I will def=
inetly have to think about that.

Off-topic: I never saw what Apache version it was for, I just assumed it was=
 the latest and greatest. :) My bad.

> 26 aug 2015 kl. 23:10 skrev Olemis Lang <olemis@gmail.com>:
>=20
>> On 8/26/15, Oscar Edvardsson <oscar@monivent.se> wrote:
>> Hi all,
>=20
> Hi !
> :)
>=20
>> I am about to set up a new Bloodhound server. I have a structure issue
>> though.
>> We aim at using the wiki and ticket system to manage three different part=
s
>> of our system. Each part may involve software/firmware, hardware and/or
>> mechanics, and each of these have different versions. It may look like
>> below.
>=20
> In my experience sometimes the best way to structure issue tracking is
> by discipline , instead of system's organisation . In a real world
> similarly complex deployment what I did was the following :
>=20
> Two BH instances , one for each intl branch .
>=20
> Six domains (mapped 2 to 4 onto BH instances) for each discipline
> (mechatronic , soft eng , automatic control , 3D design ,
> manufacturing , sales/customer support/strategy) . Products names in
> those instances were mapped onto domains by prefix e.g. mech_sensor1
> =3D> mech_sensor1.mech.domain.tld , swe_app1 =3D> swe_app1.swe.domain.tld
> , ...
>=20
> The separation of domains helped us to deal with authentication ,
> cookies , and alike ... In each case , components + milestones +
> versions .
>=20
> HTH
>=20
> [...]
>=20
> --=20
> Regards,
>=20
> Olemis - @olemislc
>=20
> Apache=E2=84=A2 Bloodhound contributor
> http://issues.apache.org/bloodhound
> http://blood-hound.net
>=20
> Brython committer
> http://brython.info
> http://github.com/brython-dev/brython
>=20
> Blog ES: http://simelo-es.blogspot.com/
> Blog EN: http://simelo-en.blogspot.com/
>=20
> Featured article: