Re: [jetty-dev] master-->jetty-9 ; jetty-9.1-->master ?

[Greg Wilkins <gregw@xxxxxxxxxxx>]

I think that most tooling is capable of handling multiple branches - eg
http://git.eclipse.org/c/jetty/org.eclipse.jetty.project.git/

Besides, for the last few months, it has been the jetty-9.1 branch that has had all the active development and not master - so it is a wrong assumption anyway!

I'm really tempted to just rename master->jetty-9 and leave jetty-9.1 as is and see what breaks and who complains!

cheers

On 8 August 2013 11:59, Joakim Erdfelt <joakim@xxxxxxxxxxx> wrote:

Most tooling defaults to 'master' being where active development is.

Gerrit, git.eclipse.org's gitview interface, github, egit, git command line, etc ...

--

Joakim Erdfelt <joakim@xxxxxxxxxxx>

webtide.com

Developer advice, services and support

from the Jetty & CometD experts

eclipse.org/jetty - cometd.org

On Wed, Aug 7, 2013 at 6:09 PM, Greg Wilkins <gregw@xxxxxxxxxxx> wrote:

All,

I think we are close to when the master branch should be renamed to jetty-9 and the jetty-9.1 branch be renamed to master.

Although, can somebody remind me of why we need to have a master branch?    If we do have a master branch can't it just be empty except for a README.TXT file saying what the current most recent branch is?

cheers

--
Greg Wilkins <gregw@xxxxxxxxxxx>
http://www.webtide.com
Developer advice and support from the Jetty & CometD experts.
Intalio, the modern way to build business applications.

_______________________________________________
jetty-dev mailing list
jetty-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jetty-dev

_______________________________________________
jetty-dev mailing list
jetty-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jetty-dev