mukulga commented on PR #108:
URL: https://github.com/apache/xalan-java/pull/108#issuecomment-1775412812

   @vlsi,
   > Committers already have an infrastructure: they can commit to a branch 
directly.
   > If you commit directly, it is less actions for everybody
   
   I actually started this way only few months ago. i.e, I was committing to 
the XalanJ dev repos branch xalan-j_xslt3.0 directly. If I may recall 
correctly, you suggested few months ago, for XalanJ committer(s) to create 
their own fork of the XalanJ repos branch, and then raise a PR to get that 
merged to XalanJ repos branch. I found your suggestion ok then, and made the 
switch (which required me to change, few git things on my local) to that 
process suggested by you.
   
   Now you're suggesting us, to follow the earlier process (i.e, committing to 
the XalanJ dev repos branch xalan-j_xslt3.0 directly). This is normally not 
convenient. It seems to me that, currently only *you* (with due respect) is 
having issues with these XalanJ development activities, and no one else is 
mentioning about these issues on XalanJ lists or github.
   
   Your opinions are very important for us to, think, evaluate and adopt 
(please keep on writing them). But if XalanJ committer(s) disagree to a certain 
point, IMHO you should respect that and not feel bad in any way, and not 
'pressure' us to adopt your points.
   
   Since you write frequently about, XalanJ git and other processes (these are 
very important topics for any software development project), and XalanJ 
committers and pmc members sometimes have different opinions, to the points 
raised, I think it'd be useful to have a 'XalanJ development and maintenance' 
process document kept on XalanJ repos. May be you should, or someone from 
XalanJ team may create a draft of this document, and then we may have a 
discussion and vote on XalanJ list to finalize that.
   
   > I suggest using "subject" and "body" better: put the most important bits 
into **subject**, and put details in **body**
   
   Thanks for this suggestion, and I find this useful and shall try to follow 
that.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional commands, e-mail: dev-h...@xalan.apache.org

Reply via email to