You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by Alex Karasulu <ak...@apache.org> on 2008/05/08 03:51:01 UTC

[ApacheDS] Replaced trunks with bigbang

Hi all,

To prepare for a new ApacheDS release cycle and a bit of a different mode of
working we've swapped out the trunks with bigbang branches for the following
projects:

   shared
   daemon
   apacheds
   installers
   project

What is now in trunk is a stable build that works.  Unlike before we intend
to work in trunks now to add what we need for the 1.5.3 release.  Before we
were just keeping the trunk stable for users but the changes we need there
for remaining features will not be large and can be safely applied in trunk
without breakage.  We will merge these changes back into the bigbang after
making them.  The following features remain for 1.5.3 on our roadmap[0]:

    Index Rebuilding - Fix CLI based index command for adding new indices.
    UserPassword - make sure userPassword cannot be searched
    New Installers - installers for Solaris and the tarball remain + making
the *.bin installer work on all supported *NIX platforms

We will also most likely attack the most critical bugs.

Shortly we will change the bigbang to use the 1.5.4-SNAPSHOT with respective
versions for dependent projects even though we intend to release 1.5.3 from
trunk.  We're doing this because there are issues with jar collisions due to
the fact that we now have a build server that makes sure our snapshot
repository is fresh.  So for this reason we decided to bump the revision for
bigbang to 1.5.4-SNAPSHOT while working on 1.5.3-SNAPSHOT in trunk.

Also we're going to get seriously medievil withing the bigbang: almost to
the point where it may not compile for extended periods of time.  For these
reasons we will switch continuum to build from the trunk now.  I'm going to
go ahead and try to make the changes for continuum now.  BTW the following
features will be incorporated into the 1.5.4 release:

    DoS Safeguards - add safeguards to prevent size based DoS attacks
    DSML w/ Jetty - add Jetty container for self service apps and DSML
support
    Nested Partitions - DIRSERVER-465
    Encrypted Attributes - add support for encrypted attributes
    Snapshotting & Restoration - add a way to restore a crashed database
(restore command as a CLI tool)
    JNDI <http://cwiki.apache.org/confluence/display/DIRxPMGT/JNDI+removing>-
Complete JNDI removal
    New Default Partition - decouple the leafEvaluator from the Partition /
Using Cursors
    MINA 2.0 - Move to MINA 2.0

This should be the last of the changes we will do as part of the bigbang
effort.  The we can just keep working out of the trunk and get to 2.0 as
soon as possible.

Thanks,
Alex

-----------------------------
[0] Roadmap -
http://cwiki.apache.org/confluence/display/DIRxPMGT/2.0+Roadmap
[1] DIRSERVER-465 - https://issues.apache.org/jira/browse/DIRSERVER-465

Re: [ApacheDS] Replaced trunks with bigbang

Posted by Emmanuel Lecharny <el...@apache.org>.
Felix Knecht wrote:
>
>> Shortly we will change the bigbang to use the 1.5.4-SNAPSHOT with 
>> respective versions for dependent projects even though we intend to 
>> release 1.5.3 from trunk.  We're doing this because there are issues 
>> with jar collisions due to the fact that we now have a build server 
>> that makes sure our snapshot repository is fresh.  So for this reason 
>> we decided to bump the revision for bigbang to 1.5.4-SNAPSHOT while 
>> working on 1.5.3-SNAPSHOT in trunk.
>>
> I think it's also possible to have both (trunk and bigbang) built by 
> continuum if wanted.
As we are going to be "medieval" with bigbang, I think we can spare a 
lot of Continuum failure notifications until we get it running locally :)
>
> Regards
> Felix
>


-- 
--
cordialement, regards,
Emmanuel Lécharny
www.iktek.com
directory.apache.org



Re: [ApacheDS] Replaced trunks with bigbang

Posted by Felix Knecht <fe...@apache.org>.
> Shortly we will change the bigbang to use the 1.5.4-SNAPSHOT with 
> respective versions for dependent projects even though we intend to 
> release 1.5.3 from trunk.  We're doing this because there are issues 
> with jar collisions due to the fact that we now have a build server 
> that makes sure our snapshot repository is fresh.  So for this reason 
> we decided to bump the revision for bigbang to 1.5.4-SNAPSHOT while 
> working on 1.5.3-SNAPSHOT in trunk.
>
I think it's also possible to have both (trunk and bigbang) built by 
continuum if wanted.

Regards
Felix

Re: [ApacheDS] Replaced trunks with bigbang

Posted by Alex Karasulu <ak...@apache.org>.
Oh yes this does not help reduce complexity nor the learning curve for sure.

Alex

On Thu, May 8, 2008 at 8:22 AM, Ersin Er <er...@gmail.com> wrote:

> Hi,
>
> I suggest we do not have such "giant" branches as bigbang. I think it may
> prevent some developers working on the project, at least it may make people
> think twice with what they are doing (in a stressful manner). Instead of
> trying to keep trunk perfectly building, we can always work on the trunk and
> avoid merging problems; and we can sometimes (svn) tag the trunk when it
> perfectly builds and makes sense as a whole. So people can be referred to
> those tagged versions if they want to go with the edge version of the
> server.
>
> Just an idea,
>
> Greetings,
>
>
> On Thu, May 8, 2008 at 4:51 AM, Alex Karasulu <ak...@apache.org>
> wrote:
>
>> Hi all,
>>
>> To prepare for a new ApacheDS release cycle and a bit of a different mode
>> of working we've swapped out the trunks with bigbang branches for the
>> following projects:
>>
>>    shared
>>    daemon
>>    apacheds
>>    installers
>>    project
>>
>> What is now in trunk is a stable build that works.  Unlike before we
>> intend to work in trunks now to add what we need for the 1.5.3 release.
>> Before we were just keeping the trunk stable for users but the changes we
>> need there for remaining features will not be large and can be safely
>> applied in trunk without breakage.  We will merge these changes back into
>> the bigbang after making them.  The following features remain for 1.5.3 on
>> our roadmap[0]:
>>
>>     Index Rebuilding - Fix CLI based index command for adding new indices.
>>     UserPassword - make sure userPassword cannot be searched
>>     New Installers - installers for Solaris and the tarball remain +
>> making the *.bin installer work on all supported *NIX platforms
>>
>> We will also most likely attack the most critical bugs.
>>
>> Shortly we will change the bigbang to use the 1.5.4-SNAPSHOT with
>> respective versions for dependent projects even though we intend to release
>> 1.5.3 from trunk.  We're doing this because there are issues with jar
>> collisions due to the fact that we now have a build server that makes sure
>> our snapshot repository is fresh.  So for this reason we decided to bump the
>> revision for bigbang to 1.5.4-SNAPSHOT while working on 1.5.3-SNAPSHOT in
>> trunk.
>>
>> Also we're going to get seriously medievil withing the bigbang: almost to
>> the point where it may not compile for extended periods of time.  For these
>> reasons we will switch continuum to build from the trunk now.  I'm going to
>> go ahead and try to make the changes for continuum now.  BTW the following
>> features will be incorporated into the 1.5.4 release:
>>
>>     DoS Safeguards - add safeguards to prevent size based DoS attacks
>>     DSML w/ Jetty - add Jetty container for self service apps and DSML
>> support
>>     Nested Partitions - DIRSERVER-465
>>     Encrypted Attributes - add support for encrypted attributes
>>     Snapshotting & Restoration - add a way to restore a crashed database
>> (restore command as a CLI tool)
>>     JNDI<http://cwiki.apache.org/confluence/display/DIRxPMGT/JNDI+removing>- Complete JNDI removal
>>     New Default Partition - decouple the leafEvaluator from the Partition
>> / Using Cursors
>>     MINA 2.0 - Move to MINA 2.0
>>
>> This should be the last of the changes we will do as part of the bigbang
>> effort.  The we can just keep working out of the trunk and get to 2.0 as
>> soon as possible.
>>
>> Thanks,
>> Alex
>>
>> -----------------------------
>> [0] Roadmap -
>> http://cwiki.apache.org/confluence/display/DIRxPMGT/2.0+Roadmap
>> [1] DIRSERVER-465 - https://issues.apache.org/jira/browse/DIRSERVER-465
>>
>
>
>
> --
> Ersin
>

Re: [ApacheDS] Replaced trunks with bigbang

Posted by Emmanuel Lecharny <el...@apache.org>.
Ersin Er wrote:
> Hi,
>
> I suggest we do not have such "giant" branches as bigbang. 
This is the first time in 4 years we are working on such a branch. It 
takes longer than expected, as we were supposed to have finished with it 
back in february. Obviously we were too optimistic.

The idea is to close this branch as soon as the JNDI removal will be over.
> I think it may prevent some developers working on the project, at 
> least it may make people think twice with what they are doing (in a 
> stressful manner).
There is always a working trunk, in which developpers can work. We are 
merging from time to time trunk with bigbang, and occasionaly, we 
replace trunk with bigbang (this is the third time we did it yesturday). 
So for people not working on bigbang, trunk is the place, and trunk is 
100% guaranted to compile (ok, 99.9% ;)

Bigbang is nothing more than a branch, all in all ...
> Instead of trying to keep trunk perfectly building, we can always work 
> on the trunk and avoid merging problems;

I don't think that's a viable option. Some of our users are currently 
maintaining some patches on their own, against trunk, just because we 
are not fast enough to fix all the existing bugs, or to apply their 
patches. If we can't offer at least a stable trunk to them, then we are 
in trouble, IMO.
> and we can sometimes (svn) tag the trunk when it perfectly builds and 
> makes sense as a whole. So people can be referred to those tagged 
> versions if they want to go with the edge version of the server.
Every single revision is a tag everyone can use to refer to a working 
version. Do we need to define a Tag directory, as we have branches and 
releases directories ? That could be an option, sure.

I'm truly sorry about all the problem this big refactoring is causing, 
and I wish they will be fixed asap. We are really doing our best to get 
rid of bigbang as fast as possible ...

Thanks !

-- 
--
cordialement, regards,
Emmanuel Lécharny
www.iktek.com
directory.apache.org



Re: [ApacheDS] Replaced trunks with bigbang

Posted by Ersin Er <er...@gmail.com>.
Hi,

I suggest we do not have such "giant" branches as bigbang. I think it may
prevent some developers working on the project, at least it may make people
think twice with what they are doing (in a stressful manner). Instead of
trying to keep trunk perfectly building, we can always work on the trunk and
avoid merging problems; and we can sometimes (svn) tag the trunk when it
perfectly builds and makes sense as a whole. So people can be referred to
those tagged versions if they want to go with the edge version of the
server.

Just an idea,

Greetings,

On Thu, May 8, 2008 at 4:51 AM, Alex Karasulu <ak...@apache.org> wrote:

> Hi all,
>
> To prepare for a new ApacheDS release cycle and a bit of a different mode
> of working we've swapped out the trunks with bigbang branches for the
> following projects:
>
>    shared
>    daemon
>    apacheds
>    installers
>    project
>
> What is now in trunk is a stable build that works.  Unlike before we intend
> to work in trunks now to add what we need for the 1.5.3 release.  Before we
> were just keeping the trunk stable for users but the changes we need there
> for remaining features will not be large and can be safely applied in trunk
> without breakage.  We will merge these changes back into the bigbang after
> making them.  The following features remain for 1.5.3 on our roadmap[0]:
>
>     Index Rebuilding - Fix CLI based index command for adding new indices.
>     UserPassword - make sure userPassword cannot be searched
>     New Installers - installers for Solaris and the tarball remain + making
> the *.bin installer work on all supported *NIX platforms
>
> We will also most likely attack the most critical bugs.
>
> Shortly we will change the bigbang to use the 1.5.4-SNAPSHOT with
> respective versions for dependent projects even though we intend to release
> 1.5.3 from trunk.  We're doing this because there are issues with jar
> collisions due to the fact that we now have a build server that makes sure
> our snapshot repository is fresh.  So for this reason we decided to bump the
> revision for bigbang to 1.5.4-SNAPSHOT while working on 1.5.3-SNAPSHOT in
> trunk.
>
> Also we're going to get seriously medievil withing the bigbang: almost to
> the point where it may not compile for extended periods of time.  For these
> reasons we will switch continuum to build from the trunk now.  I'm going to
> go ahead and try to make the changes for continuum now.  BTW the following
> features will be incorporated into the 1.5.4 release:
>
>     DoS Safeguards - add safeguards to prevent size based DoS attacks
>     DSML w/ Jetty - add Jetty container for self service apps and DSML
> support
>     Nested Partitions - DIRSERVER-465
>     Encrypted Attributes - add support for encrypted attributes
>     Snapshotting & Restoration - add a way to restore a crashed database
> (restore command as a CLI tool)
>     JNDI<http://cwiki.apache.org/confluence/display/DIRxPMGT/JNDI+removing>- Complete JNDI removal
>     New Default Partition - decouple the leafEvaluator from the Partition /
> Using Cursors
>     MINA 2.0 - Move to MINA 2.0
>
> This should be the last of the changes we will do as part of the bigbang
> effort.  The we can just keep working out of the trunk and get to 2.0 as
> soon as possible.
>
> Thanks,
> Alex
>
> -----------------------------
> [0] Roadmap -
> http://cwiki.apache.org/confluence/display/DIRxPMGT/2.0+Roadmap
> [1] DIRSERVER-465 - https://issues.apache.org/jira/browse/DIRSERVER-465
>



-- 
Ersin