Can someone please do a release?

[Chris Withers]

Domen/Jan,

Can one of you do a release?

I'm close to doing a public release of a package that builds on
sqlalchemy and migrate but relies on the work I did back in September
last year. I'd prefer not to have it depending on an unreleased version
of migrate ;-)

Can you let me know what needs to happen and if there's anything I can
do to help?

cheers,

Chris

--
Simplistix - Content Management, Batch Processing & Python Consulting
- http://www.simplistix.co.uk

[ielectric ielectric]

Hey Chris,

I am close to zero time in January, but if we put hands together it can happen:)

A quick list what needs to be done:

* fix failing tests http://hudson.fubar.si/job/sqlalchemy-migrate/python=python2.4,sqlalchemy=0.5.8/lastCompletedBuild/testReport/

* http://code.google.com/p/sqlalchemy-migrate/issues/detail?id=91

* verify fix http://code.google.com/p/sqlalchemy-migrate/issues/detail?id=107

* get rid of ugly hack http://code.google.com/p/sqlalchemy-migrate/issues/detail?id=106

* go through changelog and commits and see if they match 1:1

then we are ready to roll:) Cheers, Domen

[Jan Dittberner]

I would do the release rollout if the issues addressed by Domen are
fixed. I'm very busy with other issues though and will not have time
to look at the remaining list of tasks in January. If somebody has
some time to fix them I will happily help to get the release done
(tagging, builds, PyPI, release announcement ...)

Regards
Jan

2011/1/12 ielectric ielectric <iele...@gmail.com>:

[Chris Withers]

On 12/01/2011 10:46, ielectric ielectric wrote:
> * fix failing tests
> http://hudson.fubar.si/job/sqlalchemy-migrate/python=python2.4,sqlalchemy=0.5.8/lastCompletedBuild/testReport/

> <http://hudson.fubar.si/job/sqlalchemy-migrate/python=python2.4,sqlalchemy=0.5.8/lastCompletedBuild/testReport/>*

The failing tests don't make any sense.

For example:

http://hudson.fubar.si/job/sqlalchemy-migrate/python=python2.6,sqlalchemy=0.5.8/lastBuild/testReport/junit/migrate.tests.versioning.test_api/TestAPI/test_create/

This test passes for me quite happilly with sqlalchemy 0.5.8, python 2.6
and the tip of migrate. Moreover:

http://code.google.com/p/sqlalchemy-migrate/source/browse/migrate/exceptions.py

...suggests that the exception is there to be imported.

Can you flush Hudson to try the 0.5.8 builds again or give me a clue how
to reproduce these?

I also did the full test run against sqlalchemy 0.6.6, mysql and
postgres and got no failures.

[Chris Withers]

On 12/01/2011 10:46, ielectric ielectric wrote:

> http://code.google.com/p/sqlalchemy-migrate/issues/detail?id=91
> * verify fix
> http://code.google.com/p/sqlalchemy-migrate/issues/detail?id=107
> * get rid of ugly hack
> http://code.google.com/p/sqlalchemy-migrate/issues/detail?id=106

Can you explain why these bugs are considered release blockers?

I'm not affected by these and none of them seem sever enough to stop a
release. Sure, I could see doing another third-point release if the
people with the problem scratched their own itches and provided patches,
but it seems a bit harsh to expect me to go and fix these issues when
I'm not affected by them just so I can get a release...

[Chris Withers]

Hi Guys,

http://hudson.fubar.si/job/sqlalchemy-migrate/

...looks a little weird.

4 pending builds but no changes or build requests since 15th Jan.
What's the state of it?

[Domen Kožar]

For the record, new Jenkins instance is located at
http://jenkins.gnuviech-server.de/job/sqlalchemy-migrate/