Hi,
Please find Avogadro 1.0.2_rc2 source tarballs on Sourceforge,
https://sourceforge.net/projects/avogadro/files/avogadro-beta/1.0.2_rc2/
These address quite a few issues raised after the last rc, and have
all but one patch from Gerrit merged (that one is deferred for a
possible 1.0.3). If there are no major regressions, I would like to
tag this as 1.0.2 and create new binaries.
Please let me know if there are any blockers. I know there are still
bugs, but I would rather put out 1.0.2 and make a 1.0.3 later if
necessary. I would also like to shift focus to 1.1.0 releases, with a
view to releasing 1.2.0 once we have stabilized the 1.1 line.
Thanks,
Marcus
On Mon, Apr 18, 2011 at 2:02 PM, Marcus D. Hanwell
mhanwell@gmail.com wrote:
Hi,
Please find Avogadro 1.0.2_rc2 source tarballs on Sourceforge,
https://sourceforge.net/projects/avogadro/files/avogadro-beta/1.0.2_rc2/
These address quite a few issues raised after the last rc, and have
all but one patch from Gerrit merged (that one is deferred for a
possible 1.0.3). If there are no major regressions, I would like to
tag this as 1.0.2 and create new binaries.
For the brave WIndows users out there I have just uploaded a Windows
installer too. It works in a bare Windows 7 x64 Ultimate VM for me. I
would appreciate feedback on it. It currently uses Open Babel trunk,
which I will need to fix (my current build process depends on a few
patches in trunk for Open Babel’s build on Windows).
It would be great to hear from some of the users who were hitting
issues on newer versions of Windows (along with users of XP etc).
Marcus
On Mon, Apr 18, 2011 at 6:33 PM, Marcus D. Hanwell
mhanwell@gmail.com wrote:
On Mon, Apr 18, 2011 at 2:02 PM, Marcus D. Hanwell
mhanwell@gmail.com wrote:
Hi,
Please find Avogadro 1.0.2_rc2 source tarballs on Sourceforge,
https://sourceforge.net/projects/avogadro/files/avogadro-beta/1.0.2_rc2/
These address quite a few issues raised after the last rc, and have
all but one patch from Gerrit merged (that one is deferred for a
possible 1.0.3). If there are no major regressions, I would like to
tag this as 1.0.2 and create new binaries.
For the brave WIndows users out there I have just uploaded a Windows
installer too. It works in a bare Windows 7 x64 Ultimate VM for me. I
would appreciate feedback on it. It currently uses Open Babel trunk,
which I will need to fix (my current build process depends on a few
patches in trunk for Open Babel’s build on Windows).
It would be great to hear from some of the users who were hitting
issues on newer versions of Windows (along with users of XP etc).
I guess we don’t have too many Windows XP users left? I tried it in a
new Windows XP virtual machine and had issues. It turns out an update
overwrote my manifest file I had fixed… I just uploaded a new binary
(_a) for Windows with a fixed manifest.
Unless I hear anything I intend to tag and release 1.0.2 on Friday.
Lots of people are downloading the Windows binaries, and the version
of Qt they ship with probably doesn’t even fully support newer
versions of Windows.
Feedback appreciated.
Marcus
Hi,
On Thu, Apr 21, 2011 at 2:10 AM, Marcus D. Hanwell
mhanwell@gmail.com wrote:
On Mon, Apr 18, 2011 at 6:33 PM, Marcus D. Hanwell
mhanwell@gmail.com wrote:
On Mon, Apr 18, 2011 at 2:02 PM, Marcus D. Hanwell
mhanwell@gmail.com wrote:
Hi,
Please find Avogadro 1.0.2_rc2 source tarballs on Sourceforge,
https://sourceforge.net/projects/avogadro/files/avogadro-beta/1.0.2_rc2/
These address quite a few issues raised after the last rc, and have
all but one patch from Gerrit merged (that one is deferred for a
possible 1.0.3). If there are no major regressions, I would like to
tag this as 1.0.2 and create new binaries.
For the brave WIndows users out there I have just uploaded a Windows
installer too. It works in a bare Windows 7 x64 Ultimate VM for me. I
would appreciate feedback on it. It currently uses Open Babel trunk,
which I will need to fix (my current build process depends on a few
patches in trunk for Open Babel’s build on Windows).
It would be great to hear from some of the users who were hitting
issues on newer versions of Windows (along with users of XP etc).
I guess we don’t have too many Windows XP users left? I tried it in a
new Windows XP virtual machine and had issues. It turns out an update
overwrote my manifest file I had fixed… I just uploaded a new binary
(_a) for Windows with a fixed manifest.
Unless I hear anything I intend to tag and release 1.0.2 on Friday.
Lots of people are downloading the Windows binaries, and the version
of Qt they ship with probably doesn’t even fully support newer
versions of Windows.
Feedback appreciated.
I’ve tried your rc2 installer on windows 7 and it worked here. I’m
also updating my build environment so I can make a python installer.
Tim
Marcus
Benefiting from Server Virtualization: Beyond Initial Workload
Consolidation – Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve
application availability and disaster protection. Learn more about boosting
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
Avogadro-devel mailing list
Avogadro-devel@lists.sourceforge.net
avogadro-devel List Signup and Options
On Thu, Apr 21, 2011 at 6:24 AM, Tim Vandermeersch
tim.vandermeersch@gmail.com wrote:
On Thu, Apr 21, 2011 at 2:10 AM, Marcus D. Hanwell
mhanwell@gmail.com wrote:
On Mon, Apr 18, 2011 at 6:33 PM, Marcus D. Hanwell
mhanwell@gmail.com wrote:
On Mon, Apr 18, 2011 at 2:02 PM, Marcus D. Hanwell
mhanwell@gmail.com wrote:
Hi,
Please find Avogadro 1.0.2_rc2 source tarballs on Sourceforge,
https://sourceforge.net/projects/avogadro/files/avogadro-beta/1.0.2_rc2/
These address quite a few issues raised after the last rc, and have
all but one patch from Gerrit merged (that one is deferred for a
possible 1.0.3). If there are no major regressions, I would like to
tag this as 1.0.2 and create new binaries.
For the brave WIndows users out there I have just uploaded a Windows
installer too. It works in a bare Windows 7 x64 Ultimate VM for me. I
would appreciate feedback on it. It currently uses Open Babel trunk,
which I will need to fix (my current build process depends on a few
patches in trunk for Open Babel’s build on Windows).
It would be great to hear from some of the users who were hitting
issues on newer versions of Windows (along with users of XP etc).
I guess we don’t have too many Windows XP users left? I tried it in a
new Windows XP virtual machine and had issues. It turns out an update
overwrote my manifest file I had fixed… I just uploaded a new binary
(_a) for Windows with a fixed manifest.
Unless I hear anything I intend to tag and release 1.0.2 on Friday.
Lots of people are downloading the Windows binaries, and the version
of Qt they ship with probably doesn’t even fully support newer
versions of Windows.
Feedback appreciated.
I’ve tried your rc2 installer on windows 7 and it worked here. I’m
also updating my build environment so I can make a python installer.
That sounds great, I would love to add support for superbuilds of all
of the Python dependencies at some point. Remember to change the
.manifest file version when making packages, that got me and only
failed on my clean Windows XP virtual machine. Once you have something
I can test it for you in my VM.
Marcus