Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
O
Orekit tutorials
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Orekit
  • Orekit tutorials
  • Issues
  • #1

Closed
Open
Opened Jan 15, 2020 by Yannick Jeandroz@yannick.jeandrozDeveloper

No `develop` branch

I just noticed that the readme is inconsistent with the actual repo for the tutorials. The readme says to checkout the develop branch, but it does not exist. The only branch existing right now is master. So the clone command from the readme fails.

What is the desired branching model for the Tutorials repo ?

  • Do we put everything on master ? In this case we should modify the readme to reflect that
  • Do we use a gitflow-like branching model, like on the main repo ? In this case we should create the develop branch right now, to make the clone command from the readme work

I would personnaly prefer the gitflow-like branching model, which should make it easier to prepare tutorials for the upcoming Orekit version without interfering with the current one. It could be useful for major releases that break compatibility. The downside is that it is slightly more complex, and people contributing to the tutorials might be unfamiliar with gitflow, maybe ?

This may seem like a trivial issue, but since the tutorials will likely be one of the first steps for newcomers to Orekit, I think it is important to make this work as smooth as possible.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: orekit/orekit-tutorials#1