building a new release

8 views
Skip to first unread message

Steven Bird

unread,
Feb 9, 2012, 5:48:24 AM2/9/12
to nltk-dev
I intend to do a new release in about 12 hours, before heading off for
a couple of weeks of fieldwork. If the codebase works with Python
2.5, I'll call it 2.0.1rc4, otherwise 3.0.1a1! I'll try to do another
release within a month. Thanks for everyone's contributions! -Steven

peter ljunglöf

unread,
Feb 9, 2012, 6:32:15 AM2/9/12
to nltk...@googlegroups.com
If my changes are the only ones that are not 2.5 compatible, I can withdraw them for just this release.

Do you want me to do that?

/Peter

> --
> You received this message because you are subscribed to the Google Groups "nltk-dev" group.
> To post to this group, send email to nltk...@googlegroups.com.
> To unsubscribe from this group, send email to nltk-dev+u...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/nltk-dev?hl=en.
>

Nitin Madnani

unread,
Feb 9, 2012, 8:09:19 AM2/9/12
to nltk...@googlegroups.com
Happy fieldwork, Steven!

- Nitin

Steven Bird

unread,
Feb 9, 2012, 11:56:14 AM2/9/12
to nltk...@googlegroups.com

Thanks for the offer, Peter.  I don't have a strong opinion about this, and just want to get another release out.

-Steven

peter ljunglöf

unread,
Feb 9, 2012, 3:35:30 PM2/9/12
to nltk...@googlegroups.com

9 feb 2012 kl. 17:56 skrev Steven Bird:

> Thanks for the offer, Peter. I don't have a strong opinion about this, and just want to get another release out.

I just submitted a pull request for reverting some 2.5 incompatible changes. Perhaps it's good to create a new "2.5-compatible" branch now, so that the changes don't have to be retracted.

/Peter

PS. Happy fieldworking!

Steven Bird

unread,
Feb 9, 2012, 4:05:47 PM2/9/12
to nltk...@googlegroups.com
On 10 February 2012 07:35, peter ljunglöf <peter.l...@heatherleaf.se> wrote:
> I just submitted a pull request for reverting some 2.5 incompatible changes. Perhaps it's good to create a new "2.5-compatible" branch now, so that the changes don't have to be retracted.

Thanks Peter. I've merged this into the master branch and will get
out the release, then I think we can go ahead with an "nltk3" branch.

> PS. Happy fieldworking!

Thanks :)

Reply all
Reply to author
Forward
0 new messages