+1 for master-only and killing off -devel if few (if any) people are using
-devel
+1 for David's idea of making exceptions when there are big changes (like a
beta). As the community grows (and it looks like it slowly does) people
will want to try that devel/beta out, especially if there are some juicy
features in there. Maybe when such a beta is released, we can make a thread
on the ML and ask people who gave it a spin to write a few lines (I tried
this, it worked) so we have some kind of feedback of what was "tested"
before we consider it stable
-1 for time-based releases, as I think they're more appropriate for [much]
bigger projects. I would release when it's worth releasing (i.e. it's ready
when it's ready)

Regarding code quality: I have a QA background so I tend to put a[n overly]
big price on testing and documentation. But I still wouldn't stop moving
forward with the project for the sake of quality - Rainer adds juicy stuff
with every release and, looking back, I'm always thinking what a nice
progress this project has made.

However, I think there's increasing debt in terms of tests and docs as new
features are added. As rsyslog gets more complex, it looks harder to keep
it stable.

So I would go with something in the middle: when a new feature is done,
let's add docs and some basic tests to the testbench to it. If we want to
make exceptions, let's add a github issue with a few useful pointers so we
can "catch up" later.

--
Performance Monitoring * Log Analytics * Search Analytics
Solr & Elasticsearch Support * http://sematext.com/

On Thu, Oct 30, 2014 at 2:35 PM, singh.janmejay <[email protected]>
wrote:

> +1 for testsuite and CI.
> +1 for time based releases.
>
> It'll be valuable to have adhoc minor/micro releases. Release feature by
> feature or few features/fixes at a time type of thing.
>
> --
> Regards,
> Janmejay
>
> PS: Please blame the typos in this mail on my phone's uncivilized soft
> keyboard sporting it's not-so-smart-assist technology.
>
> On Oct 30, 2014 6:01 PM, "Thomas D." <[email protected]> wrote:
>
> > Hi,
> >
> > +1 for an always working "master" branch.
> >
> > Do your work in feature branches. Only merge when you think the changes
> > are ready. Don't merge when you think "I am ready, but this needs
> testing".
> >
> > Regarding the testing problem in general: I would stop adding new
> > features for a while. Spend more time in improving code quality.
> > Try to find/create a working test suite. There will always be the
> > problem that nobody will test your stuff. So you need a way to write
> > tests. Yes, creating a test suite will take some time. But in the end it
> > will improve the software quality and boost your development.
> > Remember that you can use CI for free with GitHub. Every pull request
> > could be automatically tested for you...
> >
> >
> > +1 for a time-based release approach.
> >
> >
> > PS: Debian Jessie will freeze at 23:59 UTC on the 5th of November 2014.
> > Just a reminder if you want to see some of the recent changes in
> Jessie...
> >
> >
> > -Thomas
> > _______________________________________________
> > rsyslog mailing list
> > http://lists.adiscon.net/mailman/listinfo/rsyslog
> > http://www.rsyslog.com/professional-services/
> > What's up with rsyslog? Follow https://twitter.com/rgerhards
> > NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad
> > of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you
> > DON'T LIKE THAT.
> >
> _______________________________________________
> rsyslog mailing list
> http://lists.adiscon.net/mailman/listinfo/rsyslog
> http://www.rsyslog.com/professional-services/
> What's up with rsyslog? Follow https://twitter.com/rgerhards
> NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad
> of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you
> DON'T LIKE THAT.
>
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of 
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE 
THAT.

Reply via email to