~emersion/public-inbox

1

Re: Release model of hut

Details
Message ID
<20220302184752.dmkpe36ggbmnsrnm@xenrox.net>
DKIM signature
pass
Download raw message
On Wed, Mar 02, 2022 at 02:23:06PM +0000, Simon Ser wrote:
> Hi,
>
> On Monday, February 28th, 2022 at 22:10, jlk <me@jlk.one> wrote:
>
> > I am interested in bringing hut to the openSUSE community/devel projects
>
> Nice!
>
> > Do you have plans to implement some kind of release model in the
> > future or is it still to soon to ask?
>
> I think it would be reasonable to publish a version sometime soon. I'm
> still not 100% sure we won't change some flags or behavior, so maybe it
> would be best to name it e.g. 0.1.0 to make the unstability clearer.

I am pretty sure there will be at least some breaking changes (e.g. once
some good usability for ACL updates is found, all services should
probably use that).

>
> Thorben, thoughts on that? Anything you'd like to do before a release?

I guess a release with the current features will already be quite
useful, especially now that the pages API - where there is no
alternative to using GraphQL mutations - is more or less
feature-complete.
There's nothing special I would particularly like to see in the first
release. The next features I wanted to work on are pretty boring
(assigning users to tickets, todo ACL handling, tracker creation) or
need some more involved changes to gqlclient (ticket show, ticket
create).

>
> (CC'ing the list for transparency.)

There was a typo in the list address.

>
> Thanks,
>
> Simon

Re: Release model of hut

Details
Message ID
<f602aa46-934a-dbaa-0f49-8bd56f7a192a@jlk.one>
In-Reply-To
<20220302184752.dmkpe36ggbmnsrnm@xenrox.net> (view parent)
DKIM signature
pass
Download raw message
Hey,

>> I think it would be reasonable to publish a version sometime soon. I'm
>> still not 100% sure we won't change some flags or behavior, so maybe it
>> would be best to name it e.g. 0.1.0 to make the unstability clearer.
> I am pretty sure there will be at least some breaking changes (e.g. once
> some good usability for ACL updates is found, all services should
> probably use that).

That should be no problem as some breakage can be expected from devel packages 
and my guess is that users wanting to install hut already know about it's status.
For me keeping track of my maintained packages works better with some kind of 
release versioning and I don't think that a well-defined scope of releases is 
that important at this development state.

>> (CC'ing the list for transparency.)

Great, next time I will send requests to the list directly? I was not sure if 
the public inbox should be used for non-technical issues.
Just for completeness as it got cut out from the first citation: The package is 
already available from my home project if someone wants to use it already: 
https://build.opensuse.org/package/show/home:jlkDE/hut

Best regards
Jan-Luca
Reply to thread Export thread (mbox)