Hi Suresh,
What is the status of the release?
Thanks,
Shameera.
On Mon, Apr 3, 2017 at 1:22 PM Suresh Marru wrote:
> Hi All,
>
> I merged PGA and Airavata develop with master. Will work on release now.
>
> Suresh
>
> On Apr 3, 2017, at 11:23 AM, Shameera Rathnayaka
> wrote:
>
> Hi Suresh/Ma
Hi All,
I merged PGA and Airavata develop with master. Will work on release now.
Suresh
> On Apr 3, 2017, at 11:23 AM, Shameera Rathnayaka
> wrote:
>
> Hi Suresh/Marcus
>
> We can follow the release git workflow suggested in this article if that make
> sense. http://nvie.com/posts/a-succes
Hi Suresh/Marcus
We can follow the release git workflow suggested in this article if that
make sense. http://nvie.com/posts/a-successful-git-branching-model/
Thanks,
Shameera.
On Mon, Apr 3, 2017 at 11:00 AM Christie, Marcus Aaron
wrote:
> I agree with Shameera. But I also have a question: wha
On Apr 3, 2017, at 11:00 AM, Christie, Marcus Aaron wrote:
>
> I agree with Shameera. But I also have a question: what is the role of the
> release branch? Is it to be a long lived branch post release for bug fixes
> for that release, or is it a temporary branch for bug fixes for this release?
I agree with Shameera. But I also have a question: what is the role of the
release branch? Is it to be a long lived branch post release for bug fixes for
that release, or is it a temporary branch for bug fixes for this release?
Thanks,
Marcus
On Apr 3, 2017, at 10:56 AM, Shameera Rathnayaka
@ Shameera, Yes makes sense to me.
Hi All,
With Shameera’s suggestion, this is the modified timeline:
* Merge develop to master (end of day today)
* Test the master and prepare for release.
* Target wednesday for RC1 - branch master to 0.17-release-branch
* Merge any changes during release pr
Hi Suresh,
I would say don't freeze develop, let it go forward instead freeze the
master and only apply bug fixes. This bug fixes must go to both develop and
master branches.
rest of the plan looks good to me.
Thanks,
Shameera.
On Mon, Apr 3, 2017 at 10:36 AM Suresh Marru wrote:
Hi All,
We r
Hi All,
We really need to get this release out. I will start working on it. Please
input any suggestions/blocker on this time line:
* Merge develop to master (end of day today) and freeze develop
* Test the master and prepare for release.
* Target wednesday for RC1 - branch master to 0.17-rele
On Jan 9, 2017, at 12:26 PM, Amila Jayasekara wrote:
>
> How about Airavata 1.0 ?
HI Amila,
Good question. We need to revisit earlier discussions like [1] and march
towards 1.0. A key missing element I see is a clear articulation of
Architecture and easy to navigate through the design and con
How about Airavata 1.0 ?
-Amila
On Fri, Jan 6, 2017 at 2:40 PM, Suresh Marru wrote:
> Hi All,
>
> Looks like we have significant progress since Airavata 0.16 release in
> late July 2016. I can volunteer to be the release manager for 0.17. Can we
> do a feature freeze and start merging develop t
Hi All,
Looks like we have significant progress since Airavata 0.16 release in late
July 2016. I can volunteer to be the release manager for 0.17. Can we do a
feature freeze and start merging develop to master branch and work on a
release?
Any actively development will get disturbed if we st
11 matches
Mail list logo
