Meeting notes 12.08.2014

alberskib commented 10 years ago

Notes: TODO:

[x] finish refactoring (waiting for review)
[x] manual testing
[x] correct documentation
[x] update dd writing to new version
[ ] template for dd writing

alberskib commented 10 years ago

@bio4j/dynamograph I need additional info regarding templates. Thanks to it I will be able to create one for ddwriting

eparejatobes commented 10 years ago

https://github.com/ohnosequences/metapasta.g8

alberskib commented 10 years ago

We should set up time of the tommorow meeting - I am available all day

laughedelic commented 10 years ago

For me better in the morning (say, around noon)

alberskib commented 10 years ago

I will try to update next project to scala 2.11 (use new version of typesets):

aws-statika
statika
amazon-linux-ami
aws-scala-tools

eparejatobes commented 10 years ago

Edu: available[AllDay]#is

alberskib commented 10 years ago

I successfully published next libraries:

aws-scala-tools_2.11 0.7.1-SNAPSHOT (based on sources from repo for 2.10)
aws-statika_2.11 1.1.0-SNAPSHOT (master)
amazon-linux-ami_2.11 0.14.1-SNAPSHOT (tag v0.14.1)
amazon-linux-ami_2.11 0.15.1-SNAPSHOT (master)
statika_2.11 1.1.0-SNAPSHOT (master)
compota_2.11 0.9.4-SNAPSHOT (master)

For aws-scala-tools I cannot find proper sources in github (when I released from realese/v0.7.0 branch I have problem with compota) so I download sources for 2.10 from http://snapshots.era7.com.s3.amazonaws.com/ohnosequences/aws-scala-tools_2.10/0.7.1-SNAPSHOT/aws-scala-tools_2.10-0.7.1-SNAPSHOT-sources.jar repackage them into project and release for scala 2.11

alberskib commented 10 years ago

@laughedelic I and @eparejatobes are available all day so provide the most suitable time for you. If you prefer to meet tommorow I also will be available all day

alberskib commented 10 years ago

I will replace org.clapper % avsl by com.typesafe.scala-logging %%scala-logging in compota an release it as snapshot. If you would like I will create pull request with this change. I am doing this because there is no avsl version for scala 2.11 In fact current version of avsl is only for 2.10-RC1 - in my opinione this library is no longer supported ant there is no sense to use it.

alberskib commented 10 years ago

Bump. How about meeting?

eparejatobes commented 10 years ago

agree about avsl, yes please open a PR. About the meeting, then better do it tomorrow. I want to take a look at everything before.

alberskib commented 10 years ago

Hello @bio4j/dynamograph, Did you publish today/yesterday any of these:

"ohnosequences" %% "scarph" % "0.2.0-SNAPSHOT"
"ohnosequences" %% "tabula" % "0.1.0-SNAPSHOT"
"ohnosequences" %% "type-sets" % "0.5.0-SNAPSHOT"

laughedelic commented 10 years ago

hey, sorry, I was almost the whole day without internet. tomorrow will be online.

about aws-scala-tools and compota relations — ping @evdokim.
about published 2.11 artifacts: if the latest released version compiles with scala-2.11, then you can just publish it, no need to bump the version. or you did some changes?
if you encounter any statika-related problems with this, tell me, I'll solve it. don't spend much of your time on it.
what do you mean in the last message? you want to rely on them? which exact versions do you need? if you want to fix these dependencies, let's release them. just tell me the branch/commit in each repo on which you depend.

alberskib commented 10 years ago

Last message is result of strange problem that I ran into. Today morning everything works fine but when I tried to execute tests on evening I received about 11 compile errors - without any change in dynamograph code. I was thinking that probably new SNAPSHOT was realesed which break my code. That's true I published type-sets with version 0.4.99-SNAPSHOT that solve my issues.

laughedelic commented 10 years ago

yep, snapshots are not reliable. but what is 0.49? why 49? look, if you depend on a project that is changing and you don't want to catch up new changes from there (or at least control it), there are at least two scenarios:

just release the dependency, if it's possible
if active changes come from one branch and you want a version from another branch (and it's also changing, so you can't release it yet), add a suffix to the version: 0.4.0-foo-SNAPSHOT and publish it

alberskib commented 10 years ago

Sorry I made mistake: I mean 0.4.99-SNAPSHOT - I know that it still magic number but:

0.4.99-SNAPSOT is almost 0.5.0 and 0.4.99
- it is SNAPSHOT

I do not release normal version because I do not want to break your numbering schema in "normal" releases.

alberskib commented 10 years ago

Meeting at 2 or 3 pm?

eparejatobes commented 10 years ago

15:00 is fine for me

laughedelic commented 10 years ago

fine for me too

bio4j / dynamograph

Meeting notes 12.08.2014 #52