Am 16.11.2011 07:12, schrieb Lex Trotman:
> 1. Individual plugin maintainers shouldn't care about all the other
> plugins in the combined release
Not a written, but existing rule.
> 2. Users getting the combined release to build should get everything
> in one command
ACK.
> 3. The combined rele
Am 16.11.2011 12:02, schrieb Alexander Petukhov:
> Maybe we can use git pre-commit hook to prevent commits that breaks some
> quality criteria?
> http://book.git-scm.com/5_git_hooks.html
> To be honest I didn't get much into details but it seemed to me that it
> can handle quality check tasks.
Wel
Am 16.11.2011 22:50, schrieb Lex Trotman:
[..]
> I don't think your perception is wrong, but I think that keeping
> plugins reasonably separate is also a good idea. As a user I can
> choose the parts I want without the parts I don't need. So only
> really tiny things should be combined like addon
[...]
> I like this proposal. Requiring pull requests will also formally mean "get
> your plugin in shape" before release. I'd like to extend this to the point
> that if a plugin is not ready (due to bad code, inactive maintainer, or
> otherwise) the snapshot from the previous release will be taken
Am 16.11.2011 13:06, schrieb Thomas Martitz:
>
> I like this proposal. Requiring pull requests will also formally mean
> "get your plugin in shape" before release. I'd like to extend this to
> the point that if a plugin is not ready (due to bad code, inactive
> maintainer, or otherwise) the snapsh
Am 16.11.2011 02:18, schrieb Matthew Brush:
>
> With some changes to the build system(s) it should be possible to make
> each plugin buildable on its own or as part of the geany-plugins
> project, as opposed to now, where it's difficult (impossible?) to have
> your plugin build independently of th
Am 15.11.2011 17:55, schrieb Frank Lanitz:
We will have one master branch where all changes intended for releasing
are going in. Features and new plugins are going to be developed inside
branches (more late onto this topic) and once they are in a suitable
status, they are getting merged into mast
On 11/15/11 8:55 PM, Frank Lanitz wrote:
Hi developers,
It has been a while when I first announced a mail about my idea of
process after transition of geany-plugins repository. As from my
understand the only open point is to have clarified the
svn-url-reference question its a good point to tell
Hi Frank,
Although I am not a plugin developer I have a couple of suggestions
based on the following needs:
1. Individual plugin maintainers shouldn't care about all the other
plugins in the combined release
2. Users getting the combined release to build should get everything
in one command
3. Th
On 11/15/2011 08:55 AM, Frank Lanitz wrote:
Hi developers,
It has been a while when I first announced a mail about my idea of
process after transition of geany-plugins repository. As from my
understand the only open point is to have clarified the
svn-url-reference question its a good point to te
Hi developers,
It has been a while when I first announced a mail about my idea of
process after transition of geany-plugins repository. As from my
understand the only open point is to have clarified the
svn-url-reference question its a good point to tell you what I'm
thinking of.
Currently we do
11 matches
Mail list logo
