Re: [papyrus-rt-dev] git tags for releases

[Ernesto Posse <eposse@xxxxxxxxxxxxx>]

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

+33 (0)1 69 08 48 48

CEA Saclay Nano-INNOV

Institut CARNOT CEA LIST

 

www.eclipse.org/papyrus

 

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