I added a 1.10.0 release to JIRA.
-Dan
On Wed, Feb 20, 2019 at 9:29 AM Sai Boorlagadda
wrote:
> Do we need to create an infra ticket to create a new release?
> I don't seem to have permissions to create releases in Jira.
>
> On Wed, Feb 20, 2019 at 8:42 AM Jacob Barrett wrote:
>
> > Release ma
Do we need to create an infra ticket to create a new release?
I don't seem to have permissions to create releases in Jira.
On Wed, Feb 20, 2019 at 8:42 AM Jacob Barrett wrote:
> Release manager need to add the next version number to JIRA when they
> branch the release. Changes going into develop
great - that works for me
On 2/20/19 9:05 AM, Jacob Barrett wrote:
On Feb 20, 2019, at 8:58 AM, Bruce Schuchardt wrote:
I would _really_ like to keep the release branches for historical purposes.
It's very useful to be able to look back and see what was/wasn't in a release
when someone ha
> On Feb 20, 2019, at 8:58 AM, Bruce Schuchardt wrote:
>
> I would _really_ like to keep the release branches for historical purposes.
> It's very useful to be able to look back and see what was/wasn't in a release
> when someone has a problem. If we delete the branches we need some other
I would _really_ like to keep the release branches for historical
purposes. It's very useful to be able to look back and see what
was/wasn't in a release when someone has a problem. If we delete the
branches we need some other way to record that information so that it's
readily available.
O
Release manager need to add the next version number to JIRA when they branch
the release. Changes going into develop need to be marked finished with a
version but may not be merged to the current release branch.
Also, after release isn’t the release branch supposed to be deleted? So what
gives
