Skip to content

Create and publish release v1.0.6 #97

Closed
@biswanaths

Description

@biswanaths
Contributor

Things to do before release

@SethTisue , @adriaanm , @ashawley Please do let me know, if I am missing anything for the release.

Activity

ashawley

ashawley commented on Apr 22, 2016

@ashawley
Member

@biswanaths Happy to review, but I can't see draft releases it seems.

adriaanm

adriaanm commented on Apr 22, 2016

@adriaanm
Contributor

Here's the draft. Is it time to add @ashawley to the committers team, @biswanaths? :-)

The following changes have been incorporated in this release

This release was made possible by contributions from @SethTisue,@adriaanm, @ashawley, @lrytz, @som-snytt.
We would like to thank them for their help.

adriaanm

adriaanm commented on Apr 22, 2016

@adriaanm
Contributor

Those are some nice release notes! Looks like you're all set for v1.0.6! Once you publish the release, the commit will be tagged and travis will stage a release on sonatype. Let me know when it's done so I can push the button to promote the staging repo to maven central.

som-snytt

som-snytt commented on Apr 22, 2016

@som-snytt
Contributor

Thanks for the mention, @adriaanm . I didn't have the gumption to adopt the module, but it's nice to see folks step up who can also exercise it!

ashawley

ashawley commented on Apr 22, 2016

@ashawley
Member

@biswanaths Release notes look good!

All the items under "Administrative" are TBD -- they're not done yet. I only proposed those things. Sorry if that wasn't clear. Were you planning on doing them?

adriaanm

adriaanm commented on Apr 22, 2016

@adriaanm
Contributor

@som-snytt, I'd love to take credit, but I didn't write the release notes, was just pasting them. @biswanaths wrote them

som-snytt

som-snytt commented on Apr 22, 2016

@som-snytt
Contributor

Thanks @biswanaths ! What conscientiousness! Except for the part about not pasting the release notes. Just kidding!

lespea

lespea commented on Apr 28, 2016

@lespea

Any update on getting this released?

biswanaths

biswanaths commented on Apr 28, 2016

@biswanaths
ContributorAuthor

I would like to address this #99 before pushing the release. Seems we are missing some paths for the OOM fix. Hopefully in couple of days.

lespea

lespea commented on Apr 28, 2016

@lespea

Oh yeah that seems like a good plan. Thanks for the update!

ashawley

ashawley commented on Apr 28, 2016

@ashawley
Member

Change mimaPreviousVersion in build.sbt to more recent scala-xml than 1.0.1

I tried making this change in #98, but it didn't ended up going very smoothly for reasons I don't understand. It's not a blocker for the next release, though.

ashawley

ashawley commented on Jun 12, 2016

@ashawley
Member

Ok, I resolved the issue with Mima by adding a commit to #98 that fixed it. I'd say we are good to release a new version of scala-xml once #98 and #100 are merged!

ghost
sarahgerweck

sarahgerweck commented on Jul 28, 2016

@sarahgerweck

Like @devisaneer, I'd love to see this as well: the fix to #45 / #91 is something that would be quite useful for my project.

29 remaining items

Loading
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @biswanaths@adriaanm@lespea@SethTisue@ashawley

        Issue actions

          Create and publish release v1.0.6 · Issue #97 · scala/scala-xml