<br><br><div class="gmail_quote">On Wed, Sep 8, 2010 at 11:04 AM, Bernhard Reiter <span dir="ltr"><<a href="mailto:bernhard@intevation.de">bernhard@intevation.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Am Dienstag, 7. September 2010 18:04:05 schrieb Igor Novikov:<br>
<div class="im">> > > Not necessary, 0.6.17 is tagged, just go at the skencil-0.6 branch.<br>
> ><br>
> > Well "store all old sources unmodified" sounds a bit scary, although it's<br>
> > not clear to me what that might mean exactly.<br>
<br>
</div>(I believe Bernhard just fears that somebody will reformat or refactor<br>
the sources to a large degree. However I find that suitable for any person<br>
that likes to push Skencil forward. On the other hand, if you make diffs<br>
readable by Bernhard, he might read them and give his knowledge. So do what<br>
you believe is best.)<br>
<div class="im"><br>
> If we create a copy of<br>
</div>> skencil-0.6/<<a href="http://wald.intevation.org/plugins/scmsvn/viewcvs.php/skencil/" target="_blank">http://wald.intevation.org/plugins/scmsvn/viewcvs.php/skencil/</a><br>
>branches/skencil-0.6/?root=skencil> as a skencil-0.6.18/ we provide an easy<br>
<div class="im">> access<br>
> to ver.0.6.17 for users which prefer SVN version of application.<br>
<br>
</div>People that want to check out 0.6.17 can still do this with svn<br>
via the following tag:<br>
<a href="https://wald.intevation.org/plugins/scmsvn/viewcvs.php/skencil/tags/skencil-0.6.17/?root=skencil" target="_blank">https://wald.intevation.org/plugins/scmsvn/viewcvs.php/skencil/tags/skencil-0.6.17/?root=skencil</a><br>
<br>
If in the future, we need a new tag, we could still branch at that point<br>
later. But currently Igor, you (and your folks) are the only developers,<br>
so you should use the main branch in my view as this is the only official<br>
Skencil progress.<br>
<div class="im"><br>
> If such branching style is not suitable for the project so I can commit all<br>
> changes into skencil-0.6/<br>
<br>
</div>My writing above is just a suggestion, it is up to you, if you like to work in<br>
a branch, you can of course do so. Given that the old tags already are called<br>
0.6.17 and so on, I would not call a working branch 0.6.18 right now, to avoid<br>
possible confusion, but again, this is just a suggestion and you can do so,<br>
if you like. :)<br>
<div class="im"><br>
> > Anyway, if the changes to 06<br>
> > branch are done in such a way that it's possible to follow them by<br>
> > reading the diffs (i.e. small self-contained changes with good commit<br>
> > messages), that<br>
> > may be OK. But please don't do any wholesale changes like converting all<br>
> > indents to tabs without prior discussion.<br>
><br>
> It's naturally because Skencil has own style coding conventions.<br>
<br>
</div>Igor, it is wonderful that you would like to help out with Skencil<br>
development!<br>
<br>
Bernhard<br>
<font color="#888888"><br>
<br>
--<br>
</font><div><div></div><div class="h5">Managing Director - Owner: <a href="http://www.intevation.net" target="_blank">www.intevation.net</a> (Free Software Company)<br>
Deputy Coordinator Germany: <a href="http://fsfe.org" target="_blank">fsfe.org</a>. Board member: <a href="http://www.kolabsys.com" target="_blank">www.kolabsys.com</a>.<br>
Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998<br>
Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner<br>
</div></div><br>_______________________________________________<br>
Skencil-devel mailing list<br>
<a href="mailto:Skencil-devel@wald.intevation.org">Skencil-devel@wald.intevation.org</a><br>
<a href="http://lists.wald.intevation.org/mailman/listinfo/skencil-devel" target="_blank">http://lists.wald.intevation.org/mailman/listinfo/skencil-devel</a><br>
<br></blockquote></div><br><br>Hi Bernhard!<br><br>Yes, you are right, the users can use copies from tags/ folder.<br>But actually we have two trunks: real trunk with 0.7.x version and branches/skencil-0.6/ as a trunk for 0.6.x version.<br>
And branches in tags/ folder. In my practice tags were usually used for important project milestones <br>(first of all for internal development usage) but not for releases.<br>Of course it's just an issue of methodology no more. So let's using skencil-0.6/ as a formal trunk.<br>
<br>I have tested Debian package for Skencil and found that it doesn't look like a stable application:<br><br><a href="http://saveimg.ru/pictures/10-09-10/a5e15398d26ba5c0850b13bc415c5857.png">http://saveimg.ru/pictures/10-09-10/a5e15398d26ba5c0850b13bc415c5857.png</a><br>
<br>So I'm starting ver.0.6.18 development iteration to fix these issues and provide stable Skencil build for tk8.5.<br>
<br>First of all I'd like to note that I have no a lot of time for investigations. Therefore to get a fast result I will implement <br>the same patterns as for UniConvertor and sK1. As you know packages of these projects have been included in all distros <br>
and their structure and build system are<span><span title=""> result of joint work with</span></span> maintainers of different distros. So I think this <br>experience is useful for Skencil revitalization.<br>
<br clear="all">If some issues will be not suitable we always can roll back changes. Anyway I will comment all changes to explain they.<br>Working solid build will be a first step because it's a major requirement to continue development. <br clear="all">
<br>-- <br>Regards,<br><br>Igor Novikov<br>sK1 Project<br><a href="http://sk1project.org" target="_blank">http://sk1project.org</a><br><br><br>