Mailing-List: contact torque-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Torque Developers List" <torque-dev@db.apache.org>
Received-SPF: pass (athena.apache.org: domain of greg.monroe@dukece.com
 designates 152.3.166.24 as permitted sender)
From: Greg Monroe <Greg.Monroe@dukece.com>
To: 'Apache Torque Developers List' <torque-dev@db.apache.org>
Date: Mon, 8 Oct 2012 14:45:46 -0400
Subject: RE: Planning
Thread-Topic: Planning
Thread-Index: Ac2hBXn2TQbKN9hHRkmd3235R98APAEdoqvQ
Message-ID: 
 <55B8568AFA5F144F886F18186BAD5B2C5115F484C2@durham-e2k7mb1.dukece.com>
References: 
 <OFA85208E4.62E38F51-ONC1257A85.0024434C-C1257A8C.0007717F@seitenbau.net>
In-Reply-To: 
 <OFA85208E4.62E38F51-ONC1257A85.0024434C-C1257A8C.0007717F@seitenbau.net>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"

> 1) It is still undecided whether we want to include documentation with th=
e=0D=0A>    binary releases=2E Currently they only contain the jar and thei=
r =0D=0A>    dependencies=2E=0D=0A=0D=0AAFAIK, there is no requirement for =
this=2E I do think it's important for folks=0D=0Ato be able to be able to a=
ccess offline docs for a specific version=2E But the=0D=0Abinary jars does =
not seem to be the right place for this=2E I'd say that there=0D=0Adocs sho=
uld be in the source or a separate download and the binary distro=0D=0Aread=
me should point to where they can be downloaded=2E =0D=0A=0D=0A> 2) It is a=
lso undecided whether we want to provide source packages for the=0D=0A>    =
single modules=2E=0D=0A=0D=0AThe requirements in www=2Eapache=2Eorg/dev/rel=
ease=2Ehtml says: =0D=0A=0D=0A=2E=2E=2E must contain a source package, whic=
h must be sufficient for a user to =0D=0Abuild and test the release=2E=2E=
=0D=0A=0D=0AUnless we plan to change our release/versioning process to allo=
w for different=0D=0Aversions of sub modules, I think the single all in one=
 source is fine=2E=0D=0A =0D=0A> 3) We need to switch the site publishing m=
echanism to svnpubsub until the=0D=0A>    end of year [1]=2E So some change=
 in the site publishing mechanism is =0D=0A>    needed=2E We need to consid=
er the following:=0D=0A>  - We need a location for the site in svn (current=
ly the "default location"   =0D=0A>    db/torque/site is occupied by the to=
rque 3 site project, see also (5))=0D=0A>  - We probably want to retain the=
 documentation for older releases=0D=0A>  - It should be no hassle to creat=
e a new site version directory (as we now =0D=0A>    have for the old docs =
of 3=2E1, 3=2E2, and the new 4=2E0 but not the current=0D=0A>    3=2E3 docs=
)=0D=0A=0D=0AThe strategy Thomas F proposes seems OK=2E E=2Eg=2E site-svnpu=
bsub with subdirs for=0D=0Aeach release=2E Maybe scm-site or site-scm would=
 be a shorter name?=0D=0A=0D=0A> 4) How much time do we allow for testing b=
efore the first attempt to release=0D=0A>    4=2E0 ?=0D=0A=0D=0A4=2E0 is a =
major change=2E  I think folks will be a bit slow to start kicking =0D=0Ath=
e tires due to the learning curve=2E  2 months might be enough, but I don't=
=0D=0Athink we'd really get a lot of extra testers in that time frame=2E  =
=0D=0A=0D=0AOn the other hand, if stuff pops up after 4=2E0 is released, it=
 seems like all=0D=0Athe good work done to automate the release process wou=
ld make it easier to=0D=0Ado a 4=2E1 with fixes=2E=0D=0A=0D=0AI think as lo=
ng as we know there wouldn't be too many months between=0D=0Amissing featur=
es reports (e=2Eg=2E I used to be able to do=2E=2E) and a release=0D=0Athat=
 corrects them, a short 2 month test time is OK=2E=0D=0A=0D=0ABTW - Did any=
 notices of the beta release go out?  E=2Eg=2E in the site news and=0D=0Ato=
 torque-users?  If folks don't know it's there, they probably won't test =
=0D=0Awith their local code=2E=0D=0A=0D=0A=0D=0A> 5) Do we want to reorgani=
ze svn by putting the torque 3 resources into a=0D=0A>    separate place ?=
=0D=0A=0D=0A+1=2E=2E=2E but we should make sure it's well noted in the site=
=2E  This means=0D=0Athat folks with local projects that pull from svn will=
 need to update=0D=0Atheir local settings=2E  When such stuff breaks, it sh=
ould be easy to find=0D=0Aa notice that the structure has changed=2E=0D=0A=
=0D=0AMaybe there should be some "pre-notices" too=2E  E=2Eg, a note on the=
 site,=0D=0Ato this list, and to torque-user that the svn structure will ch=
ange on=0D=0Aa specific date (or date range)=2E=0D=0A=0D=0A> 6) I'd like to=
 improve the online docs further by dropping the strict =0D=0A>    separati=
on between modules in the docs=2E=0D=0A=0D=0A+1 - I think this would allow =
for some needed overview and "rabbit trail"=0D=0Atype organization=2E  E=2E=
g=2E, what to read to understand using torque =0D=0Avs what to read for mod=
ifying/developing topics=2E =0D=0A=0D=0AI think we sort of have this now, b=
ut you have to understand which =0D=0Asub-project you need=2E=2E=2E which y=
ou don't until you start learning things=2E Lol=2E=0D=0A=0D=0ADukeCE Privac=
y Statement:=0D=0APlease be advised that this e-mail and any files transmit=
ted with=0D=0Ait are confidential communication or may otherwise be privile=
ged or=0D=0Aconfidential and are intended solely for the individual or enti=
ty=0D=0Ato whom they are addressed=2E If you are not the intended recipient=
=0D=0Ayou may not rely on the contents of this email or any attachments,=0D=
=0Aand we ask that you please not read, copy or retransmit this=0D=0Acommun=
ication, but reply to the sender and destroy the email, its=0D=0Acontents, =
and all copies thereof immediately=2E Any unauthorized=0D=0Adissemination, =
distribution or copying of this communication is=0D=0Astrictly prohibited=
=2E

---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org