[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [incubation] Additional GitHub Repos
|
Hi Kevin
Tidy is good, but history is good too.
If in 5 years time you want to know why the code is the way that it is,
it will be much harder to figure it out if the repo has changed. This
prevents a 'simple' check out the five year old code.
IMHO if already have a (GIT) repo stick with the GIT thereof, unless you
really are going for such a major tidy that it approaches a rewrite.
You can refactor to an archive/dead/deprecated top level folder within
the one GIT repo.
Regards
Ed Willink
On 10/04/2025 16:02, Kevin Herron via incubation wrote:
Recently I completed the move to a project-specific org on GitHub
(e.g. i.e. `eclipse/milo` became `eclipse-milo/milo`).
Now I'm preparing for a long overdue 1.0 release and looking to move
some of the modules in my project to separate incubating or deprecated
repositories (i.e. create `eclipse-milo/milo-incubating` and
`eclipse-milo/milo-deprecated` repositories).
Is this a pattern that other projects have used before? Are there any
objections to this? Is this just a simple help desk request? Am I even
asking in the right place? :)
Thanks,
Kevin
_______________________________________________
incubation mailing list
incubation@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/incubation
