History of Contribute Code
Version 2 | Current version | |||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
As you know, bitweaver consists of a set of core packages and a number of optional packages. New devs who join the bitweaver coding team, have immediate access to non core packages and may commit to these. When there is demand, we will grant access to the core packages. Commits to these need to be treated with more respect since they affect all packages. ToDo List
Discuss CommitsCertain types of commits should always be discussed:
Schema ChangesIf you do need to make schema changes (regardless of how small the changes are):
Version NumbersAny package can use version numbers as they see fit. Core packages stick to the following rules:
To illustrate this with an example: bitweaver version 2.0.0 is released and all core packages have version 2.0.0. now liberty undergoes a schema change which would bump it up to version 2.1.0 but the remainder of the core packages still remain at version 2.0.0 Core PackagesCore packages consist of:
Other notesPlease make sure you view the CodingGuidelines before you start committing. We've spent a lot of time cleaning up the code and it would be a shame to mix styles and get sloppy.Be careful when committing and always make sure you've tested your changes before committing them. </version> | As you know, bitweaver consists of a set of core packages and a number of optional packages. New devs who join the bitweaver coding team, have immediate access to non core packages and may commit to these. When there is demand, we will grant access to the core packages. Commits to these need to be treated with more respect since they affect all packages. How can i contribute?We recommend that you subscribe to the bitweaver-core mailing list. This is a low volume mailing list where important announcements are made.Frequently it's useful to discuss changes in real time and we recommend that you ConnectingToIRC. Commit using CVS (recommended)
Submit Patches to SourceforgeAlternatively, you may submit patches to sourceforge. This might not always get picked up right away, since we are not very good at checking the patches section...Discuss CommitsCertain types of commits should always be discussed via the bitweaver-core mailing list or on IRC:
Schema ChangesIf you do need to make schema changes (regardless of how small the changes are):
Version NumbersAny package can use version numbers as they see fit. Core packages stick to the following rules:
To illustrate this with an example: bitweaver version 2.0.0 is released and all core packages have version 2.0.0. now liberty undergoes a schema change which would bump it up to version 2.1.0 but the remainder of the core packages still remain at version 2.0.0 Core PackagesCore packages consist of:
Other notesPlease make sure you view the CodingGuidelines before you start committing. We've spent a lot of time cleaning up the code and it would be a shame to mix styles and get sloppy.Be careful when committing and always make sure you've tested your changes before committing them. |