Multiple configurations per project & version replacement variable#38
Multiple configurations per project & version replacement variable#38danielvijge wants to merge 18 commits intoiridakos:masterfrom
Conversation
8e48649 to
c66597a
Compare
|
Great! I will test the branch later. Thanks so much.
|
|
it seems there's something error when I create a new release log, the error information is |
|
@danielvijge , Thanks. I rake db migrate and then test it again. I tried to create a new release log in project with version, and when I want to save and preview the notification ,it occured an error,
|
|
If there are errors, I'll take a look at it of course. Please note that for now, this only works on a new installation. It doesn't correctly migrate old data to be compatible with this feature. I'm still planning to write that as well. |
|
@danielvijge , |
|
@danielvijge ,
|
|
Can't reproduce it on my test environment. But I'll take a look at it once I get around testing it with old data |
|
Pushed some new commits that should fix backward compatibility issues with any release logs created using the old configuration. Old release logs are still displayed as a number in the overview, newer release logs are displayed by the release queue title. |
|
@danielvijge , Thanks |
Projects can work with versions. If a version is finished it can be released. In many situations a version has multiple releases: first to a test environment, then to an acceptance environment, and finally to a production environment. Most of the time these releases are the same, but sometimes an issue is removed for some reason.
I wanted to use this plugin, and made two enhancements to it:
At the moment the code works but I wouldn't advice merging it just yet. I first wanted to discuss to see if such functionality would fit with your idea of what this plugin should do, and how to work with release queues and configurations. I tested it for a complete new setup. It is required to first create a release queue, then a configuration. Also it doesn't deal with the migration of existing queues/configurations to this new functionality. So it's a bit rough, but most functionality is there. If you think this fits with your idea of release logs, I can work on it a bit more and send a complete pull request later.