Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Received-SPF: pass (athena.apache.org: domain of akarasulu@gmail.com
 designates 64.233.162.239 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:sender:to:subject:mime-version:content-type:x-google-sender-auth;
        b=IwsIiMjDEhK77xoKO+1ZNVmS4MqSfnsQUqfOXgBJJ9jRk0O/pDTz0nHuAQefAdlClSsp+Z7eKlTMJ3xprO8nzsv1Ev4I5yv2qSi0A97ZrMMqo/7zgzo8LDyN+nh3/sOorXZiSlIvmDC9oBHQfWCi10THKItisguuBu/0P/l75Ag=
Message-ID: <a32f6b020710291122y64af9de9w2a5a53fd72f054d3@mail.gmail.com>
Date: Mon, 29 Oct 2007 14:22:20 -0400
From: "Alex Karasulu" <akarasulu@apache.org>
Sender: akarasulu@gmail.com
To: "Apache Directory Developers List" <dev@directory.apache.org>
Subject: [VOTE] [ApacheDS] [BigBang] Should we check point what we have?
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_4283_13351967.1193682140826"

------=_Part_4283_13351967.1193682140826
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi all,

I think we can say we're finished with Phase I of the the big bang plan
[0].

Emmanuel planted the seed in my head that we might consider replacing the
current trunk with a copy of the big bang branch before moving forward on
Phase II.  He made some excellent points:

  o this gives developers a chance to see the changes
  o allows for an interim release if the team wants to release 1.5.2
  o gives the team a chance to start documenting some changes
  o prevents stalling somewhat as this refactoring is underway

These are all good points.  Personally I'm strapped on time trying to work
on
various things such as Triplesec, the refactoring in bigbang, and my day
job.
So I may not have enough time for helping out in a release but I'm fully
supportive
of one.

Copying big bang over to trunk check points the refactoring at a community
level:
heck svn automatically checkpoints for us and we can tag things as they are
now
too.  But the point is it checkpoints the current state and sends a clear
message
about where we are and what we can do before we do much with more in the
bigbang.
Who knows Phase II might become a big mess and/or we might not like where we

get to.  We may decide to keep things as they are after Phase I.

Should we replace trunk now with the bigbang?

[  ] +1 - replace trunk with big bang in present state
[  ] +/-0 - don't care
[  ] -1 - no not now

Thanks,
Alex

---------------------

[0] -
http://www.nabble.com/-ApacheDS---BigBang--Status-Report-tf4585474.html#a13089517

------=_Part_4283_13351967.1193682140826
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi all,<br><br>I think we can say we&#39;re finished with Phase I of the the big bang plan [0].&nbsp; <br><br>Emmanuel planted the seed in my head that we might consider replacing the <br>current trunk with a copy of the big bang branch before moving forward on 
<br>Phase II.&nbsp; He made some excellent points:<br><br>&nbsp; o this gives developers a chance to see the changes<br>&nbsp; o allows for an interim release if the team wants to release 1.5.2<br>&nbsp; o gives the team a chance to start documenting some changes
<br>&nbsp; o prevents stalling somewhat as this refactoring is underway<br><br>These are all good points.&nbsp; Personally I&#39;m strapped on time trying to work on <br>various things such as Triplesec, the refactoring in bigbang, and my day job.&nbsp; 
<br>So I may not have enough time for helping out in a release but I&#39;m fully supportive <br>of one.<br><br>Copying big bang over to trunk check points the refactoring at a community level: <br>heck svn automatically checkpoints for us and we can tag things as they are now 
<br>too.&nbsp; But the point is it checkpoints the current state and sends a clear message <br>about where we are and what we can do before we do much with more in the bigbang.&nbsp; <br>Who knows Phase II might become a big mess and/or we might not like where we 
<br>get to.&nbsp; We may decide to keep things as they are after Phase I.&nbsp; <br><br>Should we replace trunk now with the bigbang?<br><br>[&nbsp; ] +1 - replace trunk with big bang in present state<br>[&nbsp; ] +/-0 - don&#39;t care<br>[&nbsp; ] -1 - no not now
<br><br>Thanks,<br>Alex<br><br>---------------------<br><br>[0] - <a href="http://www.nabble.com/-ApacheDS---BigBang--Status-Report-tf4585474.html#a13089517">http://www.nabble.com/-ApacheDS---BigBang--Status-Report-tf4585474.html#a13089517
</a><br>

------=_Part_4283_13351967.1193682140826--