Versions Compared

Key

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

...

  • Cons
    • Release process ? (weekly release will be more complicated due to vote process) (olamy)
      • The definition of an ASF release (http://www.apache.org/dev/release.html) is something that's publicized outside of the project's developers mailing list, so developer snapshots can be released quickly. A proper release requires a 72-hour vote (bdelacretaz)
      • The ASF process does not requires a 72-hour vote. It says it "should  generally be permitted to run for at least 72 hours to provide an opportunity for all concerned persons to participate regardless of their geographic locations." (http://www.apache.org/foundation/voting.html) (elecharny)
    • new committer entry (olamy : IHMO not a real issue as the goal is to probably to move only core and bundled plugins)
      • Adding new committers is not complicated but requires a 72-hour vote and there's a delay for creating new accounts that's currently up to a week (bdelacretaz)
    • back to svn (AFAIK asf use a central svn repo) (olamy : btw is it a problem ?) (andrew: fwiw, ASF has talked about having a git repo, but no one there has stepped up to get it set up/supported - that may be something we'd be able to help with)
      • Is this really true? Why could we not continue to run with github? Can someone explain what the infrastructure constraints are? (magnayn)
      • Apache project code must be in the ASF's central svn repo, but you can use git to a certain extent, see http://git.apache.org - git support might be extended in the future but there are no definite plans at this time as far as I know (bdelacretaz)
    • legal issues regarding gpl libs (olamy : btw same for eclipse)

...