We are closing down on the metadata sync work. We are looking at 22 June for being able to finish the remaining pieces.
I wanted to understand as to how do we move ahead with the merge into trunk?
I see that we can propose for merging with in launchpad itself. Please let know what makes sense and how to go about it?
After the merge to trunk, we will continue to test it further and add automation tests( we are working with Jason Pickering for the same).In the event of any bugs that we uncover during that time, would we be able to port those fixes back to trunk?
It would be good if you could keep us in loop for the various milestone dates that the DHIS core team is going through.
We are closing down on the metadata sync work. We are looking at 22 June for being able to finish the remaining pieces.
I wanted to understand as to how do we move ahead with the merge into trunk?
I see that we can propose for merging with in launchpad itself. Please let know what makes sense and how to go about it?
After the merge to trunk, we will continue to test it further and add automation tests( we are working with Jason Pickering for the same).In the event of any bugs that we uncover during that time, would we be able to port those fixes back to trunk?
It would be good if you could keep us in loop for the various milestone dates that the DHIS core team is going through.
We are closing down on the metadata sync work. We are looking at 22 June for being able to finish the remaining pieces.
I wanted to understand as to how do we move ahead with the merge into trunk?
I see that we can propose for merging with in launchpad itself. Please let know what makes sense and how to go about it?
After the merge to trunk, we will continue to test it further and add automation tests( we are working with Jason Pickering for the same).In the event of any bugs that we uncover during that time, would we be able to port those fixes back to trunk?
It would be good if you could keep us in loop for the various milestone dates that the DHIS core team is going through.
We are closing down on the metadata sync work. We are looking at 22 June for being able to finish the remaining pieces.
I wanted to understand as to how do we move ahead with the merge into trunk?
I see that we can propose for merging with in launchpad itself. Please let know what makes sense and how to go about it?
After the merge to trunk, we will continue to test it further and add automation tests( we are working with Jason Pickering for the same).In the event of any bugs that we uncover during that time, would we be able to port those fixes back to trunk?
It would be good if you could keep us in loop for the various milestone dates that the DHIS core team is going through.
We also have changes to one of the screens in settings-app, for which the source code is in a git repo. I wanted to understand on how to move ahead with these changes. I hope that submitting a pull request when we send the launchpad details would suffice. Let us know your thoughts on this.
Thanks
Aamer.
···
On Fri, Jun 17, 2016 at 4:27 PM, Lars Helge Øverland lars@dhis2.org wrote:
Thanks. Projected release date is July 1 (alternatively July 4).
We are closing down on the metadata sync work. We are looking at 22 June for being able to finish the remaining pieces.
I wanted to understand as to how do we move ahead with the merge into trunk?
I see that we can propose for merging with in launchpad itself. Please let know what makes sense and how to go about it?
After the merge to trunk, we will continue to test it further and add automation tests( we are working with Jason Pickering for the same).In the event of any bugs that we uncover during that time, would we be able to port those fixes back to trunk?
It would be good if you could keep us in loop for the various milestone dates that the DHIS core team is going through.
We also have changes to one of the screens in settings-app, for which the source code is in a git repo. I wanted to understand on how to move ahead with these changes. I hope that submitting a pull request when we send the launchpad details would suffice. Let us know your thoughts on this.
We are closing down on the metadata sync work. We are looking at 22 June for being able to finish the remaining pieces.
I wanted to understand as to how do we move ahead with the merge into trunk?
I see that we can propose for merging with in launchpad itself. Please let know what makes sense and how to go about it?
After the merge to trunk, we will continue to test it further and add automation tests( we are working with Jason Pickering for the same).In the event of any bugs that we uncover during that time, would we be able to port those fixes back to trunk?
It would be good if you could keep us in loop for the various milestone dates that the DHIS core team is going through.
We also have changes to one of the screens in settings-app, for which the source code is in a git repo. I wanted to understand on how to move ahead with these changes. I hope that submitting a pull request when we send the launchpad details would suffice. Let us know your thoughts on this.
We are closing down on the metadata sync work. We are looking at 22 June for being able to finish the remaining pieces.
I wanted to understand as to how do we move ahead with the merge into trunk?
I see that we can propose for merging with in launchpad itself. Please let know what makes sense and how to go about it?
After the merge to trunk, we will continue to test it further and add automation tests( we are working with Jason Pickering for the same).In the event of any bugs that we uncover during that time, would we be able to port those fixes back to trunk?
It would be good if you could keep us in loop for the various milestone dates that the DHIS core team is going through.
