[t2t] 2.7 release (was: I NEED YOUR OPINION: Website and docs)

[Aurelio Jargas]

it's good to hear that a new version might be coming out soon. I would like
to get some patches in before the new version is released though. I'll
attach them to the appropriate bug reports.

Everybody would be happy of a "coming soon" release, but txt2tags
really needs a lot of Aurelio's work to be released, and unfortunately
he isn't currently available.
There's some design, new option and option name decisions Aurelio is
the only one who can do.
Personnally, I have done a lot of new targets so I have some fixes to
do on my TODO list.
Florent

Thanks for the reminder Florent.

Txt2tags deserves a hard work week(s?) to prepare the multitude of
changes for a release. There's so many news that it's even hard to
choose where to start. This time, I can't do it alone.

I need help.

1) The test suite is broken — (cd test ; ./run.py). It needs to be
fixed and all tests should pass OK. It the problem is the test, such
as it's OK-template is not updated, just fix the template. If the
problem is the wrong txt2tags behavior, fix txt2tags.

2) Changelog — We need to track changes since r382. Here's a good link
to start: http://code.google.com/p/txt2tags/source/list?num=25&start=406
Any effort to summarize the changes or at least highlight the
important ones will be appreciated. Things such as new targets, new
marks, new options, new rules are the most important.

3) Code isolation — Ideally all the new features added to txt2tags
since v2.6 should be, were possible, isolated in it's own class or
function. It will make it easy to modularize the code in the future
and keep the global namespace cleaner. If you wrote a new feature,
please try to encapsulate it in one class/function.

4) Backwards compatibility of generated code — Avoid changing the
syntax/alignment/case of target generated code. For example, changing
<B> to <b> in HTML. Users rely on the code to make their filters
(preproc, postproc) work. The test suite will scream if the target
code has changed. It's better to fix the code than the test-suite. If
possible, keep the generated code the same. Breaking changes should be
in 3.0 only.

5) New features, new tests — If you wrote a new feature, please, add a
new test do the test-suite to make sure your feature works. That's the
only way we can check if your nice idea will remain working in the
ever-changing txt2tags code. Email me if you need help in making the
test.

If you can help in any of these tasks, in any amount, that will be
GREAT. And I do really need this help. It's too much work this time.

In the last 2 years, it was the first time devs were free to commit
whatever they wanted to the txt2tags SVN, without my pre-approval.
That was a great experience and lots of good ideas were implemented.
Txt2tags now is more powerful than ever, thanks! But for the release,
I'll have to analyze all the changes, one by one, to make sure 1)
they're working 100% and 2) they're respecting the sacred KISS
Principle.

So, please, if you can help in any of these tasks, do it.

[Jendrik Seipp]

Post by Aurelio Jargas
5) New features, new tests — If you wrote a new feature, please, add a
new test do the test-suite to make sure your feature works. That's the
only way we can check if your nice idea will remain working in the
ever-changing txt2tags code. Email me if you need help in making the
test.

I think you definitely need to add a README file under test/ describing
how to write tests. E-mails are too private here. If someone has a
specific question others might have the same and you don't want to mail
them individually.

Also, the tests should be executable one by one in addition to running
them all at once.

Cheers,
Jendrik

[Aurelio Jargas]

Post by Jendrik Seipp

Post by Aurelio Jargas
5) New features, new tests — If you wrote a new feature, please, add a
new test do the test-suite to make sure your feature works. That's the
only way we can check if your nice idea will remain working in the
ever-changing txt2tags code. Email me if you need help in making the
test.

I think you definitely need to add a README file under test/ describing
how to write tests. E-mails are too private here. If someone has a
specific question others might have the same and you don't want to mail
them individually.
Also, the tests should be executable one by one in addition to running
them all at once.

You're right Jendrik.

Just added the README file:
http://code.google.com/p/txt2tags/source/browse/trunk/test/README

Needing help, please send an email here to the mailing list. Then we
can update the README with the answer.

You can't run a specific test alone, but you can run one (or more)
specific module alone. For example:

./run.py marks

[Forgeot Eric]

I'll have a look at the changelog!

2) Changelog — We need to track changes since r382. Here's a good link
to start: http://code.google.com/p/txt2tags/source/list?num=25&start=406
Any effort to summarize the changes or at least highlight the
important ones will be appreciated. Things such as new targets, new
marks, new options, new rules are the most important.

[Aurelio Jargas]

Great Eric, thanks!

And you're fast, already begun the work:
http://code.google.com/p/txt2tags/source/detail?r=897

THANK YOU

Post by Forgeot Eric
I'll have a look at the changelog!

Post by Aurelio Jargas
2) Changelog — We need to track changes since r382. Here's a good link
to start: http://code.google.com/p/txt2tags/source/list?num=25&start=406
Any effort to summarize the changes or at least highlight the
important ones will be appreciated. Things such as new targets, new
marks, new options, new rules are the most important.

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
txt2tags-list mailing list
https://lists.sourceforge.net/lists/listinfo/txt2tags-list