-
Notifications
You must be signed in to change notification settings - Fork 44
Prepare 9.3.1 #287
Comments
@tiagocoutinho A new release sounds good. That would also help with the request in #287. I would have liked #281 to be included, but not sure if @sdebionne has made any progress on it? If not, does it look like something you could fix, @tiagocoutinho? I will also make a documentation update following #282. |
Cool!
Sure, I can have a look at it. I synchronize with @sdebionne to make sure we are not duplicating work. |
I did have a quick look at #281 but could not find anything obvious. I'll try got give it another go next Friday. My guess was that a converter from |
@tiagocoutinho Can we get a conda build of cppTango 9.3.3 and use that for tests? |
@tiagocoutinho Are you busy preparing a branch for this version, or should I? |
@ajoubertza, I can take care of the conda package for cppTango. It would be great if you could prepare the branch for pytango 9.3.1. I am also trying to prepare git repos for conda recipes for both cppTango and pyTango. |
OK, will do.
I like the code to live in Github, since all the users work on it already have access, and know the system. Also nice to have a single place to look for tango-related code. That being said, Gitlab's CI is nice too. SKA are using both. The development and "source of truth" is on Github, but they mirror the repos onto Gitlab for CI. I propose this. Would like to hear other opinions. I see there is already a tango-controls group on Gitlab. It is empty at the moment. Only member is @gjover - hopefully he can give you access, if we go this way. And then it could become an "official" group. |
Sounds good to me
There should be no problem. @gjover works 10 meters away from me :-) |
@tiagocoutinho Are you close to having a cppTango 9.3.3 conda package ready? I'd like to update the Travis tests to use it. Similarly, what is happening with the PyTango conda recipe? Do we need to wait for these before the release, or can I do it today? |
@tiagocoutinho Any feedback on my questions from last week (see above)? If not, I'm going to proceed with this release tomorrow. |
I've tried building the release, but the AppVeyor artefacts come out as This build is with the
Any ideas @tiagocoutinho @sdebionne @NexeyaSGara? |
Never mind - I made a mistake - forgot to update tango/release.py file! (Even the sdist build had the |
@andygotz I've uploaded the v9.3.1 PyTango release to PyPI. Can you please request someone at ESRF to build the Conda package? |
Hi @ajoubertza, I have started projects to build conda packages for Tango C++ on linux, PyTango on linux and PyTango on windows:
They are just staging areas. We are of course free to restructure and/or move them as we please. They are not working yet. I hope to have some time next week to make all of this work. |
Hi @tiagocoutinho |
@ajoubertza, I have uploaded the conda packages for python 2.7, 3.6 and 3.7 The linux repository I mentioned above is configured with gitlab CI to build conda packages. The windows repository contains the script to build the conda package + documentation on how to do it. There is no CI for it. Let me know if there is something missing |
Thanks for conda packages @tiagocoutinho. For the Windows conda packages, the previous discussion about this suggested we use feature like "python-static". Did that happen yet? |
Sorry, I don't know enough about conda to see if something is missing. Seems like the recipes are working. Would like them to move to https://gitlab.com/tango-controls (or maybe they should just be added to this repo?). |
This is to inform the community that 9.3.1 is being prepared
.travis.yml
with a conda package using a final cppTango 9.3.x release?The text was updated successfully, but these errors were encountered: