Le Samedi 4 Février 2006 21:03, Tobias Toedter a écrit :
> (My first mail didn't seem to have reached the list, sorry if I've posted
> now twice.)
Hello,
It has reached the list :P
> > .bold { } by strong {}
> > .italic { } by em { }
> >
> > and replace <span class="bold"> and <font class="fold"> (etc) by <strong>
> > (etc)
> >
> > That's maybe the cleanest way to do it.
>
> Absolutely. I'm strongly in favour of this approach. I also think that it
> should be easily manageable before the next release.
Ok, so we'll go for it.
> Do you think that those fixes (span and font tags -> strong and em tags)
> could be committed on the trunk, or should we open a new branch for that as
> well?
I think that the wiki format branch name is based on the main purpose of the
branch but most changes we are currently doing should happen on the branch.
First, this make our life easier when comes the time of the merge.
Second, there is no reason to implement these different things concurrently,
on different branches.
Adding a new branch would only make sense if we where about to start new
development that where not due to be merged at the same time than the others.
And working on the trunk would just break our current policy (some projects
have a different policy, they consider the trunk as the first place for
developments and do branches only exceptionally - when they have to make a
bugfix release, they build it starting from an old release tag) and that
would bad.
So this should simply go on the current branch. To do things nicely, a task
should be added for this and a dependancy should be added on the item
handling the branch :)
Regards,
--
Mathieu Roy
+---------------------------------------------------------------------+
| General Homepage: http://yeupou.coleumes.org/ |
| Computing Homepage: http://alberich.coleumes.org/ |
| Not a native english speaker: |
| http://stock.coleumes.org/doc.php?i=/misc-files/flawed-english |
+---------------------------------------------------------------------+
_______________________________________________
Savane-dev mailing list
[email protected]
https://mail.gna.org/listinfo/savane-dev
