| Re: [papyrus-rt-dev] git tags for releases |
Hi,
Given the current plan, i would indeed expect that a few bugfixes should be pushed to the stream/0.8-maintenance branch. It would be indeed costly to work on both branch. But for the early adopters/customizers, i would expect the need of only small but important fixes (priority of the viewpoint for example) on the stable branch.
Regards,
Rémi
Objet : Re: [papyrus-rt-dev] git tags for releases
Hi,
Do we have a clear idea of what the criteria are for deciding what bugs need to be fixed in a maintenance branch? As I understand it, the 0.9 release is planned for the middle of December It hardly seems worth the overhead of duplication of builds, setups, commits, testing, etc. for 0.8 maintenance.
Christian
On 26 October, 2016 at 10:50:11, SCHNEKENBURGER Remi 211865 (remi.schnekenburger@xxxxxx) wrote:
Yes,
That would allow the integration of the waiting gerrits on the eclipse server. As soon as the release has been done, we enter on the release maintenance period for 0.8. That also means the job duplication on the Hudson server – one set for master, the other set for streams/0.8-maintenance branch.
This has the side effect for developers working on the maintenance branch not to forget to backport the fixes on master (or work on master and then backport on streams/0.8-maintenance)
And this may also require some action on the oomph setup model, depending if we are working on the master or on the maintenance, and so to update the documentation on the developer side of the wiki.
Regards,
Rémi
-------------------------------------------------------
Rémi SCHNEKENBURGER
CEA Saclay Nano-INNOV
Institut CARNOT CEA LIST
De : papyrus-rt-dev-bounces@xxxxxxxxxxx [mailto:papyrus-rt-dev-bounces@xxxxxxxxxxx] De la part de Ernesto Posse
Envoyé : mercredi 26 octobre 2016 16:39
À : papyrus-rt developer discussions <papyrus-rt-dev@xxxxxxxxxxx>
Objet : Re: [papyrus-rt-dev] git tags for releases
And should we also create a maintenance branch for 0.8?
Perhaps streams/0.8-maintenance?
I would assume that we would do 0.9 commits on master and 0.8.1 on streams/0.8-maintenance.
On Wed, Oct 26, 2016 at 10:32 AM SCHNEKENBURGER Remi 211865 <Remi.SCHNEKENBURGER@xxxxxx> wrote:
Hi,
+1 for me, it sounds like a good idea for classifying the git repo.
So we should have this kind of “structure”:
releases/
.. 0.8.0
.. 0.8.1
milestones/
.. 0.8.0RC1
Regards,
Rémi
-------------------------------------------------------
Rémi SCHNEKENBURGER
CEA Saclay Nano-INNOV
Institut CARNOT CEA LIST
De : papyrus-rt-dev-bounces@xxxxxxxxxxx [mailto:papyrus-rt-dev-bounces@xxxxxxxxxxx] De la part de Ernesto Posse
Envoyé : mercredi 26 octobre 2016 16:12
À : papyrus-rt developer discussions <papyrus-rt-dev@xxxxxxxxxxx>
Objet : Re: [papyrus-rt-dev] git tags for releases
No objections then to calling it "releases/0.8.0"?
...going twice...
On Tue, Oct 25, 2016 at 11:12 AM Ernesto Posse <eposse@xxxxxxxxxxxxx> wrote:
Any other opinions? ...going once...
On Tue, Oct 25, 2016 at 8:18 AM charles+zeligsoft.com <charles@xxxxxxxxxxxxx> wrote:
+1
On 2016.10.24, at 17:53 , Christian Damus <give.a.damus@xxxxxxxxx> wrote:
Hi, Ernesto,
My own preference is for the releases/0.8.0 shape because several git UI tools on Mac show slash-separated branch and tag names as collapsible nodes in a tree.
Christian
On 24 October, 2016 at 14:55:31, Ernesto Posse (eposse@xxxxxxxxxxxxx) wrote:
Hi everyone.
Since we have now released 0.8.0, we should create a tag in the git repo.
There is one question: what do we call the tag? For the previous releases we have just the version number: 0.7.0, 0.7.1 and 0.7.2. We could keep the same scheme, or we could do something more descriptive, like
releases/0.8.0
0.8.0_release
release_0.8.0
etc.
With a more descriptive tag name, we could also have corresponding tags for milestones.
Any comments? suggestions? preferences?
--
Ernesto Posse
Zeligsoft
_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev
_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev______________________________________________________________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev