Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Releases should be tagged and/or branched #29

Closed
GoogleCodeExporter opened this issue Jul 7, 2015 · 3 comments
Closed

Releases should be tagged and/or branched #29

GoogleCodeExporter opened this issue Jul 7, 2015 · 3 comments

Comments

@GoogleCodeExporter
Copy link

I'm having problems with the latest version of run-jetty-run (will open a
new ticket for that in a bit) and need to revert to an older version, but
am unable to easily do so.

Old releases should be tagged under the tag folder to make it easy to
revert to previous versions.

Otherwise, I have to check out an old version from trunk, try to figure out
what source revision matched the run-jetty-run revision and go from there.

Original issue reported on code.google.com by dree...@gmail.com on 7 May 2009 at 6:36

@GoogleCodeExporter
Copy link
Author

You have a good suggestion (i.e. I should tag when creating each release), but 
it 
isn't necessary to resolve your issue...

First uninstall run-jetty-run, and then re-install it.  When you're selecting 
run-
jetty-run in the dialog, by default you're only shown the latest release, but 
there 
is an option to show you all versions.  Click that check-box, and then select 
the 
version you want.

Original comment by James.Sy...@gmail.com on 7 May 2009 at 10:48

  • Changed state: Accepted

@GoogleCodeExporter
Copy link
Author

Thanks James, I can't believe I missed that checkbox!  Lack of sleep & caffeine 
to
blame. ;-)

There isn't a mailing list or anything is there?  I'd like to discuss the bug 
I'm
having with 1.1.1 before opening an Issue, or just let me know if I should just 
go
ahead an open it.

Original comment by dree...@gmail.com on 7 May 2009 at 11:20

@GoogleCodeExporter
Copy link
Author

There isn't a mailing list at this time.  Please don't worry about opening a 
bug 
(i.e. go ahead and do so, please).

I've created tags for the last 3 releases.  Thanks for reminding me about doing 
that.

Original comment by James.Sy...@gmail.com on 7 May 2009 at 11:30

  • Changed state: Done
  • Added labels: Type-Other
  • Removed labels: Type-Defect

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant