FtpServer milestone plan

[Niklas Gustavsson <ni...@protocol7.com>]

Hi

I would like us to start discussing to road to a first 1.0 release of
FtpServer. Here's my view at how I would like to organize our
remaining work, feel free to provide input about timing or stuff you
would like to include or exclude. Note that this list start with the
M2 milestone, we actually have a M1 milestone that was never relased
but since its been tagged and discussed previsouly, I would like us
not to reuse it. Number are cheap :-)

Also note that my aim is not to set this plan in stone but rather get
a common view on what we focus on in the coming months.

FtpServer 1.0-M2
* Spring configuration done and stable, this also includes removing
our home-grown IoC code
* General clean-up of the code as an effect of the above item
* Updated the documentation to reflect the new configuration

Hopefully this can be done within the next few weeks and we could then
aim for a first real milestone release

FtpServer 1.0-M3
* Getting FtpServer running in performance benchmarking to ensure we
find the most obvious bottlenecks
* Integrating JSecurity and throwing out our user management
* Updated the documentation for user management
* Enable FtpServer to work well in an OSGi environment. For example,
structuring our package structure so that it work with OSGi and
finding Ftplets using OSGi whiteboarding

FtpServer 1.0-M4
* Feature complete for 1.0
* Stable API
* Complete documentation for 1.0

FtpServer 1.0-RC1
* Bugfixes and simple additions only

After that we'll use as many RCs as necessary to get a stable 1.0 relase out.

What do you think?

/niklas

Re: FtpServer milestone plan

[Niklas Gustavsson <ni...@protocol7.com>]

On Mon, Jun 16, 2008 at 8:53 AM, Fred Moore <fr...@gmail.com> wrote:
> On a side note: as we get close to 1.0-M4 something should probably be done
> for Apache FTP Server "public image": as of today I have the impression that
> this product remains largely unknown to most; attraction users & developers
> is obviously important for any software product but as we all know it's
> absolutely key for open source products!

I agree. I have been somewhat quite about the project until I feel
more comfortable about the stability of the API. As we're now getting
closer to that point, it would probably be time to start banging the
drums.

/niklas

Re: FtpServer milestone plan

[Fred Moore <fr...@gmail.com>]

Hi Niklas,

that sounds like a good plan... ...OSGi-friendliness & performanche
benchmarking are -- methinks -- of particular interest.

On a side note: as we get close to 1.0-M4 something should probably be done
for Apache FTP Server "public image": as of today I have the impression that
this product remains largely unknown to most; attraction users & developers
is obviously important for any software product but as we all know it's
absolutely key for open source products!

Cheers,
FM

On Wed, Jun 11, 2008 at 2:13 PM, Niklas Gustavsson <ni...@protocol7.com>
wrote:

> Hi
>
> I would like us to start discussing to road to a first 1.0 release of
> FtpServer. Here's my view at how I would like to organize our
> remaining work, feel free to provide input about timing or stuff you
> would like to include or exclude. Note that this list start with the
> M2 milestone, we actually have a M1 milestone that was never relased
> but since its been tagged and discussed previsouly, I would like us
> not to reuse it. Number are cheap :-)
>
> Also note that my aim is not to set this plan in stone but rather get
> a common view on what we focus on in the coming months.
>
> FtpServer 1.0-M2
> * Spring configuration done and stable, this also includes removing
> our home-grown IoC code
> * General clean-up of the code as an effect of the above item
> * Updated the documentation to reflect the new configuration
>
> Hopefully this can be done within the next few weeks and we could then
> aim for a first real milestone release
>
> FtpServer 1.0-M3
> * Getting FtpServer running in performance benchmarking to ensure we
> find the most obvious bottlenecks
> * Integrating JSecurity and throwing out our user management
> * Updated the documentation for user management
> * Enable FtpServer to work well in an OSGi environment. For example,
> structuring our package structure so that it work with OSGi and
> finding Ftplets using OSGi whiteboarding
>
> FtpServer 1.0-M4
> * Feature complete for 1.0
> * Stable API
> * Complete documentation for 1.0
>
> FtpServer 1.0-RC1
> * Bugfixes and simple additions only
>
> After that we'll use as many RCs as necessary to get a stable 1.0 relase
> out.
>
> What do you think?
>
> /niklas
>