Jim Mathies [:jimm] Reporter
	Description • 10 years ago

We're moving this browser off the main release trees for the time being. we plan to keep it up and running in a project repo for the team to tinker with and for community development.

Project type: finite, kept in projects directory.
Project name: I like the 'tree' names for our project repos. How about sequoia?
For builds:
 test runs: linux, mac, windows
 mozilla-central mozconfigs: yes with an added enable flag checked into existing configs.
 nightly builds: *yes*
 updates: *yes*
 talos: no
Name of the contact person for this branch: :jimm
Timeline:
 when should this branch go live: as soon as possible
 expected life span of project branch: hard to say, at least a year

	Kendall Libby [:fubar] (he/him)
	Comment 1 • 10 years ago

Pulling in Hal, as he may have questions/suggestions first.

	Hal Wine [:hwine] use NI!
	Comment 2 • 10 years ago

Pulling into correct product/component -- this may have several steps to it. :jimm for reference, the request process is described at https://wiki.mozilla.org/ReleaseEngineering/RepositoryCreationRequest Kudos on supplying so much info.

(In reply to Jim Mathies [:jimm] (away 4/1-4/21) from comment #0)
> Project type: finite, kept in projects directory.

Jim - What you're asking for is a big ask, touching several different groups. So, bear with me as we get some items clarified.

> Project name: I like the 'tree' names for our project repos. How about
> sequoia?

Tree names are reserved for 'twigs', which are described at https://wiki.mozilla.org/ReleaseEngineering/DisposableProjectBranches and are self serve. While there are no twigs available at the moment, some appear to be ready to be released at the end of March.

If that will meet your needs all the steps are outlined on the wiki page. Given how long you want this, and potential futures, I suspect a twig isn't appropriate.

> For builds:

>  nightly builds: *yes*
>  updates: *yes*

Are you asking for a separate update channel here? 

>  talos: no
> Name of the contact person for this branch: :jimm
> Timeline:
>  when should this branch go live: as soon as possible

Once we get a few questions answered, we can get the repository set up within a day or two.

New questions:
 - which existing repo will you want as the basis for this repo? m-c? or m-b?
 - what commit level will be needed
 - I assume you want all the normal hooks for firefox work - let me know if not

	Jim Mathies [:jimm] Reporter
	Comment 3 • 10 years ago

(In reply to Hal Wine [:hwine] (use needinfo) from comment #2)
> Pulling into correct product/component -- this may have several steps to it.
> :jimm for reference, the request process is described at
> https://wiki.mozilla.org/ReleaseEngineering/RepositoryCreationRequest Kudos
> on supplying so much info.
> 
> (In reply to Jim Mathies [:jimm] (away 4/1-4/21) from comment #0)
> > Project type: finite, kept in projects directory.
> 
> Jim - What you're asking for is a big ask, touching several different
> groups. So, bear with me as we get some items clarified.
> 
> > Project name: I like the 'tree' names for our project repos. How about
> > sequoia?
> 
> Tree names are reserved for 'twigs', which are described at
> https://wiki.mozilla.org/ReleaseEngineering/DisposableProjectBranches and
> are self serve. While there are no twigs available at the moment, some
> appear to be ready to be released at the end of March.

If we had a "twig" available now it would work provided no one would mind an extended reservation. I'm not willing to bet that we have a twig available end of march though - I looked through the list before filing this hoping for some availability, I really didn't see anything that looked like it would be open soon.  If we do wait for a twig, the code would have to live in limbo on mc.

> > For builds:
> 
> >  nightly builds: *yes*
> >  updates: *yes*
> 
> Are you asking for a separate update channel here? 

Nightlies generated for the repo. We have this in other twigs currently, oak has nightlies and back when we had this code on elm we generated nightlies there as well.
 
> New questions:
>  - which existing repo will you want as the basis for this repo? m-c? or m-b?

m-c

>  - what commit level will be needed

same as m-c.

>  - I assume you want all the normal hooks for firefox work - let me know if
> not

that sounds right.

	Jim Mathies [:jimm] Reporter
	Comment 4 • 10 years ago

(In reply to Jim Mathies [:jimm] (away 4/1-4/21) from comment #3)
> (In reply to Hal Wine [:hwine] (use needinfo) from comment #2)
> > > For builds:
> > 
> > >  nightly builds: *yes*
> > >  updates: *yes*
> > 
> > Are you asking for a separate update channel here? 
> 
> Nightlies generated for the repo. We have this in other twigs currently, oak
> has nightlies and back when we had this code on elm we generated nightlies
> there as well.

which would include the ability to update from within the app? I don't think we want people to install a build and be left stranded.

	Hal Wine [:hwine] use NI!
	Comment 5 • 10 years ago

Thanks for the answers.

My inclination here would be to set up a new repository, named 'projects/metro'. To my knowledge, we've never done something quite like this before, but this would give us an option to NOT kill the repo if some community members still want to work on it down the road. If there's a better name than 'metro', please suggest it.

It will require level 3 commit access, and we can get builds stood up fairly easily.

It will have it's own update channel, named the same as the branch. (FYI, this is more than just producing the builds, it uses the same product delivery process as Firefox - it will be just like nightly.) This will take a bit longer to set up.

I've been assuming that the builds will be en_US only.

If all the above is correct, especially the name, I can start the various processes.

	Jim Mathies [:jimm] Reporter
	Comment 6 • 10 years ago

(In reply to Hal Wine [:hwine] (use needinfo) from comment #5)
> Thanks for the answers.
> 
> My inclination here would be to set up a new repository, named
> 'projects/metro'. To my knowledge, we've never done something quite like
> this before, but this would give us an option to NOT kill the repo if some
> community members still want to work on it down the road. If there's a
> better name than 'metro', please suggest it.
> 
> It will require level 3 commit access, and we can get builds stood up fairly
> easily.
> 
> It will have it's own update channel, named the same as the branch. (FYI,
> this is more than just producing the builds, it uses the same product
> delivery process as Firefox - it will be just like nightly.) This will take
> a bit longer to set up.
> 
> I've been assuming that the builds will be en_US only.
> 
> If all the above is correct, especially the name, I can start the various
> processes.

Yep, that sounds awesome!

	Hal Wine [:hwine] use NI!
	Comment 7 • 10 years ago

Jim, the repo is now available at http://hg.mozilla.org/projects/metro -- you should be able to clone and land at will.

It will be a few days before we have builds going.

	Jim Mathies [:jimm] Reporter
	Comment 8 • 10 years ago

(In reply to Hal Wine [:hwine] (use needinfo) from comment #7)
> Jim, the repo is now available at http://hg.mozilla.org/projects/metro --
> you should be able to clone and land at will.
> 
> It will be a few days before we have builds going.

great, thanks. should I file a new bug on getting builds going?

	Hal Wine [:hwine] use NI!
	Comment 9 • 10 years ago

At this time, you can get builds from try.

You do ask for a number of builds in comment 0 -- we can keep the discussion of which builds/services here, and I'll file bugs to implement each piece. Which platforms will be part of the CI & nightly builds depends (in part) on what the official "tier level" is for this going forward. I haven't heard anything official yet on that.

	Jim Mathies [:jimm] Reporter
	Comment 10 • 10 years ago

(In reply to Hal Wine [:hwine] (use needinfo) from comment #9)
> At this time, you can get builds from try.
> 
> You do ask for a number of builds in comment 0 -- we can keep the discussion
> of which builds/services here, and I'll file bugs to implement each piece.
> Which platforms will be part of the CI & nightly builds depends (in part) on
> what the official "tier level" is for this going forward. I haven't heard
> anything official yet on that.

Generally we'd like to do a typical "twig" set of builds and tests similar to oak, does that require some sort of tier designation?

	Jim Mathies [:jimm] Reporter
	Comment 11 • 10 years ago

Hey Hal, this obviously isn't a high priority over other projects, but we'd appreciate some help in getting bugs filed for getting builds going, which maybe some rough estimate of time line.

	Jim Mathies [:jimm] Reporter
	Comment 12 • 10 years ago

s/which/with

	Hal Wine [:hwine] use NI!
	Comment 13 • 10 years ago

Jim - go ahead and file bugs for the builds you need -- there may be resource constraints, but specific bugs would be a better place to get that discussion going.

Since the repository exists, and is being used, closing this bug.