Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. JD: Update the documentation for checkout and build (can use the uDig docs as a good starting point for this)
    • Try (tick) Source Code Try out the docs using the official github fork
    • (tick) Using Git Do we need the Fork me instructions here? With a link to developers guide?
  2. JD: Update (tick) Update the developers guide with a note about pull requests; and any other requirements:
    • a quick primer (tick) a quick Working with Git primer for people with sample commands for common tasks
    • (tick) Working on a stable branch a list of git does and donts, ie don't rebase on a public branch, etc... 
    • line endings figured out re Bens comment
    JD: Update
  3. JD: (tick) Update the build procedure:
    • Maven: a way to get git revision info from the build...
    • Hudson: update the scripts to pull from git
  4. JD: Transition the repository - July 1st Weekend 
    • (tick) Contact github about the size of the repository; uDig experience shows this will be fine - but it is good to ask.
    • Set up a GeoTools organisation (PSC members as group owners), with a group for commiter
    • (tick) Do westart from the official github fork? YES (If we need to grab anything else we will do so on request)
    • (warning) Make the old repository read only http://trac.osgeo.org/osgeo/ticket/913
    • Turn on github
  5. JD: Transition (tick) Transition comitters
    • Grab the comitter list from OSGeo servers; send out an email asking for github IDs
    • Create GeoTools PSC and GeoTools Committers Groups (uDig organisation is an example here)
    • Add github IDs as appropriate
  6. Transition JD: (tick) Transition the build machinery
    • hudson configuration
    • release scripts
  7. JGJD: Release 8.0-RC3 RC2 form the new repository to show we made it
    • Update any of justin's automated scripts
    • Update the how to cut a release page in the docs