Release current aws about aws HOT 12 CLOSED

Do you want to merge the ElasticTranscoder into this release? I have it completed the commands and tested most of it -- I just need to complete the testing and make some adjustments to the packaging. I am expecting to have completed this over the weekend.

(My branch is here; prior discussion of ElasticTranscoder on #57.)

from aws.

@meteficha I believe I have released all changes that do not change the API. Regarding the next major release 0.8 (https://github.com/aristidb/aws/issues?milestone=2&page=1&state=open), I guess some of those issues could be cut out. As you might have noticed other projects have recently had higher priority than aws for me, but maybe I can try to get out a stripped down (i.e. basically just what is already in master and some cleanup) as 0.8 soonish.

@cdornan If it doesn't negatively affect other components, and you clean up your branch a little (as discussed in #57), it might be possible. Or maybe not. I don't know.

from aws.

@aristidb It seems you have missed aws' dependencies, though. It still won't accept conduit 1.0, which is why I linked to #60.

Regarding new features, I guess I don't need any of them yet so don't haste yourself for me =). The deps, however, force me to use a non-released version.

from aws.

Well I guess that one could be against the stable branch.

Felipe you can do that release yourself if you want. Just cherrypick the
relevant commits onto stable, adapt the Readme and the cabal file and make
a git tag.

Me, I'm gonna sleep now.
Am 14.03.2013 20:49 schrieb "Felipe Lessa" [email protected]:

@aristidb https://github.com/aristidb It seems you have missed aws'
dependencies, though. It still won't accept conduit 1.0http://packdeps.haskellers.com/feed?needle=aws,
which is why I linked to #60 #60.

Regarding new features, I guess I don't need any of them yet so don't
haste yourself for me =). The deps, however, force me to use a non-released
version.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/63#issuecomment-14925078
.

from aws.

Sorry if I sounded too harsh. The release isn't something that needs to be done yesterday. I was just trying to point out that I don't need to wait for 0.8 and don't want to pressure its release. Please don't avoid sleeping because of the aws package =).

from aws.

OK, #61 was already released no idea where you got the idea that it had not been. Now getting #60 into stable branch.

I should just refuse to accept pull requests that are on the wrong branch. :-P

from aws.

Released as 0.7.6.3. Please test if this release fulfills your needs, @meteficha

from aws.

I guess I missed the window for this release.

Maybe its no bad thing -- better not to rush a new release.

from aws.

It was a bugfix release so no new features did get in at all.

The next release with new features is 0.8.
Am 17.03.2013 12:03 schrieb "Chris Dornan" [email protected]:

I guess I missed the window for this release.

Maybe its no bad thing -- better not to rush a new release.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/63#issuecomment-15020822
.

from aws.

Cool. I have diverted into a another project this w/e but expect to pick it up again RSN.

from aws.

Any chance we can have a release once again? 0.9 doesn't work with GHC 7.8 due to the transformers bound which is fixed in HEAD.

from aws.

Yes I'll make a release as soon as I find some time.
Am 08.07.2014 12:43 schrieb "David Terei" [email protected]:

Any chance we can have a release once again? 0.9 doesn't work with GHC 7.8
due to the transformers bound which is fixed in HEAD.

—
Reply to this email directly or view it on GitHub
#63 (comment).

from aws.