You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@opennlp.apache.org by Jörn Kottmann <ko...@gmail.com> on 2011/07/13 18:42:59 UTC

Release Process

Hi all,

we should soon start to work on creating the next release.
As part of this release we also need to fine tune the release
process and document it, so that it is for everyone in the
team possible to make a release.

I started to write down the steps we did for our last release,
and will soon add that to the website.

I believe the basic release process should be as follows.

We first discuss on the mailing list when and what should
be released, depending on the jira issues, some need to be delayed, or the
release needs to be delayed to get them in.

After this discussion is done we should elect a release manager which
is responsible for all formal tasks and overseeing the release process,
the RM should try to distribute the tasks among the committers as good
as possible.

Since making a release contains a number of tasks and steps I suggest
that we work out a wiki page which documents all that, and when tasks
are done people document that as well. This way we can ensure that
everything was done. A wiki page has the advantage over jira that we
can easily copy a table of tasks, instead of creating a lot of jira issues
manually.

So, in the end the RM is guided by the documentation on the website
which explains the individual tasks and the wiki page to distribute
and document the tasks and progress.

We should also make sure that the RM role is done by different people
from release to release so we have the knowledge about how to make one 
in the team.

Any opinions?

Jörn


Re: Release Process

Posted by Jörn Kottmann <ko...@gmail.com>.
On 7/18/11 2:11 PM, Jason Baldridge wrote:
> Great. Should we plan on releases roughly every 3-4 months, with flexibility
> to have releases in between if important changes or bug fixes have been made
> in the meantime?
>
> Also, have we decided on a version incrementing scheme?

I prefer to decide both case by case and make it dependent on the 
development
which happened. There might be good reasons to release quicker, or wait 
longer.

Probably it will then end up usually in a time frame of 3 - 4 month, but 
that also
gives us the flexibility to directly release again, in case there is 
serious bug or wait
for 6 -7 month if we want to make big changes.

The version increment also needs to take API changes into account.

Jörn


Re: Release Process

Posted by Jason Baldridge <ja...@gmail.com>.
Great. Should we plan on releases roughly every 3-4 months, with flexibility
to have releases in between if important changes or bug fixes have been made
in the meantime?

Also, have we decided on a version incrementing scheme?

On Mon, Jul 18, 2011 at 7:07 AM, Jörn Kottmann <ko...@gmail.com> wrote:

> On 7/18/11 2:04 PM, Jason Baldridge wrote:
>
>> +1 Sounds great.
>>
>> Does it make sense for Jorn to do this again this time, solidify the
>> documentation, and then someone else do the next?
>>
>>
>>  +1 I think that is is the way we should go.
>
> Jörn
>



-- 
Jason Baldridge
Assistant Professor, Department of Linguistics
The University of Texas at Austin
http://www.jasonbaldridge.com
http://twitter.com/jasonbaldridge

Re: Release Process

Posted by Jörn Kottmann <ko...@gmail.com>.
On 7/18/11 2:04 PM, Jason Baldridge wrote:
> +1 Sounds great.
>
> Does it make sense for Jorn to do this again this time, solidify the
> documentation, and then someone else do the next?
>
>
+1 I think that is is the way we should go.

Jörn

Re: Release Process

Posted by Jason Baldridge <ja...@gmail.com>.
+1 Sounds great.

Does it make sense for Jorn to do this again this time, solidify the
documentation, and then someone else do the next?

On Thu, Jul 14, 2011 at 5:38 AM, Olivier Grisel <ol...@ensta.org>wrote:

> 2011/7/13 Jörn Kottmann <ko...@gmail.com>:
> >
> > Any opinions?
>
> Sounds good.
>
> --
> Olivier
> http://twitter.com/ogrisel - http://github.com/ogrisel
>



-- 
Jason Baldridge
Assistant Professor, Department of Linguistics
The University of Texas at Austin
http://www.jasonbaldridge.com
http://twitter.com/jasonbaldridge

Re: Release Process

Posted by Olivier Grisel <ol...@ensta.org>.
2011/7/13 Jörn Kottmann <ko...@gmail.com>:
>
> Any opinions?

Sounds good.

-- 
Olivier
http://twitter.com/ogrisel - http://github.com/ogrisel