Tag Current SVN Release

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Natalie G

    (@nataliegarza011)

    Hello Sam,

    Thanks for bringing this to our attention. I reviewed this with our developers and they are going to continue to look into this soon.

    We use an automated script to deploy to www.ads-software.com subversion since all of our version control is in git. We had the impression that we were already tagging the correct SVN release and not pointing to trunk. But again, we’ll see if there’s something we missed or we can improve.

    Thread Starter samedwards

    (@samedwards)

    Hi Natalie,

    Thanks for looking in to this. From the SVN logs, it looks like there might sometimes be a different procedure followed for your releases. When I noticed this issue last week, 1.6.1.1 was the current version, and there is just a single SVN commit, with the message only saying “1.6.1.1”, whereas 1.6.1.2 is now the current release, and I see two commits, with the messages “Committing 1.6.1.2 to trunk” and “Tagging 1.6.1.2”, which is what I would expect.

    Plugin Support Natalie G

    (@nataliegarza011)

    @samedwards, I appreciate the update on that. We had an issue with your deployment automation a few weeks ago; our developers now think this might just be a small blip and should work as expected moving forward.

    We’ll be looking at this soon either way, but if you find that the releases continue to be inconsistent, let us know and we can try to find a pattern ??

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Tag Current SVN Release’ is closed to new replies.