From: Noel O'B. <bao...@gm...> - 2008-05-15 06:44:22
|
Ditto. I think we are in agreement on this. Any major development should be done on a branch after this point. Noel 2008/5/14 Karol M. Langner <kar...@gm...>: > On Wednesday 14 May 2008, Adam Tenderholt wrote: >> The regression script looks fine to me now. I wonder if it was >> because I was using the trunk regression.py script while having >> another branch/ tag of cclib installed. > > I have no problem with that regression file. > >> If everyone else is on board for getting a new release out at the >> end of June, I'm up for it. Is this going to mainly be a bug-fix >> release or are we adding significant new features? We should >> probably move this discussion into a new thread. > > I would opt for a quick release in June that concentrates on bug > fixes, and then follow up with the next major release, if we find the > time and new stuff gets done. > > Karol > >> Adam >> >> On May 14, 2008, at 12:04 AM, Noel O'Boyle wrote: >> > This is likely to be an error by me at some point. I'll look into >> > it. BTW, I think it's time for us to get out a release. How about >> > the end of June? (I've a lot of stuff happenining at the start of >> > June, so anything sooner would be a bit optimistic) >> > >> > 2008/5/13 Adam Tenderholt <a-t...@st...>: >> >> Anyone else having problems with the regression test script >> >> dying prematurely? >> >> >> >> Traceback (most recent call last): >> >> File "regression.py", line 238, in ? >> >> main() >> >> File "regression.py", line 218, in main >> >> eval(fnname)(data) # Run the test >> >> File "regression.py", line 33, in >> >> testGAMESS_basicPCGAMESS_dvb_td_out >> >> assert len(logfile.etoscs) == 5 >> >> AttributeError: 'ccData' object has no attribute 'etoscs' >> >> >> >> This is with revision 811 on trunk. I didn't want to change >> >> anything about the script to fix it in case there is some >> >> underlying problem with the PCGAMESS parser. >> >> >> >> Adam > > -- > written by Karol Langner > Wed May 14 22:26:02 CEST 2008 > |
From: Noel O'B. <bao...@gm...> - 2010-02-23 11:28:34
|
To get things moving, I've suddenly made a cclib-1.0a release directly from trunk. It probably breaks horribly, but I'll tidy it up and hopefully get a final out in the next week or two. - Noel |
From: Noel O'B. <bao...@gm...> - 2011-03-06 16:33:23
|
Hi all, I aim to make a new release, cclib-1.0.1 or so, in the next few days... - Noel |
From: Karol M. L. <kar...@gm...> - 2008-05-21 09:43:56
|
Why not make a quick bug-fix release now (there have been quite a few things fixed) and concentrate on a larger release later? - Karol On Thursday 15 May 2008, Noel O'Boyle wrote: > Ditto. I think we are in agreement on this. Any major development > should be done on a branch after this point. > > Noel > > 2008/5/14 Karol M. Langner <kar...@gm...>: > > On Wednesday 14 May 2008, Adam Tenderholt wrote: > >> The regression script looks fine to me now. I wonder if it was > >> because I was using the trunk regression.py script while having > >> another branch/ tag of cclib installed. > > > > I have no problem with that regression file. > > > >> If everyone else is on board for getting a new release out at > >> the end of June, I'm up for it. Is this going to mainly be a > >> bug-fix release or are we adding significant new features? We > >> should probably move this discussion into a new thread. > > > > I would opt for a quick release in June that concentrates on bug > > fixes, and then follow up with the next major release, if we find > > the time and new stuff gets done. > > > > Karol -- written by Karol Langner Wed May 21 11:56:12 CEST 2008 |
From: Noel O'B. <bao...@gm...> - 2008-05-21 20:13:12
|
But this is exactly what we are doing, except that "now" for me, means a few weeks time. I've got various excuses like grant deadlines, and a talk to prepare, but I guess the real reason is that it doesn't seem to be quite urgent. It takes a bit of time to prepare a release - is there any strong reason you would like to see it out by the end of this month, rather than next? Noel 2008/5/21 Karol M. Langner <kar...@gm...>: > Why not make a quick bug-fix release now (there have been quite a few > things fixed) and concentrate on a larger release later? > > - Karol > > On Thursday 15 May 2008, Noel O'Boyle wrote: >> Ditto. I think we are in agreement on this. Any major development >> should be done on a branch after this point. >> >> Noel >> >> 2008/5/14 Karol M. Langner <kar...@gm...>: >> > On Wednesday 14 May 2008, Adam Tenderholt wrote: >> >> The regression script looks fine to me now. I wonder if it was >> >> because I was using the trunk regression.py script while having >> >> another branch/ tag of cclib installed. >> > >> > I have no problem with that regression file. >> > >> >> If everyone else is on board for getting a new release out at >> >> the end of June, I'm up for it. Is this going to mainly be a >> >> bug-fix release or are we adding significant new features? We >> >> should probably move this discussion into a new thread. >> > >> > I would opt for a quick release in June that concentrates on bug >> > fixes, and then follow up with the next major release, if we find >> > the time and new stuff gets done. >> > >> > Karol > > -- > written by Karol Langner > Wed May 21 11:56:12 CEST 2008 > |
From: Karol M. L. <kar...@gm...> - 2008-05-22 20:49:26
|
On Wednesday 21 May 2008, Noel O'Boyle wrote: > But this is exactly what we are doing, except that "now" for me, > means a few weeks time. I've got various excuses like grant > deadlines, and a talk to prepare, but I guess the real reason is > that it doesn't seem to be quite urgent. It takes a bit of time to > prepare a release - is there any strong reason you would like to > see it out by the end of this month, rather than next? > > Noel No reason at all, but I didn't know it's mcuh time. - Karol > 2008/5/21 Karol M. Langner <kar...@gm...>: > > Why not make a quick bug-fix release now (there have been quite a > > few things fixed) and concentrate on a larger release later? > > > > - Karol > > > > On Thursday 15 May 2008, Noel O'Boyle wrote: > >> Ditto. I think we are in agreement on this. Any major > >> development should be done on a branch after this point. > >> > >> Noel > >> > >> 2008/5/14 Karol M. Langner <kar...@gm...>: > >> > On Wednesday 14 May 2008, Adam Tenderholt wrote: > >> >> The regression script looks fine to me now. I wonder if it > >> >> was because I was using the trunk regression.py script while > >> >> having another branch/ tag of cclib installed. > >> > > >> > I have no problem with that regression file. > >> > > >> >> If everyone else is on board for getting a new release out at > >> >> the end of June, I'm up for it. Is this going to mainly be a > >> >> bug-fix release or are we adding significant new features? We > >> >> should probably move this discussion into a new thread. > >> > > >> > I would opt for a quick release in June that concentrates on > >> > bug fixes, and then follow up with the next major release, if > >> > we find the time and new stuff gets done. > >> > > >> > Karol -- written by Karol Langner Thu May 22 23:01:57 CEST 2008 |